Sr. Product Manager - Strategic Integrations

Dealerware•Austin, TX

About The Position

Dealerware transforms the automotive retailers of today into the mobility network of tomorrow. Launched in 2016, Dealerware manages tens of thousands of vehicles at dealerships in North America across every major manufacturer brand. Dealerware is committed to being a people-first culture and a great place to work for all, with flexible scheduling, unlimited PTO, extensive benefits, a core value of Diversity, Equity & Inclusion, and a leadership and management team that defaults to being supportive and accessible. In 2026, Dealerware was recognized by Built In as one of their Best Startups to Work for in Austin for the fifth consecutive year. The Sr. Product Manager - Strategic Integrations is responsible for defining and executing Dealerwareâs integration strategy across DMS platforms, scheduling systems, OEM environments, and strategic partners. This role ensures integrations strengthen the core product, preserve proprietary logic, and support revenue growth across vertical offerings. This role is responsible for how Dealerware incorporates external capabilities into the product. It ensures third-party inputs are structured, enhanced, and embedded in ways that create differentiated value owned and operated by Dealerware. Build versus partner decisions are made based on long-term control, margin impact, and product scalability. This position reports directly to the Chief Product Officer and operates as a senior individual contributor with cross-functional accountability.

Requirements

7+ years of Product Management experience in B2B or B2C environments.
Experience owning integration platforms, ecosystem products, or shared infrastructure domains.
Demonstrated track record launching and scaling enterprise integrations with measurable business impact.
Strong understanding of API-driven architectures, system boundaries, and multi-system data exchange.
Experience evaluating build versus partner decisions with clear economic and architectural trade-off judgment.
Ability to operate comfortably in technical and business discussions and translate architectural decisions into commercial outcomes.
Strong cross-functional leadership and stakeholder alignment skills.
Systems thinker who prioritizes reusable architecture over one-off features.
Evaluates integrations based on margin impact, revenue contribution, scalability, and product control.
Comfortable operating in technical discussions and making architectural trade-offs under ambiguity.
Consistently connects product decisions to measurable business outcomes.

Nice To Haves

Experience working within the automotive dealership software ecosystem, including major DMS and related systems.
Experience in structuring strategic technology partnerships beyond simple technical integrations.
Experience scaling integrations across multi-tenant SaaS platforms.
Experience operating in regulated or compliance-sensitive environments.
Experience contributing to margin improvement or revenue expansion through integration strategy.

Responsibilities

Define how external systems connect to Dealerware and function within the core product.
Core System Integrations: Define repeatable API patterns for DMS, scheduling, CRM, and OEM systems. Set clear boundaries and data contracts. Keep decision logic and workflow control inside Dealerware.
Strategic Partner Integrations: Evaluate and structure third-party integrations to expand capabilities. Retain control over workflow design, user experience, and revenue/pricing models. Limit pass-through integrations and support them only when strategically required.
Build vs Partner Decisions: Assess trade-offs based on long-term control, margin impact, and reuse across customers. Align decisions with product architecture and roadmap priorities.
Platform & IP Control: Define how external capabilities are embedded into Dealerware in ways that preserve proprietary logic, protect margin, and increase long-term enterprise value. Ensure integration decisions expand internal IP rather than create vendor dependency.