Technical Content Lead
Soda · New York, NY · 1 mo ago
RemoteRemoteOTHR$120k–$130k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not boilerplate. Remove cookie/navigation/legal/EEO etc. Also remove application instructions (hiring process). So we need to extract content: The posting includes description about role, responsibilities, requirements, benefits, etc.
Let's parse.
First paragraph: "Data quality is the bottleneck..." etc. That's about company and mission. Could be "About the role" or "About the company". The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content.
We have "The Role" heading in original. That likely corresponds to "About the role". So we can put
.
Qualifications (Good to Have): list: "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". We'll list.
Benefits: includes compensation? Actually compensation is Pay. Benefits: "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", "Our Values ..."? Actually values separate. Also "Why you will love to join Soda" includes: "Be part of a transformation: data quality is having its moment, and we're at the front of it", "Ownership from day one: if you see a bottleneck, you remove it", "International culture: colleagues in 12+ countries", "Work on your own terms: fully remote, flexible hours", "Paid the same wherever you are: one band for the US and Europe, no geographic discount", "Your name on the work: you build your own audience on company time, and we want you to", "Direct line to the founders: how Soda talks about the category gets decided with you in the room". That's many benefits. We'll combine.
Pay: compensation line.
Schedule: maybe "Fully remote (US or EU-based), with offices in Brooklyn if you want one" and "Work on your own terms: fully remote, flexible hours". That's schedule.
Our Values: "We value freedom with responsibility, transparency, and a growth mindset. We avoid politics, have no tolerance for dishonesty, and value open and direct communication without judgment. We proactively bring up and address potential issues before they become critical, and we overcommunicate frequently. Working at Soda, you will have full autonomy to make impactful decisions."
We'll include as separate section.
Now we need to output HTML fragment only, no markdown fences.
We'll structure:
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not boilerplate. Remove cookie/navigation/legal/EEO etc. Also remove application instructions (hiring process). So we need to extract content: The posting includes description about role, responsibilities, requirements, benefits, etc.
Let's parse.
First paragraph: "Data quality is the bottleneck..." etc. That's about company and mission. Could be "About the role" or "About the company". The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content.
We have "The Role" heading in original. That likely corresponds to "About the role". So we can put About the role
then paragraphs describing role.
Then "What you might call yourself." etc. That's more about role description.
Then "Why this is a real problem..." etc. That's also role description.
Then "What this is not." etc.
Then "Requirements" heading present. So we can have Requirements
with list.
Then "Good to Have" heading present. Could be "Qualifications" or "Skills". The instruction says use headings for Qualifications, Skills, Benefits, Pay, Schedule. Good to Have could be "Qualifications" or "Skills". We'll decide: "Good to Have" likely corresponds to "Qualifications" or "Skills". Since they list items like grown technical audience, content growth, agentic workflows, video, industry experience. That's more like "Qualifications". We'll put Qualifications
.
Then "Benefits" heading present. So Benefits
with list.
Then "Our Values" heading present. Not in allowed list but maybe we could include as a section? The instruction says use headings for those specific ones; but we can include other sections if they have real content? It says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exclusive. However later: "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". So we can include other sections if they have real content. But we should prefer few substantive sections over many thin ones. The "Our Values" is substantive. Could include as a section with heading maybe "Our Values". But not in list; still okay? Might be okay. However they said "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the expected headings; but we could still use others if needed. Safer to stick to those headings. We could map "Our Values" into "About the role" or maybe not include. But it's substantive; maybe we can include as a separate section with heading "Our Values". I'd lean to include because it's real content and not filler. The instruction didn't forbid other headings, just gave examples. So include.
Also there is "❤️ Why you will love to join Soda" and "😡 What you might not love". Those are also substantive. Could be part of "Benefits" or separate. Could be "Benefits" and "Challenges". But we have only Benefits, Pay, Schedule. Could treat "Why you will love to join Soda" as Benefits. And "What you might not love" as maybe not a section; could be omitted? It's substantive but maybe we can incorporate into Benefits as pros/cons. However instruction: prefer few substantive sections over many thin ones. So we could combine them into Benefits section.
Also there is "Compensation: $120,000-$130,000 / €110,000-€120,000 per year + equity". That's Pay. So we need a Pay section.
Schedule: not mentioned; remote, flexible hours. Could be Schedule: "Fully remote (US or EU-based), with offices in Brooklyn if you want one" and "Work on your own terms: fully remote, flexible hours". That's schedule info. So we can include Schedule section.
Thus sections: About the role, Responsibilities (maybe we can combine role description), Requirements, Qualifications, Benefits, Pay, Schedule, Our Values (optional). But we need to avoid duplication.
Let's extract content for each.
About the role: The paragraph starting with "The Role" and following description until maybe "What you might call yourself." Actually "The Role" heading then 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." plus earlier mission description. We'll combine.
Responsibilities: Could be derived from "What you might call yourself." etc. But maybe we treat responsibilities as the bullet list of duties: building system, writing code, etc. However the posting doesn't have explicit bullet list of responsibilities; it's more narrative. We could still create a Responsibilities section with paragraphs describing responsibilities.
Requirements: Already have a "Requirements" heading with bullet list: "You can write, and you can tell good writing from bad: send us something you wrote that a technical audience actually read." then "Serious prompt engineering: multi-step LLM pipelines with structured outputs and evals, not chatting with a model." then "3+ years building things that go to market: technical content, growth engineering, marketing engineering, GTM engineering, DevRel, marketing ops, RevOps, or a founder background." then "Enough code to be autonomous: Python or TypeScript, APIs, webhooks, a database." then "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" then "Generalist instinct: you find the constraint and fix it, and you'd rather build the workflow than do the task fifteen more times" then "Independence: you don't need hand-holding in a distributed, async team across 12+ countries" then "Fluent English". We'll turn each into
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests those are the expected headings; but we could still use others if needed. Safer to stick to those headings. We could map "Our Values" into "About the role" or maybe not include. But it's substantive; maybe we can include as a separate section with heading "Our Values". I'd lean to include because it's real content and not filler. The instruction didn't forbid other headings, just gave examples. So include. Also there is "❤️ Why you will love to join Soda" and "😡 What you might not love". Those are also substantive. Could be part of "Benefits" or separate. Could be "Benefits" and "Challenges". But we have only Benefits, Pay, Schedule. Could treat "Why you will love to join Soda" as Benefits. And "What you might not love" as maybe not a section; could be omitted? It's substantive but maybe we can incorporate into Benefits as pros/cons. However instruction: prefer few substantive sections over many thin ones. So we could combine them into Benefits section. Also there is "Compensation: $120,000-$130,000 / €110,000-€120,000 per year + equity". That's Pay. So we need a Pay section. Schedule: not mentioned; remote, flexible hours. Could be Schedule: "Fully remote (US or EU-based), with offices in Brooklyn if you want one" and "Work on your own terms: fully remote, flexible hours". That's schedule info. So we can include Schedule section. Thus sections: About the role, Responsibilities (maybe we can combine role description), Requirements, Qualifications, Benefits, Pay, Schedule, Our Values (optional). But we need to avoid duplication. Let's extract content for each. About the role: The paragraph starting with "The Role" and following description until maybe "What you might call yourself." Actually "The Role" heading then 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." plus earlier mission description. We'll combine. Responsibilities: Could be derived from "What you might call yourself." etc. But maybe we treat responsibilities as the bullet list of duties: building system, writing code, etc. However the posting doesn't have explicit bullet list of responsibilities; it's more narrative. We could still create a Responsibilities section with paragraphs describing responsibilities. Requirements: Already have a "Requirements" heading with bullet list: "You can write, and you can tell good writing from bad: send us something you wrote that a technical audience actually read." then "Serious prompt engineering: multi-step LLM pipelines with structured outputs and evals, not chatting with a model." then "3+ years building things that go to market: technical content, growth engineering, marketing engineering, GTM engineering, DevRel, marketing ops, RevOps, or a founder background." then "Enough code to be autonomous: Python or TypeScript, APIs, webhooks, a database." then "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" then "Generalist instinct: you find the constraint and fix it, and you'd rather build the workflow than do the task fifteen more times" then "Independence: you don't need hand-holding in a distributed, async team across 12+ countries" then "Fluent English". We'll turn each into
About the role
... paragraphs ...
Responsibilities
... maybe combine role duties ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
- ... ...
Pay
Compensation: $120,000-$130,000 / €110,000-€120,000 per year + equity - the same band wherever you live. We don't discount for geography.
Schedule
Fully remote (US or EU-based), with offices in Brooklyn if you want one. Work on your own terms: fully remote, flexible hours.
Our Values
We value freedom with responsibility, transparency, and a growth mindset. We avoid politics, have no tolerance for dishonesty, and value open and direct communication without judgment. We proactively bring up and address potential issues before they become critical, and we overcommunicate frequently. Working at Soda, you will have full autonomy to make impactful decisions.
We need to ensure we preserve all substantive info. Also include mention of mission etc in About the role. Let's craft About the role paragraph(s): From start: "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." Then after that: "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." We can combine into one or two paragraphs. Responsibilities: Could be derived from "What you might call yourself." etc. But maybe we can treat responsibilities as the description of what you'll do: building system