Browse jobs
Straight from companies' own career pages, updated as roles open, change or close.
Straight from companies' own career pages, updated as roles open, change or close.
ngrok builds developer infrastructure to connect services and AI models, wherever they run.
Most developers know us as the way to put localhost on the internet. More than 15 million of them use ngrok, at companies like GitHub, Okta, HashiCorp, and Twilio. It's the same ngrok they've loved and leaned on for years, now with the power to run production traffic at scale.
Teams use ngrok to deliver APIs, connect to their customers' networks, manage device fleets, and route traffic between public and local AI models.
Across all of it, we hold ourselves to one standard: developers should be able to finish a whole job without becoming experts in every system it touches. We take on the complexity, make thoughtful choices by default, and keep developers in control of what matters to them.
Still reading? Good. There's more below worth your time.
The Infra Platform team builds the systems ngrok engineers rely on to build, deploy, and operate ngrok itself. We think about infrastructure the way software engineers think about software: APIs, abstractions, automation, reliability, and developer experience.
We own the internal platform that keeps engineering productive and production stable. That includes build systems, deployment workflows, infrastructure tooling, service reliability, and the glue that connects it all together. Our work touches nearly every engineer at the company, which means when we improve something, everyone feels it.
You’ll work on systems with real production load, latency constraints, and reliability requirements. We run a modern stack built primarily around Go, PostgreSQL, gRPC, Kubernetes, Terraform, Protobuf, nix, and AWS. Most of our infrastructure and application code lives in a monorepo powered by extensive code generation and internal tooling that makes complex workflows feel surprisingly manageable.
This is the team people come to when things are scaling, failing, deploying too slowly, or generally behaving like distributed systems tend to behave.
Extra credit if you’ve worked with:
ngrok runs entirely on AWS. Engineers develop on remote EC2 environments that run a full Kubernetes cluster of the ngrok stack, closely mirroring production. The codebase is primarily Go and TypeScript. We use Postgres for persistence, Kafka for streaming, Protobuf for service boundaries, and Kubernetes, Terraform, Helm, and Buildkite to operate and ship reliably. React is used for user interfaces, and GitHub supports our development workflows and remembers everything.
This is a remote position for candidates outside of the Bay Area and a hybrid role for candidates within commuting distance to San Francisco. Our Bay Area employees commute to the office on Tuesdays and Wednesdays.
All candidates must be US-based, and legally authorized to work in the United States.
At this time, ngrok is unable to provide visa sponsorship for this position. Applicants must be authorized to work in the United States on a permanent, ongoing basis without the need for current or future sponsorship.
Job Title
Senior Software Engineer
Software Engineer III
Job level and actual compensation will be evaluated based on factors including, but not limited to, qualifications objectively assessed during the interview process (including skills and prior relevant experience, potential impact, and scope of role), internal equity with other team members, market data, and specific work location. We provide an attractive mix of salary and equity.
#LI-Hybrid
San Francisco · United States
Posted 1 month ago
Still open · checked 16 Nov 2026
Ngrokinc's career page (Greenhouse)
Opens the original posting right away and adds it to your tracker in the background.