Sales Enablement Lead

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We need to extract content. The posting includes sections: About Us (company description) but not needed? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. The posting includes "About Us" (company description) maybe not needed. There's "What You'll Do" (responsibilities). There's "About You" (requirements/qualifications/skills). There's "Compensation and benefits" (benefits). There's "Remote work and travel" (maybe schedule? Not exactly schedule). There's no explicit Pay or Schedule details. So we should only include sections where we have real specific content. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate like cookie/navigation/legal/EEO etc. There's a fraud warning at end; that's boilerplate? It's a note about fraudulent recruiting activity; likely should be removed as it's not substantive job info. Also "Please note: we are seeing an uptick..." remove. We need to keep remote work description? It's about work arrangement; could be considered Schedule? Not exactly schedule but maybe we can put under "Schedule" if we have info about remote work and travel. The instruction: include a section ONLY when posting has real, specific content for it. The remote work and travel section is specific: "Our company is entirely remote, and has been since we were founded in 2018. Remote work means more time with family, less time commuting, and the flexibility to blend work and life. We value in-person collaboration and asynchronous deep-work time, which is why we schedule regular team meet-ups in our hubs across the US and, depending on the role, prioritize hiring in those hubs. If your role requires frequent travel beyond pre-scheduled team meet ups, we will represent that to the best of our ability as early as possible in the interview process." That's specific content about work arrangement; could map to "Schedule" (maybe). But schedule usually refers to hours, full-time/part-time, shift. However remote work description could be considered under "Schedule" or maybe we could create a "Benefits" section includes remote work stipend? Actually benefits includes stipend for home office, L&D, medical etc. Remote work description is more about work arrangement; maybe we can put under "Schedule" as it's about where/when work occurs. We'll include a Schedule section with that content. Pay: Not mentioned specific salary or equity numbers; only "competitive salaries with significant equity". That's vague but still specific? It says "competitive salaries with significant equity". That's not a number but it's a statement. The instruction says never emit a heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "competitive salaries with significant equity" is somewhat vague but not placeholder like "commensurate with experience". It's a statement; maybe acceptable. However they said "Prefer a few substantive sections over many thin ones." If we include Pay with just that sentence, it's thin. Might be better to omit Pay section because no concrete numbers. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation and benefits: "Higharc offers competitive salaries with significant equity, in a fast-growing, well-funded company. We provide comprehensive medical, dental, and vision coverage, with flexible PTO, and meaningful maternity/paternity leave to all U.S based employees that are full-time. You'll also have access to other big-company benefits such like short and long-term disability plans and a 401K. We also provide a stipend to create the ideal home office and support ongoing L&D." That's benefits. So we should include Benefits section with that content. Pay: they mention competitive salaries with significant equity; that's compensation. Could be considered Pay section. It's not a specific number but it's still stating compensation. I'd include Pay section with that sentence. Schedule: remote work and travel description is present; we can include Schedule. Now we need to map content. Sections: - About the role: maybe we can use the "About Us" description? But About the role likely refers to role description. The posting includes "Higharc is seeking a strategic, hands-on Sales Enablement Lead..." That's role overview. Could be placed under About the role. However we also have "What You'll Do" which is responsibilities. So we can put role overview under About the role. - Responsibilities: "What You'll Do" bullet points (actually paragraphs). We'll convert to

• . - Requirements/Qualifications/Skills: The "About You" section includes qualifications, track record, etc. We can split into Requirements (must-haves) and Qualifications (maybe same) and Skills (plus). But we need to avoid thin sections. Could combine into one Requirements section with all. But instruction says use headings for those categories if content exists. We could put all under Requirements (or Qualifications). Let's parse: About You bullet points: - You're a self-starter who thrives in an unstructured, pre-IPO environment. - You've built enablement teams and programs before, and you're happy to roll your sleeves back up as an individual contributor. - You're energized by ambiguity and by the chance to build something from scratch, and you're comfortable in small teams where shipping the solution matters as much as designing the process behind it. - You have: - A track record of owning GTM enablement, process, or strategy in SaaS, likely 5+ years. - Direct US homebuilding experience, or a proven ability to get fluent in a complex new industry fast. - Experience supporting SaaS GTM teams through significant scale - The instincts of a hands-on builder who has led programs and returned to IC work by choice. - The ability to drive consensus across functions using data, prototypes, and persuasion. - Comfort building scalable, maintainable processes while still shipping solutions where they're needed. - A major plus if you also bring: - Platform-as-a-Service or consumption-based revenue experience We could treat the bullet list as Requirements (must-haves) and the "major plus" as Skills (nice-to-haves). Qualifications maybe similar to Requirements. To avoid thin sections, we could make Requirements include the must-haves, and Skills include the plus. Qualifications maybe omitted if redundant. But we need to follow instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't say we must use all; only use when content present. So we can have Requirements and Skills sections. Thus: - Requirements: the must-have items (track record 5+ years, US homebuilding experience or ability to get fluent, experience supporting SaaS GTM teams through significant scale, instincts of hands-on builder, ability to drive consensus, comfort building scalable processes). Also maybe the self-starter etc could be considered requirements but they are more traits. We'll include them. - Skills: the major plus: Platform-as-a-Service or consumption-based revenue experience. We could also include "You're a self-starter..." as part of Requirements. Now Benefits: we have the compensation and benefits paragraph. Pay: "competitive salaries with significant equity". We'll include that as Pay. Schedule: remote work and travel description. Now we need to ensure we preserve all substantive information. Also include the company description? The "About Us" is about Higharc; maybe we could put under About the role? But About the role is about the role, not company. However we could include a brief company overview under About the role as context. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." It doesn't forbid including company description. It's substantive. We could include a short paragraph under About the role (or maybe a separate section like "About the company" but not in allowed headings). Since only allowed headings are those listed, we should fit company description under About the role (makes sense as role context). Or we could include it as a

  before any heading? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. It didn't say we must start with a heading. We could include a

  for company description then headings. But they said use

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

  outside sections. However to be safe, we can include company description as a

  before the first heading or as part of About the role section. I'll put a

  with company description, then

  About the role

  with maybe a short summary of role (the first paragraph about seeking a strategic, hands-on Sales Enablement Lead). Then Responsibilities, Requirements, Skills, Benefits, Pay, Schedule. Now we need to ensure we don't repeat job title. We'll not include "Sales Enablement Lead" as heading. Now let's extract exact sentences. Company description paragraph: "Higharc is a VC-backed startup that is changing how new homes are designed and built. Join a founding team who’ve shipped products for Autodesk, Electronic Arts, Nike, and Apple. We have raised over $175M with support from top-notch venture capital firms and more than 18 strategic investors: industry leaders in construction, building products manufacturing, and distribution." That's substantive. Now About the role: The posting says: "Higharc is seeking a strategic, hands-on Sales Enablement Lead to build the foundations of Sales, Partner, and Post-Sales Enablement as our first dedicated enablement hire. This is a team-of-one role, standing up the function from zero as our Solution Engineering and Sales teams scale fast through a double/double growth motion." We can put that as content under About the role. Now Responsibilities: The "What You'll Do" section includes multiple paragraphs. Let's capture them: - "As Higharc's first Sales Enablement hire, you'll own the enablement function end to end: the content, the training, and the systems that help our Solution Engineering, Sales, and Marketing teams close more deals, faster, with fewer resources per deal." - "You'll start by finding the immediate friction slowing those teams down and solving it tactically." - "Success in your first 90 days looks like sharper team focus and fewer self-inflicted losses, not a finished playbook." - "This is a connective-tissue role between Product & Engineering (PDE) and go-to-market." - "You'll translate every product release into a GTM-ready story, asset, and trained team, and own the signal loop that carries prospect and customer feedback back to the people building the product." - "You'll drive consensus across cross-functional groups with data, prototypes, and persuasion rather than authority." - Then "Expect to:" followed by bullet list (actually sentences starting with "Run focused discovery..." etc). We'll treat each as list item. Let's list them: 1. Run focused discovery across Solution Engineering, Sales, and Marketing to find the friction slowing win rate, and solve it tactically. 2. Build pre- and post-sales content, messaging, and objection handling that holds up in front of homebuilders and partners. 3. Own New Product Introduction end to end, from Product Marketing and Management through to prospects and customers. 4. Turn each PDE release into a GTM-ready story, a usable asset, and a trained, certified team. 5. Quantify and route customer and prospect feedback so the field's signal