GTM Architect

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Freehand" (company description) and "The Role & The Team" (role description) and "What you'll own:" (list), "Who You Are" (requirements), "Working at Freehand" (benefits and culture), "Compensation Range". We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. However we must only include sections when posting has real specific content. We need to map content to these headings appropriately. We have: - About Freehand: company overview. Could be "About the role"? Actually "About the role" is for role description. "About Freehand" is company description; maybe we can put under "About the role"? But guidelines: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can decide to include "About the role" for role description (The Role & The Team). "Responsibilities" for what you'll own list. "Requirements" for Who You Are (experience). "Qualifications" maybe not needed if same as Requirements. "Skills" maybe for AI user etc. "Benefits" for benefits listed. "Pay" for compensation range. "Schedule" maybe not present (no schedule info). So we should omit Schedule. We must not repeat job title as heading. No Job ID. We must remove boilerplate: EEO, equal opportunity, etc. Also remove "Freehand hires on merit..." that's EEO boilerplate; remove. Also remove "If you meet most of the criteria..." maybe also boilerplate? It's encouraging to apply; could be considered EEO? Might be considered generic encouragement; but it's not strictly EEO; but it's still a generic statement. Safer to remove? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The EEO statement is definitely boilerplate; remove. The "If you meet most of the criteria..." is also encouraging to apply; could be considered application instruction? It's not exactly instruction to apply but encourages; might be considered fluff. Safer to remove. Also remove "Working at Freehand" section includes culture principles; we need to keep that as part of Benefits? Actually it's culture/working environment; maybe we can include under Benefits? But Benefits heading is for benefits like vacation, health etc. The culture principles could be under a separate section like "About the role"? Not exactly. Could be under "Qualifications"? No. Perhaps we can create a section "About the role" that includes both role description and culture? But guidelines: Use headings for those specific categories; we can add extra sections not listed? The instruction says: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive? It says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings only. If some content doesn't fit, we could incorporate into nearest heading. Thus: - About the role: include company overview (About Freehand) and role description (The Role & The Team). Could combine. - Responsibilities: list of what you'll own (seller onboarding, training programs, etc.) - Requirements: Who You Are (5+ years experience, etc.) - Qualifications: maybe we can include "Native AI user" etc as skills? But we have Skills heading for skills like AI user, market thinking, credibility. Could split. - Benefits: list of benefits (Take what you need Vacation Policy, Monthly home-internet costs, Full health coverage, Life Insurance and Disability benefits, HSA/FSA Access, 401(k) with 4% Employer Match, Fully-paid Parental Leave). Also maybe include remote work, travel-first, home internet coverage, quarterly trips. Those are benefits. - Pay: Compensation Range: $200K - $250K. - Schedule: not present, omit. We must not include headings with filler text. Ensure each heading has substantive content. We must not include duplicated lines. We must output only HTML fragment. Let's craft. Structure:

About the role

About Freehand ... The Role & The Team ...

But we need to keep the content: About Freehand paragraph, then The Role & The Team paragraph. We'll combine into one

maybe with line breaks? Could use

for each paragraph. Better:

About Freehand ...

The Role & The Team ...

Then Responsibilities:

Responsibilities

• ...

List items: Seller onboarding, training programs, and certification frameworks; Sales collateral including decks, one-pagers, battle cards, objection guides; GTM narratives for new segments, verticals, and use cases; Enablement tooling and content systems, built with AI where it removes friction; Leading indicators that tie enablement activity to pipeline and revenue. Requirements:

Requirements

5+ years in field/ revenue/ sales enablement, ideally at an early-stage B2B AI or SaaS company. You've built from a blank page before and you're energized by it. Designed, own and run seller training programs end-to-end; Built collateral field teams actually use — you know why most decks fall short; Written GTM narratives: ICP, value prop, competitive positioning, the pitch itself; Native AI user — it's in how you draft, research, build, and find leverage; Thinks at the market level: spots adjacencies, new segments, brings ideas forward; Has genuine credibility with sellers, earned from time working alongside them.

But we might split some into Skills. Skills:

Skills

• Native AI user — uses AI to draft, research, build, and find leverage
• Market-level thinking — spots adjacencies and new segments, brings ideas forward
• Credibility with sellers — earned from working alongside them

But we already included some in Requirements; we need to avoid duplication. Perhaps Requirements focuses on experience and background; Skills focuses on abilities. Let's define: Requirements: experience years, built from blank page, designed/training programs, built collateral, written GTM narratives. Skills: Native AI user, market-level thinking, credibility with sellers. Qualifications: maybe not needed; we could omit if no distinct content. But we have to decide whether to include Qualifications heading. If we don't have specific qualifications beyond requirements/skills, we should omit. Benefits:

Benefits

• Take what you need Vacation Policy
• Monthly home-internet costs covered
• Full health coverage (multiple gold-standard carriers across medical, dental & vision)
• Life Insurance and Disability benefits
• HSA/FSA Access
• 401(k) with a 4% Employer Match
• Fully-paid Parental Leave
• Remote‑first work (Work Anywhere across the globe)
• Quarterly fully‑paid trip to an Office Hub to meet cross‑functional teams

Pay:

Pay

Compensation Range: $200K - $250K

We must not include Schedule. Check for any leftover boilerplate: We removed EEO line and encouraging to apply line. Also removed "Freehand hires on merit — your thinking..." etc. Also removed "If you meet most of the criteria..." etc. Check for duplicated lines: none. Now ensure we preserve all substantive information: Did we miss any? Let's review original: - About Freehand paragraph: included. - The Role & The Team paragraph: included. - What you'll own list: included as responsibilities. - Who You Are list: we split into requirements and skills. - Working at Freehand: includes Series B, ~100 people across US and India, core operating principles (list). We missed those! We need to include those somewhere. They are substantive: company size, stage, operating principles. Where to put? Could be under About the role? Or maybe under Benefits? Not exactly. Could be under "About the role" as company context. Or we could create a separate section but not allowed headings. Could incorporate into About the role paragraph. We should include: Series B, ~100 people across US and India. Five core operating principles: list them. We need to preserve them. Let's add to About the role paragraph after company description. Thus About the role will have:

About Freehand ... The Role & The Team ... Freehand is a Series B company with ~100 people across the US and India. We operate on five core operating principles: Context Before Confidence; Decisions, not Recommendations; High Agency, High Trust; Accountability is the Product; The Work That Remains is the Work That Matters.

We need to keep the description of each principle? The original includes explanations after each principle. Should we preserve them? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the explanations. However we can keep them as part of the paragraph; it's okay to include the explanations. Thus we need to include the principle names and their explanations. Let's capture them: - Context Before Confidence. We get in, ask (a ton of) questions, connect the dots ourselves and move fast. No passengers, no hand-holding. The amount of confidence you'll have in Week 1 is directly proportional to the context strive to gain. - Decisions, not Recommendations. Freehand folks decide, they don't present options. You'll have real autonomy, and real accountability to match. - High Agency, High Trust. We won't manage you closely or ask you to escalate every call. Act, share your reasoning, and course-correct when needed. That's the contract. - Accountability is the Product. When something goes wrong — and it will — we name it, learn from it, and move on. No politics, no cover. Just fix it. - The Work That Remains is the Work That Matters. We actively cut low-value work. What lands on your plate is there because it matters — and can only be done by you. We need to include all that. Thus About the role paragraph will be long but okay. Now Responsibilities list: we have. Requirements: we have experience etc. Skills: we have AI user, market-level thinking, credibility with sellers. But we also have "Designed, own and run seller training programs end-to-end" etc which we put in Requirements. Good. Now Benefits: we have list plus remote work and quarterly trip. Pay: compensation. Now ensure we didn't miss any: The original also mentions "We run on five core operating principles; these are not values-on-a-wall, this is the exact philosophy we built our AI agents on :" then list. We included. Also "We also cover your monthly home-internet costs." included. "Every quarter, we arrange for a fully-paid trip to one of our Office Hubs to meet & interact with cross-functional teams." included. "Take what you need Vacation Policy" included. "Full health coverage (with multiple gold-standard carriers across medical, dental & vision)" included. "Life Insurance and Disability benefits" included. "HSA/FSA Access" included. "401(k) with a 4% Employer Match" included. "Fully-paid Parental Leave" included. Now check for any other substantive: "Series B, ~100 people across the US and India