Marketing Lead
` for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
- Use `- ` for any list of duties/requirements/benefits
- Use `
` for prose
- Do NOT repeat the job title as a heading (page already shows it)
- Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short `
` or drop it
- Preserve ALL substantive information; do NOT invent or summarize away detail
- Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
- IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them
- Prefer a few substantive sections over many thin ones
- Output ONLY the HTML fragment — no /, no markdown code fences
2. **Analyze the Input Text:**
The input is a job posting for SageOx. Let me extract the meaningful sections and content, removing boilerplate.
Key parts:
- Company intro: SageOx, well-funded early-stage, AI shaping the world, future of work is human and collaborative
- Role exists: First marketer at SageOx, no marketing team, no agency, no brand book. AI-pilled marketer, creativity, push through noise. Creating new product category. Social media (X, LinkedIn, Reddit, Hacker News, Discords/Slacks like Claude Code, Cursor, Codex, MCP) and events (SF, Seattle, other builder hubs). Drive awareness measured by customer acquisition, engagement, ecosystem reach.
- Responsibilities/duties: Own voice on X/LinkedIn, publish weekly cadence, turn raw material into readable content, be presence where builders compare notes, run launches (HN, Product Hunt, coordinated push), amplify founders/team, bring outside-in signal, own event presence end to end, pick events in SF, Seattle, other hubs, decide how we show up (talk, demo, booth, dinner, sponsorship, or just being there), host own meetups/hackathons/workshops/dinners, systematize, measure, define good week, report, run experiments, use agents to scale, research/drafting/monitoring/reporting agent-assisted, build workflows, use SageOx daily and market from lived use
- How person operates: driven by curiosity, courageous, humble, embodies SageOx values, ships posts/events not plans, balances speed with taste, goal is right message to right builders, in age of AI slop means editing/synthesizing, comfortable with engineers/builders or skeptics, asks sharp questions, listens, changes direction, resourceful/creative, works well with founders/communicates progress, makes next decision clearer
- What We're Looking For: 2-7 years in developer marketing, community, DevRel, social, or events for technical product with builder audience. Title matters less than evidence: audiences grown, events run, what happened after. Mission alignment, lives and breathes the product, complete fluency with AI, personally grown an audience/community/channel, run events people wanted to come back to, technical enough to be credible (explain MCP server, demo product, follow engineer's answer), thinks deeply, communicates clearly, writes well, stand on own thinking, clarity, craft. Bonus if good on camera. Strong sense of ownership, resourceful/creative, great sense of direction/prioritization amid ambiguity. Cultural fit embodies SageOx values. Bonus: connected to builder scene in SF/Seattle/online, existing audience among builders, founder/early-employee experience, experience with open-source products or developer communities. Location: Seattle or San Francisco, in person, 5 days a week. Either city works, spend real time in both.
Boilerplate to remove: None really in the provided text, but I should check for any hidden. The text seems clean of EEO/legal boilerplate, but I'll ensure none slips in. Also remove "application instructions" if any, but the text seems to be the full posting.
Section mapping per rules:
- Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule
- But only include if real content exists
- Pay/Schedule/ Benefits: Not present in the posting. So I must NOT create them.
- Job title: Not to be repeated as heading. The posting doesn't explicitly give a job title in the text, but it's "Marketer" or "Marketing role". I should not add a heading for it.
- Job ID/requisition: Not present, so drop or fold into the HTML fragment.
` for prose - Do NOT repeat the job title as a heading (page already shows it) - Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short `
` or drop it - Preserve ALL substantive information; do NOT invent or summarize away detail - Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions - IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them - Prefer a few substantive sections over many thin ones - Output ONLY the HTML fragment — no /, no markdown code fences 2. **Analyze the Input Text:** The input is a job posting for SageOx. Let me extract the meaningful sections and content, removing boilerplate. Key parts: - Company intro: SageOx, well-funded early-stage, AI shaping the world, future of work is human and collaborative - Role exists: First marketer at SageOx, no marketing team, no agency, no brand book. AI-pilled marketer, creativity, push through noise. Creating new product category. Social media (X, LinkedIn, Reddit, Hacker News, Discords/Slacks like Claude Code, Cursor, Codex, MCP) and events (SF, Seattle, other builder hubs). Drive awareness measured by customer acquisition, engagement, ecosystem reach. - Responsibilities/duties: Own voice on X/LinkedIn, publish weekly cadence, turn raw material into readable content, be presence where builders compare notes, run launches (HN, Product Hunt, coordinated push), amplify founders/team, bring outside-in signal, own event presence end to end, pick events in SF, Seattle, other hubs, decide how we show up (talk, demo, booth, dinner, sponsorship, or just being there), host own meetups/hackathons/workshops/dinners, systematize, measure, define good week, report, run experiments, use agents to scale, research/drafting/monitoring/reporting agent-assisted, build workflows, use SageOx daily and market from lived use - How person operates: driven by curiosity, courageous, humble, embodies SageOx values, ships posts/events not plans, balances speed with taste, goal is right message to right builders, in age of AI slop means editing/synthesizing, comfortable with engineers/builders or skeptics, asks sharp questions, listens, changes direction, resourceful/creative, works well with founders/communicates progress, makes next decision clearer - What We're Looking For: 2-7 years in developer marketing, community, DevRel, social, or events for technical product with builder audience. Title matters less than evidence: audiences grown, events run, what happened after. Mission alignment, lives and breathes the product, complete fluency with AI, personally grown an audience/community/channel, run events people wanted to come back to, technical enough to be credible (explain MCP server, demo product, follow engineer's answer), thinks deeply, communicates clearly, writes well, stand on own thinking, clarity, craft. Bonus if good on camera. Strong sense of ownership, resourceful/creative, great sense of direction/prioritization amid ambiguity. Cultural fit embodies SageOx values. Bonus: connected to builder scene in SF/Seattle/online, existing audience among builders, founder/early-employee experience, experience with open-source products or developer communities. Location: Seattle or San Francisco, in person, 5 days a week. Either city works, spend real time in both. Boilerplate to remove: None really in the provided text, but I should check for any hidden. The text seems clean of EEO/legal boilerplate, but I'll ensure none slips in. Also remove "application instructions" if any, but the text seems to be the full posting. Section mapping per rules: - Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule - But only include if real content exists - Pay/Schedule/ Benefits: Not present in the posting. So I must NOT create them. - Job title: Not to be repeated as heading. The posting doesn't explicitly give a job title in the text, but it's "Marketer" or "Marketing role". I should not add a heading for it. - Job ID/requisition: Not present, so drop or fold into the HTML fragment.