Senior Product Manager | Forward Deployed

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. 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 boilerplate, duplicated lines, application instructions). Also must not create sections with filler like "commensurate with experience". Must only include sections when posting has real specific content. We need to parse the posting. Let's extract sections: - About the role: The first paragraph(s) describing role: "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: Could be part of About the role or separate. Might be considered part of About the role. But we can include as part of About the role or maybe separate section "Why This Role Is Different". However headings list only includes certain headings; we can only use those headings. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings. Likely we should only use those exact headings. So we need to map content to those headings. Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only those that have real specific content. Let's extract content for each. Responsibilities: The "What You Will Be Doing" bullet list. Requirements: Might be "What You Will Likely Bring" (the list of qualifications). Could be considered Requirements. Qualifications: Possibly the education and experience list (Bachelor's degree etc). Could be separate. Skills: Could be the "What Will Set You Apart" (preferred qualifications) or the specific skill sets. Benefits: The "Competitive Pay & Benefits" section includes benefits list. Pay: The salary range: "Range Minimum: $105,000 USD Maximum: $178,000 USD". Also note that they say it's national average etc. We should include the range as Pay. Schedule: Travel willingness: "Willingness to travel to customer sites (typically 20% to 40%)." That's schedule/travel. Could be considered Schedule. We must not include filler like "commensurate with experience". Not present. We must remove boilerplate: EEO statement, equal opportunities, recruiter name, etc. Also remove "MB2 About Epicor" maybe? Actually there is "MB2 About Epicor". That seems like a stray marker. We'll ignore. Also remove "Equal Opportunities and Accommodations Statement" etc. Also remove "Recruiter Matthew Brady". Also remove internal mobility etc? Those are benefits; we keep benefits. Now produce HTML. Structure:

About the role

... (combined paragraphs about role and why it's different maybe). We'll combine.

Responsibilities

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

Requirements

• ... from "What You Will Likely Bring" (player-coach leadership etc).

Qualifications

• ... from education/experience list: 5+ years combined product management and engineering experience, hands-on technical background, experience leading/mentoring technical teams, direct customer-facing experience, experience integrating software in enterprise environments, Bachelor's degree in CS, Engineering, Business, or related field; or equivalent practical experience, willingness to travel 20%-40% (maybe schedule). But travel maybe schedule. We'll keep travel under Schedule.

Skills

• ... from "What Will Set You Apart": advanced degree, experience building/leading forward-deployed function, hands-on experience deploying AI/ML or LLM-based solutions, experience developing enterprise pricing, packaging, ROI models, familiarity with ERP, manufacturing, distribution, retail, supply chain workflows, familiarity with ETL processes and data pipeline concepts, history of converting bespoke customer work into scalable platform capabilities.

Benefits

• ... from Competitive Pay & Benefits bullet list: Health and Wellness: Comprehensive health and wellness benefits..., Internal Mobility: Opportunities for mentorship..., Career Development: Free LinkedIn Learning licenses..., Inclusive Workplace..., Work-Life Balance..., Global Mobility...

Pay

Salary range: $105,000 USD – $178,000 USD (national average; actual compensation varies based on experience, qualifications, market factors).

Schedule

Willingness to travel to customer sites typically 20% to 40%.

We must ensure we don't include any boilerplate like "Equal Opportunities and Accommodations Statement". Also remove "MB2 About Epicor". Also remove "Recruiter Matthew Brady". Also remove "The salary range provided reflects the national average for this job title and does not represent compensation specific to Epicor Software Corporation." Might be considered boilerplate but it's part of Pay description; we can keep brief note but maybe it's okay. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The salary range note is not exactly those categories; it's still part of Pay. Might keep but could be considered legal? It's a disclaimer. Might be safe to keep brief. We must not invent or summarize away detail. We must preserve ALL substantive information. So we need to include all details from each bullet. Let's extract each bullet precisely. From "What You Will Be Doing": - 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. From "What You Will Likely Bring": - 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%). From "What Will Set You Apart": - Advanced degree, such as an MBA or Master's in Computer Science or AI/ML. - 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. - A history of successfully converting bespoke customer work into scalable platform capabilities. From "Competitive Pay & Benefits": - Health and Wellness: Comprehensive health and wellness benefits designed to support your overall well-being. - Internal Mobility: Opportunities for mentorship, continuing education, and focused career goal setting, with 25% of positions filled internally. - Career Development: Free LinkedIn Learning licenses for everyone, along with our Mentoring Program to boost your personal development. - Inclusive Workplace: Collaborate with a diverse team in an inclusive, global workplace that fosters innovation and celebrates partnership. - Work-Life Balance: Policies built on mutual trust and support, encouraging time off to rest, recharge, and reconnect. - Global Mobility: Comprehensive support for international relocations and permanent residency processes. We also have a paragraph about Epicor culture etc. That could be part of About the role? Actually it's after "MB2 About Epicor". It's a description of company. Might be considered "About the role" or maybe not needed. The instruction: "Preserve ALL substantive information". So we should include that description somewhere. Could be part of About the role or maybe a separate section like "About Epicor". But headings list doesn't include About Epicor. Could we include it under About the role? Probably we can add a paragraph after the role description about Epicor's mission. That is substantive. Thus About the role section will include: - First paragraph(s) about role and why it's different. - Then the Epicor culture paragraph. We must not include the "MB2 About Epicor" marker. Now produce HTML. We must output only HTML fragment, no markdown fences. Let's craft. We'll need to escape any HTML special characters? Not needed. We'll produce:

About the role

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