Senior Developer Educator

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.

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, differentiated product story.
• Letting a model write for you. (More on that below.)
• Parroting messaging frameworks. You'll help build them.

Right now, we're betting that the most important thing we can do is change how developers think about ngrok. Most of the developers who'd buy our infrastructure products already have an ngrok account. They just don't reach for us when the problem shows up. Brand-defining work is how we close that gap, and this role exists because we want to put more of our team's time into it, not less.

One of our core beliefs is that every default, interaction, and piece of content should earn its place. For you, that means quality over cadence. We'd rather you disappear for two weeks and come back with a piece that changes how people think about a problem than ship five things nobody remembers. Great education is useful on its own, whether or not the reader ever signs up, and we always aim to give our audience more than we take from them.

We also want you to be known for your work: not as an ngrok spokesperson reciting talking points, but as a sharp voice with strong opinions about what good developer content looks like. If you want to become a recognized voice in developer tooling or in the craft of teaching technical ideas, we'll back you fully.

We use AI a lot: for research, for getting oriented in unfamiliar code, and for feedback on a draft before a human reads it. We don't use it to write. Writing is how we work out what we think, and we care about the craft too much to hand off the sentences. We hope you feel the same way.

None of this is new for us. ngrok has been sweatin' the small stuff since before "developer experience" was cool. We just think it should apply to our content, too.

• A writer's heart. You care about the craft of writing, you read widely, and you have opinions about sentences (yours and everyone else's).
• A builder's instinct and an educator's clarity. You don't just explain things; you make them tangible.
• Deep technical knowledge of AI/ML or networking and infrastructure, or at least a serious curiosity about whichever one you don't know yet.
• An eagerness to learn. Our products span tunnels, gateways, deployments, and GPUs, and nobody here knew all of it on day one.
• A body of work that shows taste and range: blog posts and launches, sure, but also tools, talks, side projects, or an interactive thing. You reach for whatever shape an idea demands.
• Experience working directly with product and engineering. You can pull the thing that matters out of a sprint review and turn it into something developers actually want to read.
• Strong opinions about how other dev tools companies do content: who does it well, who phones it in, and what you'd do differently.
• A chronically online streak (the good kind). You know what's on Hacker News today, which threads on X and Bluesky are worth reading, and which newsletters developers actually open.
• Thick skin and a sharp eye. You can dish out critique as well as you take it, and you know both make the work better.
• Experience as a full-stack or backend developer, or in infrastructure or AI, so your technical writing rings true to developers and DevOps/platform engineers.
• Built something with AI agents and LLMs, and have a clear sense of where the tools help and where they don't.
• A high bar for quality. You've killed your own drafts because they weren't good enough, and you'd rather publish nothing than publish something mediocre.
• A portfolio of work you're proud of. Send us links!
• An active ngrok account. (We won't check. Probably.)

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. 

At this time, ngrok is unable to provide visa sponsorship for this position. US Applicants must be authorized to work in the United States on a permanent, ongoing basis without the need for current or future sponsorship.

Senior Developer Educator, Video

• Tier 1 (SF, LA, Seattle, NYC): $160,000 – $200,000
• Tier 2 (rest of US): $147,200 – $184,000

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