Software Engineer III/Senior, Customer Data

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.

• 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’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

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.

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.

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.

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

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.

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.

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