Technical Writer / Project Based
Location: Remote
About Estuary
Estuary is reshaping how the world moves data. Our right time data platform unifies CDC, batch, and streaming into one dependable system, eliminating the need to stitch together fragmented ETL and replication tools. We are also one of the first data infrastructure companies shipping into the AI agent stack. Our skills library plugs directly into Claude, Cursor, and other assistants, turning Estuary into a tool agents can actually use.
We help data teams build modern, real-time infrastructure that powers analytics, operations, and AI without the complexity and cost of legacy tools. Backed by top investors and led by experienced repeat founders in data infrastructure, we recently raised a $17M Series A led by M13.
As organizations shift toward right-time architectures, the market is moving fast, and we are too. We are looking for a contract technical writer who can translate this platform into deep, useful content that data teams actually want to read and that ranks for the queries our buyers run when they are evaluating tools.
The Role
This is a senior contract seat for a writer who can grasp technical concepts quickly and translate them into content that engineers respect. You will work directly with the VP Marketing, our SEO and growth marketing lead to produce technical blog content on data pipelines, streaming architecture, and the data infrastructure powering agentic and operational AI.
This is not a role for a generalist content writer who needs an engineer to translate every concept. We are looking for someone who can read a technical spec or sit in a 30-minute call with a product engineer and walk away ready to write. You will need strong opinions, the discipline to ship on agreed dates, and the ability to write clearly about complex infrastructure.
What You'll Do
- Rewrite and produce technical blog posts (typically 1,500–3,000 words)
- Build hands-on tutorials with working code and reproducible setups
- Produce evaluation guides and architectural comparison content
- Provide editorial polish on all deliverables
- Partner with our SEO and content leads to align deliverables with search intent and pillar strategy
What You Bring
- A portfolio of published technical writing that demonstrates depth and a distinct point of view
- The ability to grasp technical concepts quickly and explain them clearly. You can pick up a new system, read the docs, ask the right questions, and produce content that holds up under technical scrutiny
- Comfort writing about infrastructure and AI topics without hand-waving or filler
- Strong writing and editing chops: you can produce a tutorial, a deep dive, and a comparison piece without heavy editing
- Bias toward shipping: you move from a blank page to a publishable draft quickly and know when something is ready
- Self-directed working style and reliable turnaround on agreed deliverable dates
- Editorial judgment: you push back on jargon, hype words, and weak language
Bonus Points If You
- Have a data engineering, developer relations, or developer-facing engineering background
- Have worked at a data infrastructure, dev tools, or modern data stack company
- Have built or contributed to open source data infrastructure projects
- Have a conference talk, community-building, or DevRel track record
- Have written content that ranks for competitive technical search queries
- Have used AI tooling (Claude, ChatGPT, Cursor, perplexity) to accelerate research and drafting workflows
Why Estuary
- A category that is moving: the modern data stack is being rebuilt around real-time and AI, and we are positioned at the center of it
- Genuinely interesting technical surface area, with room to go deep on the topics you find most compelling
- Remote, project-based, and flexible by design
Engagement Details
- Contract, project-based with flexible hours
- Per-deliverable rate, scoped at kickoff based on length and complexity
- Fully remote, US-based or US-time-zone friendly preferred
- Immediate start
How to Apply
Send a short note, your rate expectations, and 2–3 writing samples that demonstrate technical depth.
















































