About the role
About Doss DOSS is building an Operations Cloud for the real world. A modern, AI-native platform for physical product businesses to manage the flow of goods, dollars, and data in real time, across: Procurement Inventory Orders Fulfillment Finance Built to replace spreadsheet chaos and rigid, consultant-heavy ERPs. Fast time-to-value, adaptable as the business evolves. Through our Adaptive Resource Platform (ARP) and unified operational data model, teams deploy quickly, automate workflows, and make changes without months of re-implementation. We recently raised a $55M Series B , co-led by Madrona and Premji Invest. Participation from Intuit Ventures, Theory Ventures, General Catalyst, Contrary Capital, and Pathlight VC. DOSS is trusted by fast-growing operators to run critical operations with speed, control, and confidence.
About
the Role As a Senior Product Manager on our Foundations team, you'll own the primitives that everything at Doss is built from: tables, workflows, interfaces, dashboards, navigation, permissions, and mobile. These are the building blocks our internal solutions teams assemble into customer instances, and the interface through which our customers interact with Doss every day. That gives you two sets of customers. The first is internal and external teams who build and configure customer instances on top of Doss. The second is the end customers who use what those teams build. Your job is to make both the building blocks and the experiences they create more capable, more composable, and easier to work with. This is a systems role. The decisions you make are about primitives, composability, and building the right level of abstraction that ripples across every part of the product. We've found that people who've built platforms, infrastructure, or developer tools products tend to think in exactly this way, which is why we're especially excited about candidates from that background. Your computer science background and or prior experience as a software engineer will help you go deep with the engineering team and reason about the technical implications of product decisions. Over time, the engineering team will break into dedicated product areas, each with its own engineering team focused on a single core product (tables, workflows, interfaces, mobile, and so on). You'll help shape how that evolution happens and where those lines get drawn.
