About Trigger.dev

Trigger.dev is the platform for running reliable AI agents and workflows. Developers use it to build, deploy, and scale production systems with built-in tools for orchestration, scheduling, monitoring, and debugging.

Our Cloud product is a managed service where we deploy our users' code and auto-scale from zero to millions of executions. Today, we serve thousands of teams building AI apps and agents, handling hundreds of millions of executions per month.

About the position

We're looking for a Technical Content Engineer to help us become top-of-mind for developers building AI agents. This is a hybrid role for someone who actually builds with code and writes for an audience - not a marketer who can read TypeScript, and not an engineer who occasionally blogs, but someone who treats content as a craft and ships it with the same rigour as production code.

You'll own technical content end to end: strategy, production, distribution, and measurement. You'll build with our product, ship things alongside our engineering team, and turn what you learn into blog posts, video, demos, and tweet threads that the AI agent community actually wants to read. You'll also work directly with our founders to help shape and produce content that goes out under their names.

This is a senior IC role. You'll be our first dedicated content hire, so the strategy is yours to define.

What you'll be doing

You'll do a variety of things including:

Producing technical content. Blog posts, tutorials, video, tweet threads, demo apps - whatever format best lands the idea. The bar is content that gets read, shared, and converts developers into users.
Owning content strategy. You'll decide what we should be writing about, which channels we should be on, what success looks like, and how often we should ship. You'll communicate that plan to the rest of the team and adjust as we learn.
Building with the product. You'll write real TypeScript on top of Trigger.dev - sample apps, integrations, reference implementations - both because it's some of our best content and because you can't write credibly about something you don't use.
Supporting founder content. You'll work with Matt and the team to produce posts, threads, and longer pieces that go out under their own names. Some of this is editing, some is ghost-writing, all of it is collaborative.
Measuring and iterating. Setting up conversion tracking, running A/B tests on content, looking at what worked and what didn't, and adjusting. We want a feedback loop, not a publishing calendar.
Reading the room on our audience. The dev tools and AI agent crowd has a specific sensibility - technical, informal, a bit irreverent. You should already get it.
Shaping how we tell our story. What we sound like, what we're known for, what we don't bother saying - you'll influence all of it.

Requirements

You really need to have:

Strong TypeScript skills. You can ship real applications, not just snippets. Our stack is Node/TypeScript and you'll be building demos and reference apps on top of it.
A track record of external technical content that has performed. Public examples we can read, watch, or scroll through - blog posts, tweet threads, YouTube videos, talks. We care more about evidence of work that landed than what your job title was.
Fluency with the current AI tooling landscape. You build with AI agents and the surrounding stack, you understand where Trigger.dev fits, and you can hold a credible conversation with the developers we're trying to reach.
Strategic instincts alongside production chops. You can write the blog post, but you can also tell us which blog posts we should be writing, what channels we should be

Trigger.dev

Open Vacancies (1)

Technical Content Engineer