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.
What you'll actually do
You'll take a complicated technical idea (networking, distributed systems, GPUs, whatever's genuinely hard) and turn it into something that makes developers stop scrolling and think, huh, ngrok made that? It might be a deep technical post, an interactive web experience, a video, a CLI demo, a small open source project, or a format nobody's tried yet. We don't optimize for medium. We optimize for whether the work changes how developers think about ngrok.
You'll work with Joel, Annie, Ryan, and SG (our content team!) on the work that defines ngrok's brand at the technical level. Think Annie's Compression is prediction . We want more of that, in more shapes.
First and foremost, you're a writer. Writing is the heart of this job, even when the finished piece is a video or an interactive page, because that's where the thinking happens. But great brand work at a dev tools company also means time with the product. We don't want someone who can write about ngrok. We want someone who builds from inside ngrok.
Day to day, you'll:
Produce brand-defining work. We’re looking for the pieces that get shared by people we don't know, land in TLDR and on Hacker News, and get read on a Saturday morning by someone whose taste you respect. We always have a queue of next bets, and you'll help pick them.
Choose the right medium for each idea. Sometimes that's a 6,000-word deep dive. Sometimes it's an interactive page that lets a developer feel a concept, a skill file for their agent, or a weekend side project. You pick whatever makes the idea land.
Give and get honest critique. Everything here runs through real feedback loops, and we want someone who gives constructive critique on other people's work and genuinely wants it on their own. Our bar is simple: would you be proud to share this from your personal account? If not, it doesn't ship.
Study how other people change minds. An outdated picture of what ngrok is remains our public enemy No. 1. You'll keep your ear to the ground, find where technical conversations actually happen, and bring those patterns back home.
Make ngrok an authority on networking, infrastructure, and AI. When developers want to understand how these things really work, we want them to end up reading something you made.
What you won't spend your time on
You won't be:
Creating content just for the algorithm (SEO, AI citations, or otherwise). We use those signals to inform and tune our work, not to steer it.
Hitting a quota of X pieces a week. We work on longer timelines that put impact ahead of cadence.
Cranking out launch posts on a schedule. We ship product launches together as a team, but this role doesn't carry them.
Operating as PR for product.
Writing "Top 10" listicles or thought leadership that anyone could've written about anything.
Chasing trends you can't connect to a lasting,…