Field Marketing & Partnerships Associate

We need to output HTML fragment with sections: About the role? Actually the posting includes "The Problem", "The Role", "What You’ll Do", "You Might Be a Fit If…", "Requirements", "Nice to Have", "Compensation", "Benefits", "The Process", "To Apply". We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we should map content accordingly. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we need to decide which sections to include based on actual content. We must not repeat job title as heading. We must not put Job ID etc. We must include a section only when posting has real, specific content for it. So we need to extract content for each relevant heading. We have: - About the role: could be "The Role" paragraph describing reporting, etc. That's a description. - Responsibilities: "What You’ll Do" bullet list. - Requirements: "Requirements" bullet list. - Qualifications: maybe "You Might Be a Fit If…" could be qualifications? Or "Nice to Have" could be qualifications? The instruction says we can use Qualifications heading if we have content. We have "You Might Be a Fit If…" which lists traits; could be considered Qualifications. Also "Nice to Have" could be Skills? Actually Skills heading could be for skills. But we can decide to include Qualifications for the "You Might Be a Fit If…" and Skills for "Nice to Have". However we need to avoid thin sections. Let's see content: "You Might Be a Fit If…" includes bullet points: High agency, Energized by building from zero, think in simple systems, experienced in high-pace environments (~2 years in field marketing, partnerships, growth, BD, GTM, or startup roles, with real ownership already), want serious ownership and career capital, etc. That's substantive. "Nice to Have" includes: Experience in insurance, fintech, or regulated industries; Prior work with founders or small teams; Familiarity with AI/automation tools and workflows; Prior startup or 0→1 experience. That's also substantive. Compensation: Salary range $125,000 - $150,000 + performance bonuses & equity. Also location: San Francisco, in-office. That's Pay. Benefits: Health, dental, and vision insurance; Commuter benefits; Team meals and snacks. Schedule: Not explicitly mentioned; maybe travel heavy, but schedule not given. We should not create Schedule unless stated. So omit. Process: "The Process" includes steps: Lead screen, Partnerships screen, On-site day. Could be a section but not in the list of headings. The instruction only mentions those example headings, but we can include other headings? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings for sections; but we could also include other headings if needed? Safer to stick to those headings. However we have "The Process" and "To Apply" which are not in the list. Should we include them? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but says use

for section headings (e.g ...). It might be okay to use other headings as needed, but better to map to given headings. However "The Process" and "To Apply" are substantive; we could include them as sections with appropriate headings like "Process" and "Application". But the instruction says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, just gives examples. I'd include them as headings like "Process" and "How to Apply". But to be safe, maybe we can incorporate them under existing headings? For example, "The Process" could be under "About the role"? Not ideal. Better to include as its own heading. We must not repeat job title as heading. No job title given explicitly, but we can ignore. We must remove boilerplate: cookie/navigation/legal/EEO etc. Not present. We must preserve all substantive information. We must not invent or summarize away detail. We must not create Pay/Schedule/Benefits sections unless posting actually states them. We have Pay (Compensation) and Benefits stated. Schedule not stated, so omit. We must prefer a few substantive sections over many thin ones. So we could combine some. Potential sections: - About the role (from "The Role" paragraph) - Responsibilities (from "What You’ll Do") - Requirements (from "Requirements") - Qualifications (from "You Might Be a Fit If…") - Skills (from "Nice to Have") - Benefits (from "Benefits") - Pay (from "Compensation") - Process (from "The Process") - How to Apply (from "To Apply") That's many sections but each substantive. Could we combine Process and How to Apply under a single "Application Process"? Might be better. But instruction: "Prefer a few substantive sections over many thin ones." So we should try to reduce number of sections. Perhaps combine Requirements and Qualifications into one "Requirements & Qualifications"? But they'd be separate headings. Could combine "You Might Be a Fit If…" and "Nice to Have" into "Qualifications & Skills". However we need to follow heading examples; but we can still use

for those combined headings. Let's think: The posting has clear sections: The Role, What You’ll Do, You Might Be a Fit If…, Requirements, Nice to Have, Compensation, Benefits, The Process, To Apply. That's 9 sections. Could we merge some? For instance, "The Role" and "What You’ll Do" could be combined into "About the role & Responsibilities". But we need to follow heading examples: About the role, Responsibilities. Could we have About the role (includes The Role paragraph) and Responsibilities (What You’ll Do). That's two sections. Requirements and Qualifications: Requirements is explicit list; Qualifications could be You Might Be a Fit If…. Could combine into "Requirements & Qualifications". But we have separate headings examples; but we can still use a combined heading. Skills: Nice to Have could be Skills. Benefits: as is. Pay: Compensation. Process: The Process. Apply: To Apply. That's still many. Maybe we can omit Process and Apply as they are not in the example list but still substantive. However the instruction says "include a section ONLY when the posting has real, specific content for it". It doesn't forbid adding sections not in the list. So we can keep them. But to follow "Prefer a few substantive sections over many thin ones", maybe we can combine Process and Apply into "Application Process". That would be one section. Thus final sections: - About the role (The Role paragraph) - Responsibilities (What You’ll Do) - Requirements & Qualifications (combine Requirements and You Might Be a Fit If…) - Skills (Nice to Have) - Benefits - Pay - Application Process (The Process + To Apply) That's 7 sections. Check if any section becomes thin: Requirements & Qualifications will have two lists; that's substantive. Now we need to output HTML fragment with

headings and appropriate

• for lists,

  for prose. We must not include markdown code fences. Let's extract content precisely. **About the role**: From "The Role" paragraph: "The Role This role reports into Head of Partnerships and sits at the intersection of field marketing and partnerships. The partnerships motion is already in early form. Your job is to be in market — creating presence, activating partners, testing what converts, and feeding a clear scoreboard back — not to invent strategy from a desk. You're not supporting marketing from Slack. That's not a warning — it's the design. Travel is a really big part of this job. Week to week, you are in rooms where partners and buyers actually show up, pressure-testing messaging, running field plays, and turning signal into something the team can run. Early does not always mean revenue yet. It means the motion is being proven in person." We need to preserve all substantive information. We'll put that in a

  . **Responsibilities**: "What You’ll Do" bullet list: - Own field execution for priority partnership markets. Show up, run the play, learn what converts, write it down. - Travel constantly. Being in market is the core of the job, not a perk. - San Francisco is home base. - Activate partners that produce signal. Meetings and logos without follow-through don't count; tracked outcomes do. - Run a simple scoreboard. Activity → meetings → referrals → conversion — visible even when revenue is still early. - Close the feedback loop. Turn field insight into messaging, collateral, and handoffs the rest of the team can use. - Experiment fast. Try plays, measure, double down or kill — learning speed over polish. - Own outcomes within your lane. When a motion isn't moving, fix the targeting, message, channel, or handoff. - Travel is the job. If you want a San Francisco desk role with occasional events, this is the wrong seat. You will be in market a lot. - It's measured in movement, not vibes. Events attended don't count if nothing converts or gets tracked. Early markets may not have clean revenue yet — your job is still to create and measure signal. We need to keep each bullet as

• . Ensure we keep the exact phrasing. **Requirements & Qualifications**: Combine Requirements list and You Might Be a Fit If… list. Requirements list: - 2 years in field marketing, partnerships, growth, demand generation, BD, GTM, or a high-intensity startup role, with demonstrated ownership (startup experience weighted heavily) - Evidence you can own messy work end-to-end - Strong written and verbal communication - Ability to operate autonomously and context-switch rapidly - Track record of delivering under pressure with high standards - Based in San Francisco or willing to relocate immediately - Able and willing to travel heavily on a regular basis You Might Be a Fit If… list (bullet points): - High agency — you move toward execution, not away from it. - Energized by building from zero rather than rattled by it. - You think in simple systems: insight → play → scoreboard → next move. - Experienced in high-pace environments — typically ~2 years in field marketing, partnerships, growth, BD, GTM, or startup roles, with real ownership already. Startup years are weighted heavily. - You want serious ownership and career capital, not a desk-only marketing job. Note there is some overlap with Requirements (2 years etc). We'll keep both as given; duplication is okay? The instruction says preserve ALL substantive information; do not invent or summarize away detail. Duplication is present in original; we should keep it as is. So we will include both lists under the same section, maybe separate
  for each? Could combine into one list but that would lose duplication. Better to keep two separate lists with headings? But we only have one heading for the section. We could just put all items in one list; duplicates will appear twice if they appear twice in source. Let's check: Requirements includes "2 years in field marketing, partnerships, growth, demand generation, BD, GTM, or a high-intensity startup role, with demonstrated ownership (startup experience weighted heavily)". You Might Be a Fit If… includes "Experienced in high-pace environments — typically ~2 years in field marketing, partnerships, growth, BD, GTM, or startup