Technical Content Lead
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections that have real specific content. The posting includes many paragraphs. We need to extract content and format accordingly.
We must not repeat job title as heading. No Job ID. Remove boilerplate like cookie/navigation/legal/EEO etc. There's none.
We need to preserve all substantive information. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide sections: About the role (intro), Responsibilities (what you'll do), Requirements (what you need), Qualifications maybe overlapping with Requirements, Skills maybe separate, Benefits (compensation, remote, etc), Pay (compensation details), Schedule maybe not present. The posting mentions compensation band, fully remote, offices, tokens, etc. That's Benefits and Pay. Could combine Benefits and Pay? But we need separate sections only if content exists. We have compensation details: "$120,000-$130,000 / €110,000-€120,000 per year + equity". Also "Fully remote (US or EU-based), with offices in Brooklyn if you want one". "All the tokens you need, across all frontier models". "Real ownership, real impact, no micromanagement". "Colleagues in 12+ countries". Those are benefits. Could put Benefits section with those bullet points. Pay section could just have compensation line. But we could also combine. The instruction: Prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements, Benefits (including Pay). But they said use headings for Benefits, Pay, Schedule separately if content exists. Since we have Pay info, we could make a Pay section. Benefits section for other benefits. Schedule not present, so omit.
We need to avoid filler like "commensurate with experience". Not present.
Let's extract content.
About the role: The first paragraphs describe Soda, mission, role: "We're hiring one person to own content at Soda, end to end." Then description of what they'll do: website, technical blogs, webinars, product videos, own content and following, build system. Also reporting to co-founder, joining Growth team. Also mention what you might call yourself. Also mention why this is a real problem etc. We'll put that in About the role.
Responsibilities: Likely the bullet list of duties: "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." Also "You'll join the Growth team reporting to a co-founder." Also "Your own profile and following is part of how we'll know it works." Also "You'll write code every day". Also "You need to be able to write and you need to be able to build". Also "The engine has to write in distinct voices". Also "Your job is to get it out of their heads and onto the internet, at a volume that is only possible with a machine behind it." Also "Taste is the bar. Anti-slop is the whole point." Also "You'll write code every day, but this is not a software engineering job." Also "We're not hiring you to build product". Also "It's also not a traditional marketing or DevRel role". Also maybe list of responsibilities: building system, writing, coding, evaluating outputs, etc.
Requirements: list: "You can write, and you can tell good writing from bad: send us something you wrote that a technical audience actually read." "The most important line in this adSerious prompt engineering: multi-step LLM pipelines with structured outputs and evals, not chatting with a model. You know why the naive version produces slop" (that's weird formatting). Probably requirement: Serious prompt engineering: multi-step LLM pipelines with structured outputs and evals. "3+ years building things that go to market: technical content, growth engineering, marketing engineering, GTM engineering, DevRel, marketing ops, RevOps, or a founder background." "Enough code to be autonomous: Python or TypeScript, APIs, webhooks, a database." "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"
Good to Have: list but we may not need a separate section unless we want to include as part of Requirements? Could be separate "Qualifications" maybe. But we can treat Good to Have as part of Requirements or separate "Qualifications". The instruction: Use headings for Qualifications if content exists. We have Good to Have items. Could make a Qualifications section for those. Or we could incorporate them into Requirements. Better to have Requirements (mandatory) and Qualifications (good-to-have). Let's do that.
Skills: maybe not separate; we could omit if not distinct.
Benefits: list: "Compensation: $120,000-$130,000 / €110,000-€120,000 per year + equity - the same band wherever you live. We don't discount for geography" "Fully remote (US or EU-based), with offices in Brooklyn if you want one" "All the tokens you need, across all frontier models" "Real ownership, real impact, no micromanagement" "Colleagues in 12+ countries" Also maybe "Our Values" but that's not benefit. Could be separate but not required.
Pay: we could put compensation line there. But we already have compensation in Benefits. To avoid duplication, maybe put Pay section with compensation line, Benefits section with other benefits. Let's do that.
Schedule: not present, omit.
Now produce HTML fragment:
About the role
... paragraphs ...
Responsibilities
- ... items ...
Requirements
- ... mandatory items ...
Qualifications
- ... good-to-have items ...
Pay
Compensation: $120,000-$130,000 / €110,000-€120,000 per year + equity – same band worldwide, no geographic discount.
Benefits
- Fully remote (US or EU‑based), with optional office in Brooklyn.
- Access to all tokens needed across frontier models.
- Real ownership and impact, no micromanagement.
- Colleagues in 12+ countries.
We need to ensure we preserve all substantive information. Let's capture the About the role text: from "Data quality is the bottleneck..." up to "You'll join the Growth team reporting to a co-founder." plus maybe the "What you might call yourself." and "Why this is a real problem..." We'll combine into a few paragraphs.
Let's craft About the role paragraph(s):
Paragraph 1: "Data quality is the bottleneck of the AI era. Every Fortune 500 is trying to solve it. We're the team they call. Soda is the data quality layer for Disney, Ralph Lauren, CBRE, HelloFresh, 2K Games, and Nubank. Our open‑source engine, Soda Core, is used by companies like Tesla, Slack, Adyen, Walmart, and JPMC. The category is growing fast because AI doesn't work on bad data. We're hiring one person to own content at Soda, end to end. Soda's mission is to monitor the world's decisions. We're building the first Data & AI performance monitoring platform that spans data collection to automated decision‑making. Soda helps customers find, understand, and fix data quality issues."
Paragraph 2: "The Role: 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."
Paragraph 3: "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."
Paragraph 4: "Why this is a real problem and not a content calendar: The expertise is already in the building. Founders who have argued about this category for a decade. Customer engineers who spend their week inside broken pipelines at Fortune 500s. Customers who will tell you things nobody has published anywhere. Almost none of it gets written down, and what does get out is hand‑made, one piece at a time, by people who have other jobs. Your job is to get it out of their heads and onto the internet, at a volume that is only possible with a machine behind it. Taste is the bar. Anti‑slop is the whole point. An engine that ships slop faster has negative value, and most of them do. We're hiring for the judgment to look at an accurate, competent, lifeless draft and bin it – then work out what the pipeline did wrong and fix it. The engine has to write in distinct voices: a founder sounds nothing like a customer engineer, and the output should sound like them, not like a model. Your own profile and following is part of how we'll know it works. If it can't make you sound good, it won't make anyone else sound good either."
Paragraph 5: "What this is not: You'll write code every day, but this is not a software engineering job. We're not hiring you to build product, and if you're a backend, data, or platform engineer looking for your next engineering role, this isn't it. It's also not a traditional marketing or DevRel role: no agency to brief and no conference circuit."
That seems comprehensive.
Now Responsibilities: we can list bullet points:
- Own the end‑to‑end content process for Soda: website, technical blogs, webinars, product videos, and your own content/following.
- Build the system (workflows, pipelines, agentic workflows) that can produce this volume of content automatically.
- Write code daily (Python/TypeScript, APIs, webhooks, DB) to enable autonomous content generation.
- Evaluate LLM outputs, design multi‑step prompt engineering pipelines with structured outputs and evaluations to avoid slop.
- Shape the voice of the output to match different personas (founder, customer engineer, etc.).
- Collaborate with founders, customer engineers, and customers to extract undocumented expertise and turn it into publishable material.
- Continuously judge output quality, discard lifeless drafts, and improve the underlying pipeline.
- Operate independently in a distributed, async team across 12+ countries.
That captures.
Requirements (mandatory):
- Ability to write well and discern good writing from bad; provide a sample that a technical audience has actually read.
- Expertise in serious prompt engineering: multi‑step LLM pipelines with structured outputs and evaluations, not just chatting with a model; understanding why naïve approaches produce slop.
- 3+ years of experience building things that go to market (technical content, growth engineering, marketing engineering, GT
for prose. We need to decide sections: About the role (intro), Responsibilities (what you'll do), Requirements (what you need), Qualifications maybe overlapping with Requirements, Skills maybe separate, Benefits (compensation, remote, etc), Pay (compensation details), Schedule maybe not present. The posting mentions compensation band, fully remote, offices, tokens, etc. That's Benefits and Pay. Could combine Benefits and Pay? But we need separate sections only if content exists. We have compensation details: "$120,000-$130,000 / €110,000-€120,000 per year + equity". Also "Fully remote (US or EU-based), with offices in Brooklyn if you want one". "All the tokens you need, across all frontier models". "Real ownership, real impact, no micromanagement". "Colleagues in 12+ countries". Those are benefits. Could put Benefits section with those bullet points. Pay section could just have compensation line. But we could also combine. The instruction: Prefer a few substantive sections over many thin ones. So maybe we have About the role, Responsibilities, Requirements, Benefits (including Pay). But they said use headings for Benefits, Pay, Schedule separately if content exists. Since we have Pay info, we could make a Pay section. Benefits section for other benefits. Schedule not present, so omit. We need to avoid filler like "commensurate with experience". Not present. Let's extract content. About the role: The first paragraphs describe Soda, mission, role: "We're hiring one person to own content at Soda, end to end." Then description of what they'll do: website, technical blogs, webinars, product videos, own content and following, build system. Also reporting to co-founder, joining Growth team. Also mention what you might call yourself. Also mention why this is a real problem etc. We'll put that in About the role. Responsibilities: Likely the bullet list of duties: "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." Also "You'll join the Growth team reporting to a co-founder." Also "Your own profile and following is part of how we'll know it works." Also "You'll write code every day". Also "You need to be able to write and you need to be able to build". Also "The engine has to write in distinct voices". Also "Your job is to get it out of their heads and onto the internet, at a volume that is only possible with a machine behind it." Also "Taste is the bar. Anti-slop is the whole point." Also "You'll write code every day, but this is not a software engineering job." Also "We're not hiring you to build product". Also "It's also not a traditional marketing or DevRel role". Also maybe list of responsibilities: building system, writing, coding, evaluating outputs, etc. Requirements: list: "You can write, and you can tell good writing from bad: send us something you wrote that a technical audience actually read." "The most important line in this adSerious prompt engineering: multi-step LLM pipelines with structured outputs and evals, not chatting with a model. You know why the naive version produces slop" (that's weird formatting). Probably requirement: Serious prompt engineering: multi-step LLM pipelines with structured outputs and evals. "3+ years building things that go to market: technical content, growth engineering, marketing engineering, GTM engineering, DevRel, marketing ops, RevOps, or a founder background." "Enough code to be autonomous: Python or TypeScript, APIs, webhooks, a database." "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" Good to Have: list but we may not need a separate section unless we want to include as part of Requirements? Could be separate "Qualifications" maybe. But we can treat Good to Have as part of Requirements or separate "Qualifications". The instruction: Use headings for Qualifications if content exists. We have Good to Have items. Could make a Qualifications section for those. Or we could incorporate them into Requirements. Better to have Requirements (mandatory) and Qualifications (good-to-have). Let's do that. Skills: maybe not separate; we could omit if not distinct. Benefits: list: "Compensation: $120,000-$130,000 / €110,000-€120,000 per year + equity - the same band wherever you live. We don't discount for geography" "Fully remote (US or EU-based), with offices in Brooklyn if you want one" "All the tokens you need, across all frontier models" "Real ownership, real impact, no micromanagement" "Colleagues in 12+ countries" Also maybe "Our Values" but that's not benefit. Could be separate but not required. Pay: we could put compensation line there. But we already have compensation in Benefits. To avoid duplication, maybe put Pay section with compensation line, Benefits section with other benefits. Let's do that. Schedule: not present, omit. Now produce HTML fragment:
About the role
... paragraphs ...
Responsibilities
- ... items ...
Requirements
- ... mandatory items ...
Qualifications
- ... good-to-have items ...
Pay
Compensation: $120,000-$130,000 / €110,000-€120,000 per year + equity – same band worldwide, no geographic discount.
Benefits
- Fully remote (US or EU‑based), with optional office in Brooklyn.
- Access to all tokens needed across frontier models.
- Real ownership and impact, no micromanagement.
- Colleagues in 12+ countries.