Senior Product Manager | Forward Deployed

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. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also remove "Why This Role Is Different" maybe part of About the role? We'll need to parse content. Let's extract sections: Job description text: "Senior Product Manager — Forward Deployed Engineering At Epicor, we are building the world's first cognitive ERP, and Forward Deployed Engineering is how we prove its value inside our most strategic accounts. We are looking for a product manager with a builder's mindset to own this team and drive the underlying product strategy. As the Senior Product Manager, Forward Deployed Engineering (FDE), you will work with an embedded team of engineers working on-site with customers. You will help own the strategy, roadmap, and outcomes for the solutions they ship. In this role, you will establish the operating model for strategic account engagement, prioritize key technical problems, and scale field learnings into durable improvements for Epicor's core platform. This is a hands-on role that will guide and grow the FDE team, partner directly with customers and executives, and make critical technical decisions. You will also build and prototype solutions directly when speed demands it. This role offers true ownership, direct customer access, and a mandate to move fast." That's about the role. Next: "Why This Role Is Different ..." Could be part of About the role or separate. We'll treat as part of About the role. Then "What You Will Be Doing" list of responsibilities. Then "What You Will Likely Bring" list of qualifications/skills. Then "What Will Set You Apart" maybe additional qualifications. Then "MB2 About Epicor" maybe about company; not needed? Might be considered boilerplate? It's about Epicor but not required sections; we could include as About the company? Not required heading. Probably ignore. Then "Competitive Pay & Benefits" with bullet list of benefits. Then "Equal Opportunities and Accommodations Statement" - boilerplate to remove. Then "Range Minimum: $105,000 USD Maximum: $178,000 USD" - Pay info. Then "Recruiter Matthew Brady" - maybe minor metadata; we can fold into short p or drop. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have responsibilities (What You Will Be Doing). We have qualifications/skills (What You Will Likely Bring + What Will Set You Apart). Could split into Requirements (maybe mandatory) and Qualifications (preferred) and Skills (maybe technical). But we need to follow instruction: Use headings for those sections if content exists. We can decide to combine. We must not create sections with filler like "not specified". Schedule not mentioned; we should not create Schedule section. Pay we have range, so include Pay section. Benefits we have list, include Benefits section. About the role: we have description. Responsibilities: list from "What You Will Be Doing". Requirements: maybe "What You Will Likely Bring" includes mandatory qualifications? It says "What You Will Likely Bring". Could treat as Requirements. Qualifications maybe "What Will Set You Apart" as preferred qualifications. Skills maybe we can extract technical skills from those lists. But we must not invent content. We need to preserve all substantive info. So we need to include all points from those lists under appropriate headings. We could have:

About the role

... (combined description)

Responsibilities

• ... each bullet from "What You Will Be Doing"

Requirements

• ... each bullet from "What You Will Likely Bring"

Preferred Qualifications

• ... each bullet from "What Will Set You Apart"

But the instruction only lists headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It does not mention "Preferred Qualifications". However we could put "Qualifications" for the "What Will Set You Apart" and maybe "Skills" for technical skills? But we need to not create headings without real content. We have content for Qualifications (the "What Will Set You Apart") and Skills (maybe we can extract skills from both lists). However we risk splitting content arbitrarily. Better approach: Use the headings as given, but we can map content: - About the role: description. - Responsibilities: "What You Will Be Doing". - Requirements: "What You Will Likely Bring" (these are likely required). - Qualifications: maybe we can treat "What Will Set You Apart" as qualifications (preferred). - Skills: we could extract technical skills from both lists, but that would be duplicating or summarizing. Might be better to omit Skills heading if no distinct content not already covered. But we need to decide if we have content for Skills. The lists include technical skills like "hands-on technical background building and maintaining software, rapid prototyping skills in modern languages", "experience integrating software in enterprise environments, including APIs, data pipelines, authentication/SSO, and cloud platforms", "experience building or leading a forward-deployed, solutions engineering, or technical delivery function", "hands-on experience deploying AI/ML or LLM-based solutions to production, including RAG, prompt engineering, agentic orchestration, and model evaluation", "experience developing enterprise pricing, packaging, and ROI value models", "familiarity with ERP, manufacturing, distribution, retail, or supply chain workflows", "familiarity with ETL processes and data pipeline concepts". Those could be considered skills. But they are already in Requirements/Qualifications. If we create Skills heading, we would be duplicating content, which might be okay but risk of redundancy. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Duplicating is not inventing, but could be considered redundant but still preserving. However they might prefer not to repeat. Safer to not create Skills section if we can't find distinct skill-only content not already captured. But we could create Skills section with the technical skill bullets extracted from the lists, but then we would be omitting them from Requirements/Qualifications, losing detail. So better to not have Skills section; we can omit it if no unique content. Similarly Benefits: we have list. Pay: we have range. Schedule: not mentioned, so omit. Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to ensure we don't include boilerplate like "Equal Opportunities..." etc. Now craft HTML. We need to parse the description for About the role: combine first paragraph plus "Why This Role Is Different" maybe. Let's extract About the role text: "Senior Product Manager — Forward Deployed Engineering At Epicor, we are building the world's first cognitive ERP, and Forward Deployed Engineering is how we prove its value inside our most strategic accounts. We are looking for a product manager with a builder's mindset to own this team and drive the underlying product strategy. As the Senior Product Manager, Forward Deployed Engineering (FDE), you will work with an embedded team of engineers working on-site with customers. You will help own the strategy, roadmap, and outcomes for the solutions they ship. In this role, you will establish the operating model for strategic account engagement, prioritize key technical problems, and scale field learnings into durable improvements for Epicor's core platform. This is a hands-on role that will guide and grow the FDE team, partner directly with customers and executives, and make critical technical decisions. You will also build and prototype solutions directly when speed demands it. This role offers true ownership, direct customer access, and a mandate to move fast. Why This Role Is Different The forward deployed engineering model places technical talent directly at the point of action. Engineers operate where the problems live, feeding critical insights back into the core product. Leading this function is one of the highest-leverage product roles in the company because you sit at the intersection of customer reality and the product roadmap. For our customers, the work lives on the shop floor, in the warehouse, in the distribution center, and in the retail back office. Building a workflow in a sandbox is only a small fraction of the challenge. Success requires navigating complex enterprise realities: legacy data models, decades-old integrations, SSO security reviews, compliance constraints, and building trust with customer teams. Your job is to lead a team that consistently navigates these complexities and transforms breakthroughs into reusable patterns for future deployments. Agentic AI is shifting the traditional boundaries between Engineering, Product, UX, and Data Science. We need a leader who can span these disciplines. You need the engineering depth to evaluate architecture trade-offs, the product judgment to decide what is worth scaling, the empathy to design functional workflows, and the executive presence to lead a room of client stakeholders." We'll combine into a paragraph or multiple paragraphs. Use

for prose. Now Responsibilities: list from "What You Will Be Doing". Let's extract each bullet: - Lead and scale the team: Build, mentor, and grow the Forward Deployed Engineering team. Set high standards for customer engagement, solution delivery, and knowledge sharing. - Own the product and roadmap: Manage the lifecycle of field-developed capabilities into a coherent, multi-year roadmap. Decide which solutions become reusable product features and which remain custom, partnering with executive leadership to align strategy. - Define the operating model: Establish how FDE engagements operate, including account selection, resource staffing, discovery, deployment, and platform integration. - Stay technical and hands-on: Evaluate architecture designs, review technical trade-offs, and build rapid prototypes when needed to maintain momentum and earn team trust. - Work backwards from the customer: Lead discovery and advisory sessions with strategic accounts to uncover high-value problems, ensuring customer needs drive development. - Execute cross-functionally: Coordinate with engineering, data science, UX, marketing, and field teams to maintain development urgency and align customer feedback with the broader roadmap. - Drive go-to-market and value: Partner with Product Marketing and Sales on engagement expansion. Develop pricing, packaging, and ROI models grounded in measurable customer value. We'll put each as

. Now Requirements: from "What You Will Likely Bring". Extract bullets: - Player-coach leadership: Ability to lead a technical team from the front, raising engineering standards and removing blockers through active participation. - Builder's instincts: Background building and maintaining software, with a strong capability to move from concept to working prototype quickly. - Product judgment: Sharp analytical skills to evaluate field data and determine what should be turned into platform features, reusable patterns, or isolated solutions. - AI-native thinking: Solid understanding of LLMs, RAG, agents, and AI-driven software to set technical direction and evaluate team engineering bets. - Customer obsession: Proven experience leading technical customer discovery and designing solutions based on operational empathy. - Executive presence: Clear communication skills to articulate product vision to engineers, operators, and CIOs alike, with the confidence to defend technical positions. - Bias toward action: Ability to move fast, make decisions with incomplete information, and prioritize shipped and adopted software. - 5+ years of combined product management and engineering experience, with a track record of launching and scaling software products. - Hands-on technical background building and maintaining software, along with rapid prototyping skills in modern languages. - Experience leading or mentoring technical teams as a manager or tech lead. - Direct customer-facing experience managing technical and business stakeholders, including executive leadership. - Experience integrating software in enterprise environments, including APIs, data pipelines, authentication/SSO, and cloud platforms. - Bachelor's degree in Computer Science, Engineering, Business, or a related field; or equivalent practical experience. - Willingness to travel to customer sites (typically 20% to 40%). Now Qualifications: from "What Will Set You Apart". Extract bullets: - Advanced degree, such as an MBA or Master's in Computer Science or AI/ML. -