Senior Technical Product Manager, SourceDay

• 4+ years in product management, including at least two owning technical surfaces — APIs, integrations, or data infrastructure — rather than end-user features
• 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
• Enough comfort with data to answer your own questions in SQL rather than filing a request and waiting
• 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
• An Austin address or willingness to relocate. This is a hybrid role, three days per week in office
• We know the confidence gap and imposter syndrome can get in the way of meeting great candidates. If you read this and hesitated, apply anyway

Desirable

• Reports to: Head of Product, Data & AI
• This role owns the platform layer beneath SourceDay’s application experience: the ERP integrations that feed the product, the data platform those integrations land in, and the API surface that lets customers and their systems build on SourceDay directly. Application workflows and user experience are owned separately, so your attention stays on the systems underneath
• You will also be the product owner on our most technically involved professional services engagements. When an enterprise customer arrives with a nonstandard ERP footprint or a multi-site rollout, you decide what becomes a supported product capability and what stays a configuration we can live with
• You'll own how this area is discovered, prioritized, and measured, working within an established engineering delivery process and directly with engineering leadership and customers
• ERP integrations. Roadmap and health of our connector portfolio. You define what "good" looks like for sync reliability, error handling, and onboarding time, then hold the line on it
• Data platform. The models, pipelines, and data quality standards that everything else depends on — including the data our AI and analytics features read from
• Public API. Treat our REST API as a product with real customers: versioning, authentication, rate limits, documentation, and a deprecation policy people can plan against
• Agentic readiness. Stand up MCP servers that expose SourceDay data and actions to customer-side AI agents, along with the permission scoping and audit trail that has to come with it
• Professional services projects. Partner with implementation and services on the biggest customer builds, and feed what you learn back into the platform roadmap instead of leaving it as one-off work
• Prioritization. Make the tradeoff calls between integration debt, new connectors, API investment, and customer-specific commitments, and explain those calls to the people they affect
• Measurement. Define and track the numbers that matter here: sync success rates, time to first successful integration, API adoption, support volume tied to integration failures
• ERP subject matter expertise. Be the internal go-to on ERP behavior, integration health, and what is actually possible in a given customer environment