> Markdown version of [/jobs/ext/2963030-technical-content-lead](https://www.wearedevelopers.com/jobs/ext/2963030-technical-content-lead). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Technical Content Lead

- **Company:** STUDIO ONE TO ONE
- **Location:** New York, NY, United States (Remote available)
- **Experience:** Expert
- **Salary:** $120,000.0 - $130,000.0
- **Contract:** Permanent contract
- **Skills:** Application Programming Interfaces (APIs), Databases, Programming Tools, Data Intelligence, Python (Programming Language), Open Source Technology, DataOps, TypeScript, Data Management, Webhooks
- **Published:** September 17, 2026
- **Apply:** https://www.careerjet.com/jobad/us292cc2f84600a6fff1aa212a8ab1a1d9

## About the Role

What you might call yourself. Content engineer, technical content marketer, growth engineer, marketing engineer, GTM engineer, developer advocate, technical writer who got bored, or nothing in particular. We've seen this job posted under every one of those. We don't care what's on your CV. You need to be able to write and you need to be able to build, and almost nobody can do both., * You've grown a technical audience of your own: newsletter, blog, LinkedIn, open source, YouTube.

 * Content, growth, or DevRel in data, developer tools, or infrastructure.
 * Agentic workflows shipped to real users: MCP servers, Claude skills, tool-using agents.
 * You can shoot and cut video yourself.
 * Data quality, data management, or data observability industry experience.

## Description

The website. Technical blogs, webinars, and product videos. Your own content and following.
One person cannot hand-make all of that. So you'll build the system that can. That isn't a stretch goal or a second phase - we don't think the job exists without it.
You'll join the Growth team reporting to a co-founder., * Enough code to be autonomous: Python or TypeScript, APIs, webhooks, a database. Nothing should be blocked waiting for an engineer. We build agentically here - Claude Code, MCP servers, and agent skills are the daily workflow.

 * Enough data fluency to be credible: you're writing for Staff Data Engineers and CDOs. You can hold your own on pipelines, data quality, and warehouses.
 * Generalist instinct: you find the constraint and fix it, and you'd rather build the workflow than do the task fifteen more times.
 * Independence: you don't need hand-holding in a distributed, async team across 12+ countries.
 * Fluent English.