Enterprise Account Director, New Business

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, etc. Also remove navigation, cookie, etc. Must not create sections with filler like "commensurate with experience". Must include Pay and Benefits only if posting actually states them. The posting includes "Compensation & Benefits" with base salary and benefits list. So we need Pay section (maybe combine with Benefits? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So separate Pay and Benefits sections. The posting includes both compensation and benefits. So we can put Pay: base salary and commission plan. Benefits: list of benefits. Also need About the role: includes location, travel, team, reporting line, description. That's about the role. Responsibilities: from "What You'll Do" bullet list. Requirements/Qualifications/Skills: The posting has "What You Bring" and "How You Operate" and "This Role Likely Isn't Right For You" and "What Great Looks Like In The First 12 Months". We need to map to sections: Requirements, Qualifications, Skills. We need to decide what goes where. The instruction: Use those headings only if posting has real specific content. We can split: Requirements: years of experience, track record, etc. Qualifications: maybe education? Not present. Skills: specific abilities like multithreading, champion building, etc. Could also include "How You Operate" as skills/attributes. We'll need to preserve all substantive info, not invent. So we need to extract all bullet points and paragraphs. We must not include boilerplate like EEO, legal, etc. The posting includes "We welcome and encourage applications from people with disabilities under the Accessibility for Ontarians with Disabilities Act. Accommodations are available on request..." That's EEO/legal boilerplate; should be removed. Also "Candidates must have current US or Canada work authorization. For US candidates, this employer participates in E-Verify..." That's also legal; remove. Also "No relocation assistance can be offered at this time." That's maybe not boilerplate but could be considered part of benefits? It's a statement about relocation assistance; could be included in Benefits? It's a negative statement; but it's substantive? It says no relocation assistance. Might be considered part of Benefits or general info. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The relocation assistance statement is not exactly legal but could be considered a condition; but it's not a benefit. Might be okay to keep? It's not EEO. It's a condition of offer. Might be considered part of Benefits? Probably we can keep it under Benefits as a note: "No relocation assistance offered." But it's not a benefit; it's a lack. Might be considered boilerplate? Not sure. Safer to omit? The instruction says remove legal/EEO etc. Relocation assistance is not legal; it's a condition. Might be okay to keep. However, we have limited sections; we could include a short paragraph under Benefits or under About the role? Probably better to include under Benefits as a note: "No relocation assistance offered." But the instruction says only include Benefits section if posting actually states them. It does state benefits and also mentions no relocation assistance. So we can include that. We also need to remove duplicated lines. Ensure we don't repeat. Now craft HTML. Structure:

About the role

Location: Remote, US or Canada. Travel: 25–30%, including client visits and industry events. Team: Client Partner / Growth. Reports to VP, Client Partner, Growth & Strategy. As an enterprise sales role, you will partner with BDRs to turn early conversations into won enterprise engagements, develop champions, reach economic buyers, and manage long sales cycles.

But we must preserve all substantive info; we can't summarize away detail. However we can condense but must not lose detail. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." That means we cannot omit details; we must keep all specifics. Summarizing may be considered summarizing away detail. So we need to keep the details, maybe as bullet points or prose but not omit any specifics. However we can rephrase but must keep all info. That's tricky. We need to include all specifics: location remote US/Canada, travel 25-30%, team, reporting line, role description (partner with BDRs, turn early conversations, develop champions, get to economic buyer, carry complex deals through cycles, procurement, scoping, review to signed engagement). Also mention that BDR team opens door and you turn that first conversation into a won enterprise engagement. Also mention you'll take early-stage conversations and build them into real opportunities. Also mention developing champions from nothing, getting to economic buyer, carrying complex deals through long cycles, procurement, scoping and review to a signed engagement. Also mention you know how enterprise organizations buy professional services, etc. That's more about you. That belongs in Requirements/Qualifications/Skills. We need to ensure we don't lose any detail. Might be best to keep the original paragraphs under each heading, just wrap them in

or

• . That preserves info. Thus: About the role: copy the paragraphs under "About The Role" (starting from "Location: Remote, US or Canada Travel: 25–30%, including client visits and industry events Team: Client Partner / Growth This is an enterprise sales role reporting our VP, Client Partner, Growth & Strategy. Our BDR team opens the door and you turn that first conversation into a won enterprise engagement. You'll take early-stage conversations and build them into real opportunities. That means developing champions from nothing, getting to the economic buyer, and carrying complex deals through long cycles, procurement, scoping and review to a signed engagement.") We'll keep as

  . Responsibilities: copy bullet list under "What You'll Do". Each bullet as

• . Requirements: maybe from "What You Bring" (the bullet points). That includes years of experience, experience running deals, track record, proven ability to gain access, comfort selling premium, proven ability to multithread, hands-on experience navigating procurement, working fluency in martech ecosystem, grounded point of view on AI, experience selling advisory etc., rigorous pipeline management. We'll put those as
• under Requirements. Qualifications: maybe from "How You Operate" (the attributes: Hungry, Persistent, Wide, not narrow, Commercially courageous, Curious, Comfortable with ambiguity). Also maybe "This Role Likely Isn't Right For You" could be considered qualifications? But that's more about not fit. We could treat that as a separate section? Not in list. Could omit? But we must preserve all substantive info; we cannot omit that. However we could incorporate those as part of Qualifications or Skills? The instruction says we can only use those headings; we could put "This Role Likely Isn't Right For You" under Qualifications as a note? But it's not a qualification; it's a negative filter. Might be better to include under Qualifications as a bullet list of what is not desired. That preserves info. Skills: maybe from "What Great Looks Like In The First 12 Months" (outcomes). Or we could treat that as Skills? But it's more about expected performance. Could be under Skills? Not ideal. However we need to include all sections only if posting has real specific content. We have content for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Do we have Schedule? Not mentioned besides travel 25-30% (that's travel, not schedule). No schedule info. So we should NOT create Schedule section because no specific content. Similarly, we might not have separate Skills if we already covered skills in Requirements/Qualifications. But we need to decide. We have content for: - About the role: yes. - Responsibilities: yes. - Requirements: yes (What You Bring). - Qualifications: maybe from How You Operate + This Role Likely Isn't Right For You. - Skills: maybe from "What Great Looks Like In The First 12 Months" (outcomes) or we could treat as Skills: e.g., high conversion rate, multiple net-new logos, direct relationships, predictable deals, productive partnership, expanding client. Those are more like performance expectations, not skills. Could be under Qualifications? Might be better to put under Qualifications as "What success looks like". But the instruction says we should prefer a few substantive sections over many thin ones. So we could combine Qualifications and Skills into one section? But we must use headings only if posting has real specific content for that heading. If we don't have distinct content for Skills, we should not create a Skills heading. So we could omit Skills section. Similarly Benefits: we have benefits list. Pay: we have compensation details. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We must not include Schedule. Now we need to ensure we don't repeat job title. Not include. Now we need to remove boilerplate: EEO, legal, work authorization, E-Verify, relocation assistance? Relocation assistance is not EEO but maybe considered a condition; we could keep it under Benefits as a note: "No relocation assistance offered." That's substantive. We'll keep. Now we need to preserve all substantive info: we must not lose any detail from the original. Let's extract all sections. Original text broken down: About SH/FT SH/FT is an execution-led strategic consultancy ... (company description). This is not needed for job posting? It's about the company. Might be considered boilerplate? It's not navigation/legal but it's company overview. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company overview is not those; it's substantive info about the company. Should we keep? The instruction says "Preserve ALL substantive information". So we should keep the company description? However the user asked to reformat a job posting into clean HTML. Usually we include company overview maybe under About the role? But they didn't give a heading for company. Could include under About the role as a paragraph? But the "About SH/FT" appears before "About The Role". It's part of the posting. We should keep it. However the instruction about headings: use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They didn't list "About the company". So we cannot create a heading not in that list. But we could embed it under About the role as a paragraph? That would mix company description with role description. Might be okay but could be considered not following the heading list. However we could treat "About SH/FT" as part of "About the role" section? Not ideal but maybe acceptable. The instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., not limited to? It says e.g., meaning examples. So we could also use other headings if needed? But they gave examples; we could still use other headings but they said "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 not add a heading for company overview. We could incorporate it into About the role paragraph as a brief intro. That would preserve the info. Thus About the role paragraph will include company description plus role details. Now we need to ensure we don't lose any detail from the original. Let