Skip to main content

Senior Software Engineer (Backend) - Node Connectivity

Posted today

acestackSan Jose (CA)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Senior Software Engineer (Backend) - Node Connectivity
Location: San Jose, CA (Remote)
Fulltime – Permanent
Job Description: Must Have Technical/Functional Skills:10+ years of professional software engineering experience, including technical leadership of substantial systems. Strong experience with Go, C/C++, or another systems programming language, with the ability to become productive in Go. Experience designing and operating large-scale distributed services in production. Strong knowledge of Linux and networking fundamentals, including IPv4/IPv6, TCP, routing, DNS, and TLS.Experience with concurrency, performance analysis, debugging, and capacity planning. Sound judgment in architecture, incident response, and technical tradeoffs. Clear written and verbal communication. You can align teams without relying on authority
Roles & Responsibilities: Nextunnel is a globally distributed, high-availability networking system. It routes device traffic across regions while enforcing strict access controls and preserving service through failures. The platform is written primarily in Go and runs on Kubernetes in AWS. It uses gRPC, mTLS, Docker, GitLab CI, Kustomize, and modern observability tooling. We are looking for a hands-on technical lead to guide porting the system to a new deployment platform. Work on porting Nextunnel deployment to a newly created internal kubernetes-like platform. Troubleshoot issues in bootstrapping nextunnel in this new environment. Improve the service's scalability, reliability, security, performance, and operability. Establish clear technical direction and turn it into practical, staged delivery plans. Write and review robust Go code for distributed, concurrent, networked systems. Diagnose complex failures across applications, protocols, containers, and cloud infrastructure. Strengthen testing through unit, integration, end-to-end, fuzz, and scale tests. Work with firmware, cloud infrastructure, security, SRE, and product teams on cross-system changes. Good to have skills: Kubernetes, AWS/EKS, Docker, Kustomize, and CI/CD systems.gRPC, Protocol Buffers, mutual TLS, PKI, or network security. Packet processing, tunneling, VPNs, load balancing, or distributed routing protocols.
Open: Telemetry, Prometheus, Datadog, or production observability at scale. Fuzz testing, performance testing, and failure testing.

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this