Product Manager, Applications

DOSS•San Francisco, CA

4d•Onsite

About The Position

DOSS is building an Operations Cloud for the real world, offering a modern, AI-native platform for physical product businesses to manage the flow of goods, dollars, and data across procurement, inventory, orders, fulfillment, and finance. The Applications Team is DOSS's product engine for modules like Order Management, Inventory, Procure-to-Pay, Warehouse Management, MRP, and Production Planning. This role is for the first Product Manager on this team, who will own the product surface for one of two pods (Core Operations or Frontier modules) from discovery to release. This is a build PM role focused on creating generalized, scalable products, partnering with architects on data models, sequencing the roadmap, ensuring release readiness, and managing relationships with the implementation team. The ideal candidate has a strong track record of shipping products in the operations, ERP, finance, or supply chain space and possesses deep ERP domain fluency.

Requirements

Shipped real, generalized product surfaces in at least one of: inventory, procurement, OMS, AR/AP, costing, fulfillment, EDI, WMS, MRP, production planning.
Speaks the language fluently — UoMs, BOMs, lot tracking, 3-way match, COGs, ASNs — without being asked.
Owned a product end-to-end at meaningful complexity. You can name a specific product you shipped, the trade-offs you made, the scope you cut, the revenue or adoption it drove, and what you'd build differently today.
Designed for the Nth customer, not the first. You've held the line on what's opinionated vs. configurable and can articulate the rule you actually used.
Partnered substantively with engineering. You've defended scope that shipped and updated PRDs that needed updating. You can name your favorite engineer and architect from your last team and tell us why.
Written for executives. You can sit with a pile of messy discovery notes and produce a one-page memo a CEO can act on in 60 seconds.
Systems Thinker. Operations software is highly interconnected - data, workflows, modules, integrations, customers, and finance all touch each other. You can traverse it, untangle it, and put it back together.
High-Intensity. You have a track record in high-pressure roles - startups, consulting, finance, top-tier physical-ops orgs. These are your real preferences, not your stated preferences.
Technical from 1st Principles. You can grok data models, schemas, and engineering trade-offs from intuition, not memorization. You know when to push back on architecture and when to update.
Product Taste. You can look at a product surface and tell what's wrong in seconds. You have specific opinions on defaults, configurability, and what the user is being asked to decide.
Intellectual Firepower. You cut through noise, synthesize, and get to the right answer fast.
Low Ego, High Standards. You work best alongside other A+ players, push hard on quality, and don't take it personally when someone pushes back on yours.
PM at a vertical-ERP / ops-software company (NetSuite, SAP, Microsoft Dynamics, Oracle) — has shipped products for inventory, procurement, order management, AR/AP, costing, fulfillment, or EDI.
PM or engineer at a manufacturing or physical-operations company that builds its own software to run operations (Tesla, Amazon, Walmart, Flexport).
Operations / ERP / supply-chain consultant turned PM — Big 4, Accenture, BCG, Bain, or NetSuite/Workday implementation partner.
PM with finance / accounting / industrial-engineering background at a high-bar B2B startup (Stripe, Ramp, Mercury, Rippling) ready to go deeper into the operations world.

Responsibilities

Own the end-to-end product surface for your pod - discovery, PRDs, system design partnership, release readiness, and adoption - across OMS/IMS/P2P (Bootloader) or WMS/MRP/PP (Frontier).
Run customer discovery directly and through PMO. Translate messy, conflicting, multi-customer input into generalized capabilities that work for the Nth customer, not just the first.
Write tight, opinionated PRDs that engineers and architects can build against. Ship docs that hold up under technical pushback and don't need rewriting two months later.
Partner daily with the Applications Architects on data models, schemas, workflows, and integrations. Co-design the product and the architecture. Hold the product line under technical pressure; update cleanly when a real constraint changes the right answer.
Sequence the application roadmap. Cut hard. Phase ruthlessly. Defend the trade-offs to the SLT, to PMO, and to customers.
Enforce release readiness and QA across your pod. Decide what ships and what holds.
Operate as the bridge between Applications and PMO — the team implementing your modules with live customers. Triage their feedback, decide what generalizes vs. what's a config vs. what's a no, and close the loop.
Contribute to the fused AOP (Applications, OS, Platform) roadmap with Product and Engineering. Brief Sales/GTM on what's shipping and when.