ForgeApply · Job listing
Principal Product Manager | Prism Workflow Engine
Epicor
See all 28 open roles at Epicor →
Tailor your resume for this Epicor job in about a minute.
ForgeApply tailors your resume and cover letter to this exact posting, then hands you a ready-to-submit application for Epicor's site. Free trial, no card required.
About this role
Overview Every product built on Prism eventually needs to do real, multi-step work against the ERP, not just retrieve information. The Workflow Engine is the shared foundation that makes that a customer’s quote to cash work via AI systems reliable, reversible, auditable, and reusable. You own the product definition of that foundation: how a unit of work is represented and tracked from start to finish, how information is handed off cleanly between different parts of the system, how much autonomy an AI agent gets based on how reversible its action is, and the approval, policy, and audit systems that make the engine safe to point at real production data.
This is a foundational product role. You will take the Workflow Engine from its initial build through to market launch: deciding what ships first, resolving key open questions about how the system should behave, and building the case for the resources needed to get there.
Epicor
Epicor is a technology leader in ERP software for manufacturing, distribution, and retail, with deep roots in both enterprise software and startup culture. Our product organization is in the middle of a deliberate move to a platform-first, AI-enabled delivery model: building shared capabilities that many teams can build on, broadening how roles work together, and removing the silos and handoffs that slow good teams down.
How This Team Works
The biggest change versus a traditional PM job is how the work gets done. We expect this leader to operate fluently in the model below, and to help the rest of the org adopt it.
• Built as a platform, not a feature. The Workflow Engine is built for the other product teams, consulting teams, and customers that will build on it. Ease of adoption, reuse of shared building blocks, and a clear path for a new team to get their first workflow running are treated as first-class goals, not afterthoughts. Success is measured by how much operational work in the ERP is done via the workflow engine vs. manually.
• A small, senior team, not a feature factory. Delivery happens in a lean, senior, cross-functional team working closely together against a system with built-in human oversight. You are inside that loop as the product decision-maker, not reviewing status from the outside.
• Roles blur on a team like this. The lines between product, engineering, design, and architecture blur on a team this size. You work directly in specs, cross-team sequencing decisions, and pilot results, not a backlog handed over a wall. You keep clear ownership of product scope and decisions while picking up adjacent work that a small team requires.
• Responsibility is the differentiator. How reversible an action is (fully reversible, reversible within a limited window, or effectively permanent) determines how much autonomy an AI agent gets to take it. Policy, approvals, and a clear audit trail are product features you own, not compliance add-ons, because they're what let a customer trust the system with real business decisions.
• Share openly. Open questions, pilot results, and test outcomes are shared across the org so people can see clearly what the engine can and can't yet promise.
What We’d Love to See
• Empathy for two different customers. Real understanding of the end customer whose order, supplier requalification, or month-end close runs through the engine, and of the engineering teams deciding whether to build on it or build around it. You validate both before committing to a build.
• A platform mindset. You think about ease of adoption, reusable building blocks, and how many teams choose to build on your system the way a good platform product manager thinks about retention, not the way a feature team thinks about a single roadmap.
• Working Backwards: Demonstrates mastery of customer empathy, working backwards from customer pain points to validate the customer problems, ideal customer profiles, and value propositions.
• Founder Mode' Mindset: Demonstrates an entrepreneurial spirit by taking full ownership, embracing creative problem-solving, and relentlessly challenging the status quo to drive innovation and continuous improvement.
• Prototyping Pro : Quickly generates prototypes to get early feedback from internal stakeholders and customers
• Strategic Direction & Prioritization: Lead the orchestration of strategic direction and set priorities for our AI applications and functionalities. Define the vision and roadmap that drive innovation in AI-driven products.
Duties & Responsibilities
• Own the product vision and build sequence. Decide what ships first as you take the Workflow Engine from its initial build to market, and keep the roadmap tied to real demand from the teams that want to build on it, not to technical completeness for its own sake.
• Define how work is represented and handed off. Own the core concepts that make the system work: how a unit of work is tracked from start to finish, and how information is passed cleanly between different parts of the system so nothing gets lost along the way. These are the two things every team building on the engine depends on.
• Own the full system, not one piece of it. Be the single product owner across all of the engine's functional areas: authoring (the tools people use to build and edit a workflow), execution (running workflows and connecting them to the ERP), quality (automated testing, simulation, and health monitoring), and governance (policy, approvals, and audit trails). Make the sequencing and trade-off calls that span all of these.
• Own risk classification and approvals as a product, not a policy document. Own the system that classifies how reversible a given action is, and the framework that decides who needs to approve what, based on things like reporting structure, dollar amount, and risk level, and make sure that logic is built into the system rather than handled manually.
• Resolve open questions with the right partners. Drive resolution of open questions the technical
Tailor your resume for this Epicor role before you apply.
Tailor my resume for this jobSimilar jobs
- Senior Product Manager | Prism — Epicor · Dublin, United States | Milton, United States | Eau Claire, United States
- Senior Product Manager, Workflows — Boxinc · Redwood City, CA
- Product Manager - Workflows — Outmarket · Remote
- Senior Technical Product Manager — Customer Workflow — Futurefitai · Remote
- Sr. Staff Product Manager, Workflow Efficiency — Ironcladhq · San Francisco
- Principal Product Manager — Fox Corporation · New York, New York, United States
- Principal Product Manager — Zscaler · San Jose, California, USA
- Principal Product Manager — GE HealthCare · WA07-01-Bellevue-1100-112th Avenue NE
More like this: Product Manager Jobs · Browse all jobs
Free ATS checker · No Salary on the Job Posting? How to Find the Number Before You Interview