About the Team

This role will lead either our Gateway or Agent team, depending on your experience and interests.

Both teams sit on the critical path of every ngrok connection and are central to our reliability, performance, and customer trust.

• Gateway Team: Owns the core infrastructure that handles and shapes all traffic flowing through ngrok—routing, security enforcement, rate limiting, and observability. Every request passes through this layer, and its correctness and performance are foundational to everything we do.
• Agent Team: Builds the software that runs on the customer side of every connection. The Agent is what developers install and trust to securely expose their systems to the internet, and it must perform reliably across unpredictable, real-world environments.

What You’ll Actually Do

Lead a team that ships and learns quickly

You’ll manage and coach a team of 5–7 engineers. The goal isn’t just shipping—it’s building a team that can consistently make good decisions, move fast, and improve over time.

Treat management like a systems problem (with humans in the loop)

You’ll design how your team works: planning, execution, retros, feedback loops, and decision-making. You’ll tune the system, not just react to it.

Stay close enough to the code to matter

You won’t be coding every day, but you’ll get into the details when needed—reviewing designs, debugging tricky issues, and helping the team make better technical tradeoffs.

Drive product and technical direction together

This isn’t “just execution.” You’ll help shape what the team builds—balancing product work, technical investments, and experiments that actually teach you something.

Build a team people want to be on

You’ll coach junior and senior engineers, create psychological safety, and raise the bar on both performance and collaboration.

Connect the team to the bigger picture

You’ll make sure your team understands how their work ties to ngrok’s product, customers, and business. Context isn’t optional here. You’ll work closely with senior leadership and functional orgs to shape and meaningfully impact company culture and roadmap.

You Might Be a Great Fit If…

• You’ve spent 5+ years as a software engineer and comfortable in Go, Rust, Java, or C/C++
• You have 4+ years of engineering leadership experience
• You think in systems—whether that’s distributed systems or team dynamics
• You’re comfortable zooming in (code, debugging) and zooming out (strategy, org design)
• You’ve built things from scratch—teams, processes, or products
• You communicate clearly, directly, and without unnecessary fluff

Bonus points if you’ve:

• Contributed to open source, blogs, or conferences
• Worked in developer tools or product-led growth environments
• Built teams in ambiguous, early-stage contexts

Tech Stack

ngrok runs entirely on AWS. Engineers develop by using remote development tools and/or ssh to connect to 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.

Location

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.

Sponsorship

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.

Compensation

Engineering Manager: $225,000 – $275,000

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-Remote

About the AI Gateway Team

Our AI Gateway team builds the systems that define how AI traffic is identified, controlled, and understood as it passes through ngrok.

We own the AI-specific control plane at the gateway layer: policies, usage tracking, and enforcement that sit directly on live customer traffic. Our systems must behave correctly under real-world conditions—traffic spikes, unexpected model behavior, misconfigured policies, and customers asking, “Why was this blocked?” or “Where did my tokens go?”

What You’ll Actually Do

• Build and evolve the AI Gateway: You’ll work on the AI-aware gateway components that classify and handle AI traffic in real time. This code runs directly in the request path and must be fast, safe, and predictable.
• Own AI traffic policy enforcement: You’ll design and implement AI Gateway Traffic Policy Objects—rate limits, usage caps, and access rules specific to AI workloads. These policies exist to prevent runaway costs, misuse, and accidental exposure without breaking legitimate traffic.
• Track AI usage and token consumption: You’ll build and maintain systems that accurately measure AI usage—requests, tokens, and related metadata—so customers can understand how their AI systems behave and what they’re consuming.
• Make AI behavior observable and explainable: You’ll expose clear, trustworthy signals around AI traffic: what was allowed or blocked, which policies applied, and how usage accumulated. When customers ask “what happened?”, the gateway should already know.
• Design abstractions that hide complexity: You’ll work with product and design to build AI-specific gateway primitives that feel intentional and safe, without leaking provider quirks or infrastructure details into customer workflows.
• Ship systems customers trust in production: You’ll collaborate closely with Gateway, Customer Data, and Platform teams to ensure AI usage data, policy enforcement, and billing signals line up—so customers can turn these features on with confidence.

You Might Be a Great Fit If…

• You’re comfortable in a statically typed, compiled language such as Go, Rust, C++, or Java (with bonus points for Go)
• You’ve worked with AI/LLMs and can appreciate their unique brand of edge-cases
• You care about developer experience and thoughtful abstractions
• You enjoy defining system behavior, not just plumbing
• You’ve thought about retries, limits, and costs before being asked
• You like systems that move complexity from the user to the system

Extra credit if you’ve worked on:

• AI platforms or inference infrastructure
• API gateways with product-level opinions
• Usage limits, quotas, or billing-adjacent systems
• Customer-facing observability tools

Tech Stack

ngrok runs entirely on AWS. Engineers develop by using remote development tools and/or ssh to connect to 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.

Location

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.

Sponsorship

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.

Compensation

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-Remote

About the Gateway Team

We own ngrok’s core gateway layer — the infrastructure that sits between the internet and everything our customers run.

Every request, response, retry, and timeout passes through here.

Our job is to make sure that traffic is:

• Routed exactly where it’s supposed to go
• Secured correctly, every time
• Allowed or blocked for reasons we can explain
• Rate-limited and shaped without surprises
• Observable when something inevitably goes sideways

What You’ll Actually Do

• Build and operate the gateway core: You’ll work on the services every ngrok request passes through. They’re very fast, very hot, and have extremely high standards.
• Design routing and security primitives everyone depends on: You’ll build low-level policy, routing, and validation systems used across the platform—making sure bad configs fail fast and don’t accidentally DDoS the internet.
• Debug distributed systems in the wild: You’ll chase bugs caused by timing, load, and incorrect assumptions. Expect metrics, traces, packet captures, and the occasional “how is this even possible?”
• Ship infrastructure people sleep on (in a good way): You’ll build simple, durable systems and clean abstractions that other teams rely on daily—while thinking about blast radius, safety, and rollbacks more than flashy demos.

You Might Be a Great Fit If…

• You’re comfortable in Go, Rust, C/C++, or Java (bonus points for Go)
• You’ve built networking, proxy, or infrastructure systems in production
• You understand TLS/mTLS
• You enjoy systems that are invisible until they’re not
• You passionate about building primitives other teams depend on
• You’ve said “this needs to be rock solid” and meant it literally

Extra credit if you’ve worked on:

• Gateways, proxies, or edge platforms
• Security-critical infrastructure
• Multi-tenant networking systems
• Config-heavy systems that must never surprise users
• Anything described as “simple” in the original proposal

Tech Stack

ngrok runs entirely on AWS. Engineers develop by SSH’ing into 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.

Location

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.

Sponsorship

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.

Compensation

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

Software Engineer II

• Tier 1 (SF, LA, Seattle, NYC): $148,500 – $181,500
• Tier 2 (rest of US): $136,600 – $166,900

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-Remote

About the Data Platform Team

The Data Platform team owns the data platform and analytics systems that power decision-making across ngrok. We handle ingestion, modeling, metrics, and reporting-the systems that make sure every event is counted correctly and every number in a deck can be defended.

We manage about 500TiB of data, run a dagster instance with over 1,600 assets, maintain 550+ dbt models, and own Flink streaming pipelines that process ~22,000 messages per second on average.

This data is used across all teams @ ngrok, from marketing to financial reporting. Our systems must be correct, explainable, and resilient under real-world conditions: traffic spikes, schema changes, late-arriving events, and other challenges that come from running a large, globally distributed system.

We treat data as a product: reliable, observable, well-modeled, and thoughtfully designed. Our Data Platform team is part of the Engineering organization and doesn’t live in a silo.

What You’ll Actually Do

• Build the data backbone: You’ll design and evolve the pipelines and orchestration systems that move data across ngrok - from product events to financial reporting. Ingestion, transformation, modeling, reliability. The foundation everything else depends on.
• Make the numbers make sense: You’ll own core business and product datasets - usage, revenue, growth, performance-and ensure they’re accurate, reconciled, and trusted. No mystery metrics. No “why doesn’t this match?” Slack threads.
• Turn raw events into decision-ready insight: You’ll build and refine the models that power dashboards, planning, forecasting, and experimentation. Clean schemas. Durable definitions. Metrics people actually align on.
• Raise the bar on data reliability: You’ll implement validation, testing, observability, and monitoring across our data systems. Pipelines shouldn’t silently fail. Dashboards shouldn’t drift. Finance shouldn’t find surprises.
• Own the platform as it scales: You’ll improve performance, cost efficiency, and architectural design across our data stack (Airbyte, Dagster, dbt, Athena, Flink, Superset, and beyond). As traffic and customers grow, the data platform keeps up.
• Partner across the company: You’ll work closely with Product, Engineering, GTM, Finance, and Leadership. They’ll have hard questions. You’ll build the systems that make those answers obvious.

You Might Be a Great Fit If…

• You’re familiar with Python, SQL, and Scala
• You’re also comfortable in a language such as Go, Rust, C++, or Java (with bonus points for Go)
• You’re comfortable writing production-quality code and treating data systems like real software-not just queries in a notebook
• You’re interested in AWS infrastructure and Kubernetes, managed through Infrastructure as Code (Terraform or similar) — not click ops
• You’ve built and operated large-scale event streams, product telemetry, or high-volume ingestion pipelines in production
• You enjoy thinking about data models, invariants, lineage, and failure modes
• You care about data quality and observability, and you design systems that make errors visible-not silent
• You’re the person people ping when the numbers don’t add up-and you actually enjoy figuring out why

Extra credit if you’ve worked on:

• Usage-based billing, metering, revenue, or financial reporting systems
• Event-driven or streaming data architectures
• Customer-facing dashboards or internal executive reporting

Tech Stack

ngrok runs entirely on AWS. Engineers develop by using remote development tools and/or ssh to connect to remote EC2 environments that run a full Kubernetes cluster of the ngrok stack, closely mirroring production.

We self host a large part of our data stack on Kubernetes, namely dagster, Superset, Airbyte, and Flink. Our core data warehouse is in Athena, with the data being stored as Apache Iceberg. We also run some workloads on our Clickhouse Cloud infrastructure.

Our data codebase is a mix of Python and Scala 3. We use dbt for SQL modeling. All data tools are fully integrated with the rest of our developer platform.

The ngrok 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.

Location

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.

Sponsorship

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.

Compensation

bout the Admin Team

Our Admin Engineering team builds the systems that decide who can access ngrok, what they can do, and how everything is configured.

We own identity, access control, and configuration at scale—users, certificates, service accounts, domains, policies. If it answers “who can do what?”, it’s our problem. When things work, nobody notices. When they don’t, people get locked out or something gets exposed that really shouldn’t be.

A lot of this work lives in the tension between power and safety. Customers want full control and APIs for everything. They also want guardrails and sane defaults. You’ll build systems that manage both—without making either side miserable.

What You’ll Actually Do

Build the control plane

Design and operate the services and APIs behind admin workflows—the layer that defines how ngrok behaves in production.

Own identity and access

Develop and evolve IAM/RBAC systems across users, certificates, and service accounts. If something can authenticate or authorize, you’ll touch it.

Make configuration scale

Build global configuration systems for domains, policies, and traffic behavior—flexible enough for automation, safe enough for humans.

Make debugging possible

Improve observability across admin workflows so we can answer “what changed?” without guessing or digging through logs for an hour.

Ship systems people rely on

Work with product and platform teams to deliver features that are stable, understandable, and actually usable in production.

Keep things from breaking (or worse)

Ensure admin systems stay scalable, reliable, and hard to misuse—because mistakes here tend to be very visible.

You Might Be a Great Fit If…

• You’ve built backend systems that needed to be correct and hard to misuse
• You’re comfortable in Go, Rust, Java, or C/C++
• You understand APIs, distributed systems, and why auth is never “just add auth”
• You take ownership, especially when things get weird

Extra credit if you’ve worked on:

• Admin platforms, IAM, or enterprise SaaS
• Certificates, identity systems, or observability
• Systems where flexibility vs. safety is a constant fight

Tech Stack

ngrok runs entirely on AWS. Engineers develop by using remote development tools and/or ssh to connect to 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.

Location

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.

Sponsorship

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.

Compensation

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,500 – $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-Remote

About the Customer Data Team

Our Customer Data team builds the systems that ensure customers see fair, clear billing and reliable consumption data. We handle billing, metering, limits, and usage tracking—the systems that make sure every byte is counted correctly and every invoice is accurate.

Our systems must be correct, explainable, and defensible under real-world conditions: traffic spikes, partial failures, customers changing behavior mid-stream, and someone always asks: "Why does my bill look like this?"

When things work, nobody notices. When they don't, suddenly everyone has opinions about distributed data systems. Is the bug due to caching? You'll be the one who actually knows.

What You’ll Actually Do

• Build the billing backbone: You'll maintain and evolve our billing and metering infrastructure—Stripe Orb integrations, usage aggregation systems, and everything that turns traffic into invoices. Accurate invoices. The kind customers don't dispute.
• Track everything that matters: You'll build event tracking pipelines for traffic events, session logging, and usage patterns. You'll develop traffic inspection systems for compliance and analytics. Every request counted, every session tracked, no "lost" data explaining why the numbers don't match.
• Own customer-visible usage and billing insights. Build and evolve the systems that turn raw product usage into clear, accurate, and trusted views of what customers are using and why they’re charged—eliminating billing confusion before it happens.
• Handle the infrastructure details: You'll manage IP metadata services and the systems that connect traffic patterns to customer accounts. You'll ensure billing reliability—accurate invoices, automated refund processing, and reconciliation that actually reconciles.
• Ship systems people trust: You'll work closely with product, platform, finance, and support. Finance will have questions. They always do. You'll make their day by actually having the data they need.

You Might Be a Great Fit If…

• You’ve built backend or data-heavy systems that were held to high standards of correctness
• You’re comfortable in a statically typed, compiled language such as Go, Rust, C++, or Java (with bonus points for Go)
• You’ve worked with event streams, usage data, or high-volume pipelines
• You enjoy thinking about data models, invariants, and failure modes
• You care about developer experience, including for people consuming your data
• You're the person people ping when the numbers don't add up and nobody else can explain why

Extra credit if you’ve worked on:

• Metering, billing, or pricing systems (but not limited to them)
• Event-driven or streaming architectures
• Customer-facing analytics or usage reporting
• Systems where small discrepancies become large conversations

Tech Stack

ngrok runs entirely on AWS. Engineers develop by using remote development tools and/or ssh to connect to 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.

Location

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.

Sponsorship

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.

Compensation

bout the Admin Team

Our Admin Engineering team builds the systems that decide who can access ngrok, what they can do, and how everything is configured.

We own identity, access control, and configuration at scale—users, certificates, service accounts, domains, policies. If it answers “who can do what?”, it’s our problem. When things work, nobody notices. When they don’t, people get locked out or something gets exposed that really shouldn’t be.

A lot of this work lives in the tension between power and safety. Customers want full control and APIs for everything. They also want guardrails and sane defaults. You’ll build systems that manage both—without making either side miserable.

What You’ll Actually Do

Build the control plane

Design and operate the services and APIs behind admin workflows—the layer that defines how ngrok behaves in production.

Own identity and access

Develop and evolve IAM/RBAC systems across users, certificates, and service accounts. If something can authenticate or authorize, you’ll touch it.

Make configuration scale

Build global configuration systems for domains, policies, and traffic behavior—flexible enough for automation, safe enough for humans.

Make debugging possible

Improve observability across admin workflows so we can answer “what changed?” without guessing or digging through logs for an hour.

Ship systems people rely on

Work with product and platform teams to deliver features that are stable, understandable, and actually usable in production.

Keep things from breaking (or worse)

Ensure admin systems stay scalable, reliable, and hard to misuse—because mistakes here tend to be very visible.

You Might Be a Great Fit If…

• You’ve built backend systems that needed to be correct and hard to misuse
• You’re comfortable in Go, Rust, Java, or C/C++
• You understand APIs, distributed systems, and why auth is never “just add auth”
• You take ownership, especially when things get weird

Extra credit if you’ve worked on:

• Admin platforms, IAM, or enterprise SaaS
• Certificates, identity systems, or observability
• Systems where flexibility vs. safety is a constant fight

Tech Stack

ngrok runs entirely on AWS. Engineers develop by using remote development tools and/or ssh to connect to 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.

Location

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.

Sponsorship

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.

Compensation

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,500 – $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-Remote

About the Agent Team

Our Agent team builds the software that sits at the edge of every ngrok connection. The Agent is what developers install, run, embed, and trust to expose their systems securely to the internet.

It’s the first thing customers touch and the last thing we want to debug at 3am.

The Agent must be fast, correct, and predictable under hostile conditions: flaky networks, broken configs, expired certs, overloaded laptops, CI environments held together by duct tape, and production traffic that does not care about your feelings.

When it works, nobody thinks about it.

When it doesn’t, it’s immediately obvious — and very public.

What You’ll Actually Do

• Build and evolve the ngrok Agent itself: You’ll work on the core agent that handles connection management, tunneling, authentication, and secure traffic forwarding. This is a high-performance networking system that must behave correctly across a wide range of environments and failure modes.
• Own reliability at the edge: You’ll design for latency, throughput, and correctness under real-world chaos—network partitions, transient failures, misconfiguration, and resource-constrained machines. When something goes wrong, the Agent should fail clearly, safely, and explainably.
• Develop SDKs and embeddable integrations: You’ll build and maintain SDKs and embedded agent components that other systems and products depend on. These need to be easy to integrate, hard to misuse, and stable over time.
• Make the system observable: You’ll improve diagnostics, logging, and metrics so we can understand what the Agent is doing in the wild. When customers ask “what happened?”, you’ll help make sure we can answer with facts instead of guesses.
• Ship software that runs everywhere: The Agent runs on developer laptops, servers, CI systems, containers, and occasionally very questionable hardware. You’ll ensure it behaves consistently across platforms and environments.
• Work with people who care about correctness: You’ll collaborate closely with product, platform, and support teams. When something breaks, you’ll help explain why. When something is confusing, you’ll help make it boring.

You Might Be a Great Fit If…

• You’ve built systems-level software that had to work under pressure
• You’re comfortable in Go, Rust, C/C++, or Java (bonus points for Go)
• You enjoy debugging things that “shouldn’t be possible”
• You think deeply about reliability, security, and performance
• You can reason about tradeoffs and explain them like a normal human
• You care about developer experience — not just correctness

Extra credit if you’ve worked on:

• Networking, proxies, or agents
• SDKs or embeddable runtimes
• Observability tooling
• Open-source systems people actually use

Tech Stack

ngrok runs entirely on AWS. Engineers develop by using remote development tools and/or ssh to connect to 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.

Location

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.

Sponsorship

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.

Compensation

bout the Admin Team

Our Admin Engineering team builds the systems that decide who can access ngrok, what they can do, and how everything is configured.

We own identity, access control, and configuration at scale—users, certificates, service accounts, domains, policies. If it answers “who can do what?”, it’s our problem. When things work, nobody notices. When they don’t, people get locked out or something gets exposed that really shouldn’t be.

A lot of this work lives in the tension between power and safety. Customers want full control and APIs for everything. They also want guardrails and sane defaults. You’ll build systems that manage both—without making either side miserable.

What You’ll Actually Do

Build the control plane

Design and operate the services and APIs behind admin workflows—the layer that defines how ngrok behaves in production.

Own identity and access

Develop and evolve IAM/RBAC systems across users, certificates, and service accounts. If something can authenticate or authorize, you’ll touch it.

Make configuration scale

Build global configuration systems for domains, policies, and traffic behavior—flexible enough for automation, safe enough for humans.

Make debugging possible

Improve observability across admin workflows so we can answer “what changed?” without guessing or digging through logs for an hour.

Ship systems people rely on

Work with product and platform teams to deliver features that are stable, understandable, and actually usable in production.

Keep things from breaking (or worse)

Ensure admin systems stay scalable, reliable, and hard to misuse—because mistakes here tend to be very visible.

You Might Be a Great Fit If…

• You’ve built backend systems that needed to be correct and hard to misuse
• You’re comfortable in Go, Rust, Java, or C/C++
• You understand APIs, distributed systems, and why auth is never “just add auth”
• You take ownership, especially when things get weird

Extra credit if you’ve worked on:

• Admin platforms, IAM, or enterprise SaaS
• Certificates, identity systems, or observability
• Systems where flexibility vs. safety is a constant fight

Tech Stack

ngrok runs entirely on AWS. Engineers develop by using remote development tools and/or ssh to connect to 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.

Location

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.

Sponsorship

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.

Compensation

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,500 – $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-Remote

About the Admin Team

Our Admin Engineering team builds the systems that decide who can access ngrok, what they can do, and how everything is configured.

We own identity, access control, and configuration at scale—users, certificates, service accounts, domains, policies. If it answers “who can do what?”, it’s our problem. When things work, nobody notices. When they don’t, people get locked out or something gets exposed that really shouldn’t be.

A lot of this work lives in the tension between power and safety. Customers want full control and APIs for everything. They also want guardrails and sane defaults. You’ll build systems that manage both—without making either side miserable.

What You’ll Actually Do

Build the control plane

Design and operate the services and APIs behind admin workflows—the layer that defines how ngrok behaves in production.

Own identity and access

Develop and evolve IAM/RBAC systems across users, certificates, and service accounts. If something can authenticate or authorize, you’ll touch it.

Make configuration scale

Build global configuration systems for domains, policies, and traffic behavior—flexible enough for automation, safe enough for humans.

Make debugging possible

Improve observability across admin workflows so we can answer “what changed?” without guessing or digging through logs for an hour.

Ship systems people rely on

Work with product and platform teams to deliver features that are stable, understandable, and actually usable in production.

Keep things from breaking (or worse)

Ensure admin systems stay scalable, reliable, and hard to misuse—because mistakes here tend to be very visible.

You Might Be a Great Fit If…

• You’ve built backend systems that needed to be correct and hard to misuse
• You’re comfortable in Go, Rust, Java, or C/C++
• You understand APIs, distributed systems, and why auth is never “just add auth”
• You take ownership, especially when things get weird

Extra credit if you’ve worked on:

• Admin platforms, IAM, or enterprise SaaS
• Certificates, identity systems, or observability
• Systems where flexibility vs. safety is a constant fight

Tech Stack

ngrok runs entirely on AWS. Engineers develop by using remote development tools and/or ssh to connect to 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.

Location

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.

Sponsorship

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.

Compensation

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,500 – $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