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.
- Our (unofficial) mascot is a shrimp. Yes, we make the puns.
- We have a designated Chief Emoji Officer, and the role is vital to our success.
- We like software that's serious and culture that's not.
- Our competitive advantage is that we're having fun.
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.
What You’ll Actually Do- Build and improve the engineering platform: You’ll work on the systems engineers use every day to develop, test, deploy, and operate ngrok. Better tooling, smoother workflows, fewer sharp edges.
- Treat infrastructure like software: You’ll automate operational workflows, improve reliability, and build systems that scale cleanly under production load. SRE and DevOps problems solved with software engineering discipline.
- Improve the developer experience: You’ll contribute to builder tools, deployment systems, CI/CD infrastructure, and internal abstractions that make engineers faster and safer when shipping changes.
- Help keep production healthy: You’ll participate in maintaining high uptime and operational excellence by improving observability, reliability, and incident response processes.
- Raise the engineering bar: You’ll mentor teammates, contribute technical direction, and help evolve the architecture and operational maturity of the platform over time.
- You have 3+ years of experience as a software engineer
- You’ve built and operated distributed systems in AWS or other cloud environments
- You’re comfortable in a statically typed, compiled language such as Go, Rust, C++, or Java (with bonus points for Go)
- You think operational problems are engineering problems
- You care deeply about developer experience and scalable systems design
- You enjoy understanding how systems fail, recover, and evolve over time
Extra credit if you’ve worked with:
- Kubernetes, Terraform, nix, PostgreSQL, Kafka, or gRPC
- Observability platforms like Datadog or Honeycomb
- Internal developer platforms or builder tooling
- Networking, infrastructure, or security-focused systems
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.
LocationThis 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.
SponsorshipAll 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.
CompensationJob Title
Senior Software Engineer
- Tier 1 (SF, LA, Seattle, NYC): $202,500 – $247,500
- Tier 2 (rest of US): $186,300 – $227,700
Software Engineer III
- Tier 1 (SF, LA, Seattle, NYC): $180,000 – $220,000
- Tier 2 (rest of US): $165,600 – $202,400
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
- Health stuff that actually matters. Full premiums covered on base healthcare, dental, and vision for you. Half covered for your dependents. Mental health and well-being support included, because taking care of your brain is as important as taking care of your teeth.
- Retirement matching that doesn't suck. 401(k) with 100% match up to 3% of your salary and 50% match up to another 2%. Future you will appreciate present you.
- Actually flexible time off. We say "open, flexible vacation policy" and actually mean it. Take the time you need. Your manager will bug you if you're not taking enough.
- Parental leave that's realistic. Up to 16 weeks if you give birth, up to 8 weeks for new parents (birth, adoption, fostering—however your family grows).
- Money to keep growing. Annual professional development budget for books, courses, conferences, or whatever helps you level up. Plus an annual home office/desk stipend to make your workspace not terrible.
- Work from wherever. Co-working space stipend if you want to get out of your house but aren't near our SF office.
- Lunch on us. 2x+ per week for employees onsite at our San Francisco office. Free food tastes better.
- Company offsites. Twice a year we get the whole team together. It's part strategy, part bonding, part excuse to hang out with Bufo (the toad).
- Regular feedback and fair compensation. Bi-annual reviews to make sure you're getting real feedback and staying competitively compensated. No surprises, no waiting around for performance conversations.
Skills Required
- 3+ years of experience as a software engineer
- Experience building and operating distributed systems in AWS or other cloud environments
- Proficiency in a statically typed, compiled language such as Go, Rust, C++, or Java
- Must be based in the United States
- Must be legally authorized to work in the United States on a permanent, ongoing basis without current or future sponsorship
- Experience with Kubernetes, Terraform, Nix, PostgreSQL, Kafka, or gRPC
- Experience with observability platforms such as Datadog or Honeycomb
- Experience with internal developer platforms or builder tooling
- Experience with networking, infrastructure, or security-focused systems
What We Do
Online in One Line ngrok is simplified, API-first ingress-as-a-service trusted by over 5M developers to get their apps online faster and keep security happy. With one line of code, developers get instant ingress to services with authentication, observability, and other critical controls. All without provisioning legacy proxies, load balancers or VPNs. ngrok’s simplicity has made it a de-facto standard tool among developers, and the world’s top brands — including GitHub, Okta, Shopify, and Twilio — recommend it throughout their documentation.
Gallery
