At a Glance
- Tasks: Create engaging technical content that resonates with developers in the AI space.
- Company: Join a fast-paced, innovative startup focused on AI agents and workflows.
- Benefits: Enjoy flexible working, generous vacation, and a supportive learning environment.
- Other info: Be part of a small, autonomous team that values open-source contributions.
- Why this job: Shape the future of AI content while collaborating with founders and engineers.
- Qualifications: Strong TypeScript skills and a proven track record in technical content creation.
The predicted salary is between 60000 - 80000 £ per year.
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
- 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 on, and what we should measure.
- Strong written communication and high EQ. You can work independently and still keep the rest of the team in the loop on what you're shipping, why, and how it's tracking. You can take feedback in a public channel without bristling, and give it the same way.
You’ll be an amazing fit if you have:
- An existing audience on Twitter/X, YouTube, or a personal blog in the developer or AI space.
- Previously worked in-house at a dev tools, dev infra, or AI infra company in a content, DevRel, or growth-engineering capacity.
- Experience producing content that has gone viral or driven measurable signups for a product.
- A proven track record of contributing to open source projects.
- Comfort on camera (video, YouTube, screencasts).
- Previously been a founder, indie hacker, or built and grown your own product.
About the team
We are a small team with a flat hierarchy. We encourage continuous learning and personal development. Everyone operates autonomously; we trust you to get the job done, but to also quickly raise your hand if you need help. We care about our customers and the open-source community. Being a start-up, the work is challenging and fast-paced, but we also understand the importance of taking time off to recharge. Working at a Commercial Open Source Software company is more than just shipping content. We have an active community on Discord and GitHub. Everyone on the team helps customers, reviews PRs, and creates issues.
Salary
We use PostHog's salary calculator to benchmark fair and transparent compensation, which varies based on employee location and level of experience.
Benefits
- Generous, transparent compensation and equity - We hire the best talent and pay to reflect that. We also offer equity as a way to ensure everyone is invested in the success of the company.
- Async working - Need a heads-down day or meeting-free days to stay productive? No problem!
- Home office - We will help provide equipment for a comfortable setup so you're as productive at home as you are in the office.
- Generous vacation - We believe it's important to take time off. We encourage you to take your 25 days vacation excluding national holidays, plus sick leave and generous parental leave.
- Training budget - An annual budget to contribute towards learning such as purchasing books, an Audible subscription or online courses.
- Pension and 401k contributions - Enroll in our company pension scheme or we'll contribute directly to your private pension.
Our values
- We are proud to be open source - We believe in the open source community and building a great free-to-use product. We encourage community contributions and are public about what we are building.
- We ship uncomfortably fast - As a startup, moving fast is key. We are pragmatic about what we build, when we build it, and value iterative development above all.
- Working autonomously - We don't tell you what to do. We decide as a team what will have the biggest impact for our customers and prioritise what we work on from that.
Interview process
- Application - We'll review your application and the content examples you share with us.
- Screening call - A chat about your background, the kind of content you've shipped, and what you're looking for next.
- Hiring manager call - A deeper conversation about your work, your view on content strategy, and how you'd approach the role.
- Paid task day - You'll spend a paid day working on a real piece of content or strategy artefact with us, then walk us through your thinking with the team.
- Final interview - A call with a couple of members of the wider team to answer any remaining questions and align on culture fit.
- References & offer - If everyone is happy, we'll make you an offer to join us.
If this sounds like your dream job, we can't wait to hear from you. If you're not sure that you exactly fit these requirements, get in touch anyway!
Technical Content Engineer employer: Trigger.dev
At Trigger.dev, we pride ourselves on fostering a dynamic and inclusive work culture that empowers our employees to thrive. As a Technical Content Engineer, you'll enjoy generous benefits including flexible working arrangements, a supportive training budget for continuous learning, and the opportunity to shape content strategy alongside our founders. Our commitment to open-source values and a collaborative environment ensures that your contributions will have a meaningful impact in the rapidly evolving AI landscape.
StudySmarter Expert Advice🤫
We think this is how you could land Technical Content Engineer
✨Tip Number 1
Network like a pro! Reach out to folks in the industry, attend meetups, and engage in online communities. The more connections we make, the better our chances of landing that dream role.
✨Tip Number 2
Show off your skills! Create a portfolio that highlights your best work. Whether it's blog posts, videos, or demos, let your content speak for itself. We want to see what you can do!
✨Tip Number 3
Be proactive! Don’t just wait for job openings to pop up. Reach out directly to companies you admire, like Trigger.dev, and express your interest. Sometimes, the best opportunities come from a simple message.
✨Tip Number 4
Prepare for interviews by practising common questions and showcasing your knowledge about the company. We need to show that we’re not just a good fit for the role, but also for the team culture!
We think you need these skills to ace Technical Content Engineer
Some tips for your application 🫡
Show Your Technical Skills:Make sure to highlight your TypeScript skills in your application. We want to see real examples of your work, so include links to projects or content that showcase your coding prowess and how you’ve used it to create engaging technical content.
Craft Engaging Content Samples:When applying, include samples of your previous technical content. Whether it's blog posts, videos, or tweet threads, we’re looking for evidence that your content resonates with developers. Make it clear how your work has driven engagement or conversions.
Define Your Content Strategy:In your application, share your thoughts on what content topics you think are important for our audience. We want to know how you would approach content strategy and what channels you believe we should focus on to reach developers effectively.
Be Authentic and Informal:Remember, the dev tools and AI agent crowd appreciates a bit of irreverence. Let your personality shine through in your application. We’re looking for someone who can communicate in a relatable way, so don’t be afraid to be yourself!
How to prepare for a job interview at Trigger.dev
✨Know Your Tech Inside Out
As a Technical Content Engineer, you need to be comfortable with TypeScript and the AI tooling landscape. Brush up on your coding skills and be ready to discuss how you've used them in past projects. Show that you can not only write about tech but also build with it.
✨Showcase Your Content Portfolio
Bring along examples of your previous work that have performed well. Whether it's blog posts, videos, or tweet threads, make sure they highlight your ability to engage developers. This is your chance to prove that you can create content that resonates with the audience.
✨Be Ready to Discuss Strategy
This role involves owning the content strategy, so come prepared to share your thoughts on what topics are hot right now and how you would approach content distribution. Think about what success looks like for content and how you'd measure it.
✨Embrace Collaboration
You'll be working closely with the founders and the engineering team, so demonstrate your ability to collaborate effectively. Be open to feedback and show that you can communicate your ideas clearly while also valuing input from others.