Technical Product Manager

Join SourceDay as a Technical Product Manager, where you'll own the platform layer beneath our application experience, including ERP integrations, data platform, and public API. You'll work closely with engineering, customer-facing teams, and leadership, and have the opportunity to shape the development of a well-defined product area. Enjoy a healthy work-life balance, healthcare coverage, and the flexibility of remote work.

• Ownership of the platform layer beneath SourceDay’s application experience, including ERP integrations, data platform, and API surface.
• Defining and holding the line on what "good" looks like for sync reliability, error handling, and onboarding time for ERP integrations.
• Partnering with implementation and services on the biggest customer builds, and feeding what you learn back into the platform roadmap.

• An Austin address or willingness to relocate. This is a hybrid role, three days per week in office
• Enough comfort with data to answer your own questions in SQL rather than filing a request and waiting
• Practical knowledge of API design: REST conventions, authentication, versioning, pagination, idempotency, webhooks. You can read an OpenAPI spec and push back on an engineer’s proposal
• 4+ years in product management, including at least two owning technical surfaces — APIs, integrations, or data infrastructure — rather than end-user features
• A track record of turning a specific customer’s problem into something that works for the next twenty customers, and of saying no when it will not
• Clear written communication with engineers, customer-facing teams, and executives — often in the same document
• Supply chain, procurement, manufacturing, or distribution background
• Hands-on experience with at least one ERP or comparable system of record, and a working understanding of how order, receipt, and supplier data moves through it
• Depth across multiple ERPs, or experience with middleware such as Boomi, MuleSoft, or Workato
• Exposure to LLM tooling — MCP, function calling, retrieval — and opinions about what an agent should and should not be allowed to do with a customer’s data