About ngrok Inc.

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.

A few things you should know:

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.

About the Security Team

Security at ngrok is being built from the ground up, and this role is the foundation. ngrok sits at a uniquely sensitive position in the internet stack: traffic flows through us, and the developers and companies who rely on us trust us with that. As our first dedicated Security Engineer, you won't be inheriting a sprawling program or a backlog of someone else's decisions. You'll be defining how security works here — partnering closely with engineering, infrastructure, and leadership to build automated guardrails, opinionated defaults, and self-service tooling that scale with the team rather than slow it down. The threat landscape is shifting fast, and we want a security posture we're proud to stand behind.

What You’ll Actually Do

Audit the current state of security tooling, pipeline coverage, cloud posture, and detection capabilities, and turn that into a prioritized security roadmap tied to ngrok's business objectives
Ship developer-facing security tooling: automated checks in CI/CD, secrets scanning, dependency vulnerability tracking, and secure-by-default libraries that make the right choice the easy choice
Run a structured risk assessment across product and infrastructure to document what we know, what we don't, and what needs to change
Establish guardrails for how we use AI in our engineering pipeline — policies and tooling that let us move fast without introducing new risk classes
Stand up baseline detection and response: log coverage, alerting, and a documented incident response process
Own the security engineering program end-to-end over time — clear ownership, documented controls, meaningful metrics, and an internal security platform (reusable libraries, self-service tooling, automation) that reduces the security burden on every engineer

You Might Be a Great Fit If…

You've worked in a security engineering role where you shipped tooling, built automation, or owned security infrastructure — not just reviewed it
You have strong engineering fundamentals and are comfortable writing quality code in Go or Java, Rust, C, C++
You've built internal security platforms or developer-facing security tooling
You know how to integrate security checks into CI/CD pipelines without slowing teams down
You have hands-on experience with cloud security, particularly AWS (IAM, VPC, CloudTrail, GuardDuty)
You understand AI/ML security risks like prompt injection, insecure code generation, and LLM-assisted attack vectors
Bonus Points:
You've done detection engineering — writing detection rules, tuning signals, reducing alert fatigue
You've secured networking or developer infrastructure products

Tech Stack

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.