Software Engineer III/Senior, AI Gateway

ngrok is an all-in-one cloud networking platform that secures, transforms, and routes traffic to services running anywhere. The role involves building and evolving the AI Gateway, managing AI traffic policies, and ensuring the observability of AI behavior for customers.

Responsibilities:

• 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

Requirements:

• Comfortable in a statically typed, compiled language such as Go, Rust, C++, or Java (with bonus points for Go)
• Worked with AI/LLMs and can appreciate their unique brand of edge-cases
• Care about developer experience and thoughtful abstractions
• Enjoy defining system behavior, not just plumbing
• Thought about retries, limits, and costs before being asked
• Like systems that move complexity from the user to the system
• AI platforms or inference infrastructure
• API gateways with product-level opinions
• Usage limits, quotas, or billing-adjacent systems
• Customer-facing observability tools