Software Engineer III/Senior, Customer Data

About ngrok Inc.

ngrok is an all-in-one cloud networking platform that secures, transforms, and routes traffic to services running anywhere. Instead of cobbling together nginx, NLBs, VPNs, model routers, and oodles other tools, developers solve every networking problem with one gateway. Doesn’t matter if they’re sharing localhost or running AI workloads in production.

We're trusted by more than 9 million developers at companies like GitHub, Okta, HashiCorp, and Twilio. What started as a way to put your local app on a public URL has grown into a universal gateway for API delivery, AI inference, device fleets, and site-to-site connectivity. It’s the same ngrok that millions of developers have loved and leaned on every day for years, now with the power to run production traffic at scale.

A few things you should know:

• Our mascot is a rock
• We are obsessed with our pets, Viper sunglasses and Bufo (yes, the toad)
• We have a designated Chief Emoji Officer - they are vital to our success!
• We like software that’s serious and culture that’s not

Most people skim to 'requirements' and bounce. You're actually reading this. That's the kind of thoroughness we respect, or you're just procrastinating. Either way, same same and you should keep reading.

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.