Forward Deployed Product Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have "About the role" maybe includes description of role. But we have "About Us" which is company description. Might map to "About the role"? The instruction says we can use those headings; we should include sections only when posting has real specific content. The posting includes "About Us" describing company. That's substantive. Could be placed under "About the role"? Or maybe we create a section "About the company"? Not in list. But we could use "About the role" to include both role and company? Might be okay. However we also have "What You'll Do" which is responsibilities. Then "About You" which is qualifications/requirements/skills. Then "Remote work and travel" and "Compensation and benefits". Also "Please note: fraudulent recruiting activity" is boilerplate to remove.
Thus we need sections:
- About the role (maybe combine About Us and role description). Could include company description and role overview.
- Responsibilities: from "What You'll Do" bullet list.
- Requirements: from "About You" bullet list of required qualifications.
- Qualifications: maybe separate? Could combine with Requirements? But we need to decide. The posting includes "You have:" list (required). Then "A major plus if you also bring:" list (preferred). So we can put required under Requirements, and preferred under Skills or Qualifications. The instruction: Use headings like Requirements, Qualifications, Skills. We can map:
- Requirements: required qualifications (5+ years PM experience, hands-on technical fluency, etc.)
- Qualifications: maybe the "major plus" items? Or we could treat Qualifications as the same as Requirements. But better to separate: Requirements = required; Qualifications = preferred (major plus). Skills could be technical skills like SQL, notebooks, APIs, etc. But those are already in required. Might be redundant.
We need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section "Requirements" that includes both required and preferred, but we need to follow instruction: only include sections when posting has real specific content. It's okay to have one section covering both.
But we also have Benefits, Pay, Schedule sections. The posting includes "Compensation and benefits" describing salary, equity, medical, dental, vision, PTO, maternity/paternity leave, disability, 401K, stipend for home office, L&D. That's benefits. No explicit pay numbers or schedule details besides remote work and travel up to 30%. So we have schedule info: remote work, travel up to 30% of time. That's schedule. Pay: not specified (no salary numbers). The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state benefits (compensation and benefits). It does state schedule (remote work and travel up to 30%). It does not state specific pay numbers. So we should not create a Pay section because no specific pay info. However "Competitive salaries with significant equity" is mention but not specific. The instruction says: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). So we should not create Pay section because it would be filler. So we omit Pay.
Thus sections: About the role, Responsibilities, Requirements (maybe includes Qualifications), Benefits, Schedule.
We need to use for each heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them.
Let's extract content.
About Us / role overview:
"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. Higharc is seeking a hands-on Forward Deployed Product Manager to turn a large production homebuilder's unstructured plan catalog into structured, queryable product data. This is a founding role on a brand-new Forward Deployed team."
Then description of what they do: "A homebuilder's plan library is the product data behind its entire business, and at enterprise scale that data is almost entirely unstructured. Plans live as drawing sets scattered across semi-autonomous divisions, renamed and re-numbered as they move. Nobody can say with confidence which plans are duplicates, how many versions of a given home exist, or what actually varies between them. Higharc converts those catalogs into structured, queryable plan data and builds the analysis on top of it: searchable plan libraries with agent-enabled natural-language search, geometric similarity scoring that surfaces plans which have forked under different names, structured mapping of what varies across a library, and classification that makes consolidation decisions possible. You'll own what gets built in the field, working embedded alongside our Forward Deployed Engineers and in partnership with the homebuilder to turn plans into actionable data. This is a role for someone who wants to be close to where the problem lives. Higharc is fully remote; you can sit anywhere in the continental U.S., with travel to client sites and company events up to 30% of the time."
That's a lot of prose; we can keep as
.
Responsibilities: "Expect to:" then bullet list:
- Embed with HQ, regional, and division teams to run discovery—locate plan assets, establish source of truth, and document how each division represents its plans and where variation originates.
- Own product definition for the searchable plan library, analytics dashboard, and agent-enabled search—what a good query looks like, what a useful answer looks like, and what "structured for analysis" actually means.
- Tune Higharc's Autotranslate AI to identify, categorize, and translate floorplans into data.
- Work hands-on with the data: query the structured plan library directly, build against our internal APIs, and ship working capability back to users rather than filing a ticket and waiting.
- Define acceptance criteria for delivery milestones—coverage targets, data-field completeness, QA error thresholds—and hold the line on them when schedule pressure argues otherwise.
- Frame and defend quantifiable ROI: redundancy across a catalog, dimensional spread on repeated conditions, consolidation candidates, and the purchasing leverage each one represents.
- Partner with Forward Deployed Engineering, the Technical Lead, QA, Intake Specialists, and Client Strategy, and present progress and tradeoffs to executive stakeholders.
- Capture the playbooks, artifacts, and data patterns that let the forward deployed model carry over to the next engagement.
We need to preserve all detail.
About You (requirements):
"You're a product manager who is happiest closest to the customer, and you've learned that the fastest path to the right answer is usually to go look. You're comfortable being handed a scope that is 70% specified and a data set nobody has structured before. You can hold a conversation with an architect about how a plan set is drawn in the morning and write the query that tests your hypothesis about it in the afternoon. You know the difference between a demo and a deliverable, and you're honest with customers about which one they're looking at. You have:
- 5+ years of product management experience, including significant time in customer-facing or deployed settings—enterprise implementations, solutions engineering, technical consulting, or professional services.
- Hands-on technical fluency: you write SQL, work in notebooks, script against APIs, and interrogate a data set yourself rather than requesting a pull.
- Experience prototyping to validate ideas quickly using tools like Cursor, Replit, or V0.dev.
- A track record defining structured data models, taxonomies, or classification schemes and getting a business to actually adopt them.
- Strong judgment about data quality—what level of accuracy a decision requires, and what it costs to get there.
- Excellent written and verbal communication, including with executive stakeholders who have limited time and no patience for status without substance.
- Willingness to travel to client sites and company events up to 30% of the time."
Then "A major plus if you also bring:" list:
- Background in residential construction, homebuilding, architecture, or AEC technology—especially fluency with plan sets, elevations, options, and how builders manage plan variation.
- Experience with agent-based or natural-language search over structured data, RAG systems, or LLM-powered analytics.
- Exposure to geometric or spatial data—CAD/BIM, computer vision on drawings, similarity and clustering methods.
- Experience with large, messy, enterprise-scale data migrations or ingestion programs.
- Experience building a function from zero: first hire into a new team, new practice, or new delivery model.
We need to include these as either Requirements or Qualifications/Skills. Let's decide: We'll have a section "Requirements" for the required items (the "You have:" list). Then a section "Qualifications" for the "major plus" items. Or we could combine them under "Requirements" and note which are preferred. But better to separate as per headings.
Thus:
Requirements
with of required items.
Qualifications
with of preferred items.
Skills: maybe we could include technical skills like SQL, notebooks, APIs, etc. But those are already in requirements. Could create a Skills section for those technical skills, but that would be redundant. The instruction: prefer a few substantive sections over many thin ones. So maybe we omit Skills section and include technical skills within Requirements.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule.
Now Benefits: from "Compensation and benefits:" paragraph.
"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."
We need to preserve all detail. We'll put as - items.
Schedule: from earlier: "Higharc is fully remote; you can sit anywhere in the continental U.S., with travel to client sites and company events up to 30% of the time." Also later: "Remote work and travel: 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."
We need to preserve all substantive info. So schedule section includes remote work, travel up to 30%, regular team meet-ups in hubs across US, prioritize hiring in those hubs, etc.
We should not include boilerplate like "Please note: we are seeing an uptick of fraudulent recruiting activity..." Remove.
Also remove duplicated lines.
Now produce HTML fragment.
We
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. Let's extract content. About Us / role overview: "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. Higharc is seeking a hands-on Forward Deployed Product Manager to turn a large production homebuilder's unstructured plan catalog into structured, queryable product data. This is a founding role on a brand-new Forward Deployed team." Then description of what they do: "A homebuilder's plan library is the product data behind its entire business, and at enterprise scale that data is almost entirely unstructured. Plans live as drawing sets scattered across semi-autonomous divisions, renamed and re-numbered as they move. Nobody can say with confidence which plans are duplicates, how many versions of a given home exist, or what actually varies between them. Higharc converts those catalogs into structured, queryable plan data and builds the analysis on top of it: searchable plan libraries with agent-enabled natural-language search, geometric similarity scoring that surfaces plans which have forked under different names, structured mapping of what varies across a library, and classification that makes consolidation decisions possible. You'll own what gets built in the field, working embedded alongside our Forward Deployed Engineers and in partnership with the homebuilder to turn plans into actionable data. This is a role for someone who wants to be close to where the problem lives. Higharc is fully remote; you can sit anywhere in the continental U.S., with travel to client sites and company events up to 30% of the time." That's a lot of prose; we can keep as
. Responsibilities: "Expect to:" then bullet list: - Embed with HQ, regional, and division teams to run discovery—locate plan assets, establish source of truth, and document how each division represents its plans and where variation originates. - Own product definition for the searchable plan library, analytics dashboard, and agent-enabled search—what a good query looks like, what a useful answer looks like, and what "structured for analysis" actually means. - Tune Higharc's Autotranslate AI to identify, categorize, and translate floorplans into data. - Work hands-on with the data: query the structured plan library directly, build against our internal APIs, and ship working capability back to users rather than filing a ticket and waiting. - Define acceptance criteria for delivery milestones—coverage targets, data-field completeness, QA error thresholds—and hold the line on them when schedule pressure argues otherwise. - Frame and defend quantifiable ROI: redundancy across a catalog, dimensional spread on repeated conditions, consolidation candidates, and the purchasing leverage each one represents. - Partner with Forward Deployed Engineering, the Technical Lead, QA, Intake Specialists, and Client Strategy, and present progress and tradeoffs to executive stakeholders. - Capture the playbooks, artifacts, and data patterns that let the forward deployed model carry over to the next engagement. We need to preserve all detail. About You (requirements): "You're a product manager who is happiest closest to the customer, and you've learned that the fastest path to the right answer is usually to go look. You're comfortable being handed a scope that is 70% specified and a data set nobody has structured before. You can hold a conversation with an architect about how a plan set is drawn in the morning and write the query that tests your hypothesis about it in the afternoon. You know the difference between a demo and a deliverable, and you're honest with customers about which one they're looking at. You have: - 5+ years of product management experience, including significant time in customer-facing or deployed settings—enterprise implementations, solutions engineering, technical consulting, or professional services. - Hands-on technical fluency: you write SQL, work in notebooks, script against APIs, and interrogate a data set yourself rather than requesting a pull. - Experience prototyping to validate ideas quickly using tools like Cursor, Replit, or V0.dev. - A track record defining structured data models, taxonomies, or classification schemes and getting a business to actually adopt them. - Strong judgment about data quality—what level of accuracy a decision requires, and what it costs to get there. - Excellent written and verbal communication, including with executive stakeholders who have limited time and no patience for status without substance. - Willingness to travel to client sites and company events up to 30% of the time." Then "A major plus if you also bring:" list: - Background in residential construction, homebuilding, architecture, or AEC technology—especially fluency with plan sets, elevations, options, and how builders manage plan variation. - Experience with agent-based or natural-language search over structured data, RAG systems, or LLM-powered analytics. - Exposure to geometric or spatial data—CAD/BIM, computer vision on drawings, similarity and clustering methods. - Experience with large, messy, enterprise-scale data migrations or ingestion programs. - Experience building a function from zero: first hire into a new team, new practice, or new delivery model. We need to include these as either Requirements or Qualifications/Skills. Let's decide: We'll have a section "Requirements" for the required items (the "You have:" list). Then a section "Qualifications" for the "major plus" items. Or we could combine them under "Requirements" and note which are preferred. But better to separate as per headings. Thus:
Requirements
with- of required items.
- items. Schedule: from earlier: "Higharc is fully remote; you can sit anywhere in the continental U.S., with travel to client sites and company events up to 30% of the time." Also later: "Remote work and travel: 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." We need to preserve all substantive info. So schedule section includes remote work, travel up to 30%, regular team meet-ups in hubs across US, prioritize hiring in those hubs, etc. We should not include boilerplate like "Please note: we are seeing an uptick of fraudulent recruiting activity..." Remove. Also remove duplicated lines. Now produce HTML fragment. We
Qualifications
with- of preferred items.
Skills: maybe we could include technical skills like SQL, notebooks, APIs, etc. But those are already in requirements. Could create a Skills section for those technical skills, but that would be redundant. The instruction: prefer a few substantive sections over many thin ones. So maybe we omit Skills section and include technical skills within Requirements.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Schedule.
Now Benefits: from "Compensation and benefits:" paragraph.
"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."
We need to preserve all detail. We'll put as