Director of Product, Enterprise

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes "About Us" (company description) but not needed as heading? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. So we need to map content to these headings. We have content: "About Us" description of company; maybe we can put under "About the role"? Actually "About the role" is typical heading for role description. The posting includes "What You’ll Do" (responsibilities) and "About You" (requirements/qualifications/skills). Also "Working at Higharc" includes remote work, travel, compensation and benefits. So we can create sections: - About the role: maybe a brief summary of role purpose (the paragraph after "Higharc is seeking a Head of Product, Enterprise..."). - Responsibilities: the bullet list under "What You’ll Do". - Requirements: maybe the "You have:" list (experience, etc.) could be requirements. - Qualifications: maybe the "A major plus if you also bring:" list (preferred qualifications). - Skills: maybe combine some skills? Could be derived from requirements but we could list specific skills like product strategy, team leadership, cross-functional collaboration, etc. But we need to avoid filler. The posting includes many skill-like items: "strong product thinking with strong design judgment", "experience leading cross functional teams", "strong product instincts", "ability to balance short term execution with long term product strategy", "excellent communication and stakeholder management skills", "comfort working across ambiguity". Those could be skills. - Benefits: from "Compensation and benefits:" includes competitive salaries, equity, medical/dental/vision, flexible PTO, maternity/paternity leave, disability plans, 401K, stipend for home office, L&D. - Pay: Not explicitly stated; only "competitive salaries with significant equity". No specific numbers. Should we include Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation and benefits, but not specific pay numbers. It says "competitive salaries with significant equity". That is still compensation info. Is that enough to include Pay? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state compensation (salaries, equity). So we can include Pay section with that statement. However we also have Benefits section; we could combine compensation and benefits into Benefits? But they asked separate sections for Benefits and Pay. We'll include Pay with the statement about competitive salaries and equity. Benefits with the list. - Schedule: Not mentioned; remote work, travel, meetups. No explicit schedule like full-time, hours. Could infer full-time but not stated. So we should not create Schedule section. We must not include 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 we should drop it as it's not substantive about the job. Also "Please note: we are seeing an uptick..." is not needed. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep the details exactly as given, but we can reformat into HTML lists and paragraphs. We must not repeat the job title as a heading. The job title is "Head of Product, Enterprise". Not to be used as heading. We need to output only HTML fragment, no /, no markdown. Let's structure:

About the role

Higharc is seeking a Head of Product, Enterprise to lead a major pillar of our Product organization. In this role, you will define the vision, strategy, and execution for the products that help homebuyers explore and configure their homes, while enabling suppliers and builders to move more quickly from selection to estimating and readiness. You will lead product efforts across Estimate and Showroom, shaping connected experiences that improve buyer confidence, operational speed, and business outcomes.

Responsibilities

• Build and manage a strong team of product managers across this portfolio, helping the team deliver high quality product outcomes while growing in craft and leadership.
• Own the product vision, strategy, and roadmap for enterprise products, focusing on specific workflows.
• Shape the end to end experience that enables drafters to design homes, homebuyers to select and configure their homes, and estimators to generate a takeoff.
• Own key metrics across the builder and buyer journey, with accountability for conversion, engagement, product adoption, and the business impact of each experience over time.
• Drive product led growth for key products.
• Partner with internal teams to simplify customer onboarding experience.
• Work closely with internal and external stakeholders to understand market needs, validate new opportunities, and bring new capabilities to market.
• Mentor and develop product managers, helping create a strong and durable product organization as Higharc grows.
• Stay on top of industry trends and emerging technologies, including advancements in AI, recommendation systems, visualization, supplier workflows, shopping experiences, and residential construction.

Requirements

• 8+ years of product management experience, including experience leading multiple product areas or teams
• 4+ years of people management experience, including coaching and developing product managers
• A track record of shipping products that drive measurable business outcomes across customer experience, operations, or commerce workflows.
• Experience with product led growth.
• Pair strong product thinking with strong design judgment, ensuring experiences are not only effective and scalable, but also intuitive, cohesive, and high quality.
• Experience leading cross functional teams across Product, Engineering, Design, Data, and GTM partners
• Strong product instincts for both user facing experiences and backend workflow or operational systems
• The ability to balance short term execution with long term product strategy in a fast moving environment
• Excellent communication and stakeholder management skills, with the ability to align teams around clear goals and tradeoffs
• Comfort working across ambiguity and complexity, especially where multiple personas, systems, or business goals intersect

Qualifications

• Experience in consumer products, marketplaces, ecommerce, purchasing, or supplier workflows
• Experience in construction technology, homebuilding, design software, or related vertical products
• Familiarity with AI powered workflows, recommendation systems, visualization tools, or estimating products

Skills

Strategic and customer‑obsessed product leadership; ability to move between consumer‑style experiences and complex operational workflows; talent for connecting multiple users, systems, and business processes into cohesive journeys.

Alternatively we could list skills as bullet points derived from requirements but we already have many. Might be redundant. But we need a Skills section only if there is real specific content. The posting does not have a separate "Skills" heading; but we can extract skill-like statements from "About You". However we risk duplicating content. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we create a Skills section, we must take content from the posting that corresponds to skills. The posting includes many skill-like items under "About You". Those could be considered requirements. But we already put them under Requirements. If we also put them under Skills, we'd be duplicating. Better to not create a Skills section if it would duplicate. However the instruction says we can use Skills heading if there is real specific content for it. The posting does not explicitly label a Skills section, but we could treat the "About You" bullet list as skills/requirements. Since we already used Requirements for the experience/years etc., and Qualifications for the pluses, we could put the remaining skill descriptors under Skills. Let's parse: About You bullet list includes: - You’re a strategic and customer obsessed product leader who can move fluidly between consumer style experiences and complex operational workflows. - You thrive in environments where product success depends on connecting multiple users, systems, and business processes into one cohesive journey. - You have: (then the list of experience etc.) - A major plus if you also bring: (list) Thus the first two bullet items are more about traits/skills. So we could put those under Skills. Thus:

Skills

• Strategic and customer‑obsessed product leader who can move fluidly between consumer style experiences and complex operational workflows.
• Thrives in environments where product success depends on connecting multiple users, systems, and business processes into one cohesive journey.

That preserves those statements. Now Benefits section: from "Compensation and benefits:" paragraph. We need to capture: competitive salaries with significant equity, comprehensive medical, dental, and vision coverage, flexible PTO, meaningful maternity/paternity leave to all U.S based employees that are full-time, access to short and long-term disability plans and a 401K, stipend to create the ideal home office and support ongoing L&D. We'll put as

. Pay section: maybe just the competitive salaries with significant equity statement. But we already included that in Benefits. However we could separate: Pay: competitive salaries with significant equity. Benefits: the rest. Let's do that. Thus:

Pay

Competitive salaries with significant equity.

Benefits

• Comprehensive medical, dental, and vision coverage
• Flexible PTO
• Meaningful maternity/paternity leave for all U.S.-based full‑time employees
• Short and long‑term disability plans
• 401(k) plan
• Home office stipend
• Ongoing learning and development (L&D) support
We should not include Schedule. We also need to include maybe a short paragraph about remote work and travel under maybe "Working at Higharc". That could be part of Benefits or maybe a separate section like "Work Arrangement". But not in allowed headings. Could fold into Benefits? It's not a benefit exactly but could be under Benefits? Might be better to include under Benefits as remote work flexibility. However the instruction: only create sections when posting has real specific content for it. It does have remote work and travel info. Could we add a section like "Work Arrangement"? Not allowed headings. The allowed headings are limited to those eight. So we must fit that info into one of those sections. Perhaps we can put remote work and travel under Benefits as a bullet: "Fully remote work with regular team meet‑ups across the US". Or we could put under About the role? Probably better to add a bullet under Benefits: "Remote‑first work environment with regular in‑person team meet‑ups". That preserves the info. Thus Benefits bullets add remote work. Now ensure we didn't include any boilerplate like fraud warning. We'll drop that. Now output HTML fragment. Check for any repeated content: We have About the role paragraph (makes sense). Responsibilities list (from What You’ll Do). Requirements list (from You have). Qualifications list (from major plus). Skills list (from first two bullet points). Pay paragraph. Benefits list (including compensation? Actually we put compensation in Pay, benefits list includes medical etc plus remote work). Ensure we didn't miss any substantive info: The "About Us" description at start: "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