OverviewAbout This Position: The
Product Owner owns a defined product area end to end: the Lexus.com Offers program plus a portfolio of internal tools for the Lexus Dealer Association (LDA) and Team One's own operations, such as FlightDeck (Ad-ID and traffic management), the Facebook Tool, Click-to, dealer-site launches, and custom finance tools.
Offers is a distributed system that no single team owns end to end. Offers are configured upstream in OAT by our 5A team, the platform and endpoint belong to an external partner (5&Done), and the Lexus.com rendering logic is built by our scrum teams. The Product Owner is the person who holds the whole flow together. You evaluate every incoming request, decide where it should go, write the tickets, and validate the result in production.
On the internal-tools side, you run the product for a small dedicated engineering team. You turn requests from Traffic, Business Affairs, Finance, and LDA stakeholders into a prioritized backlog, and you see each release through.
This is a mid-level role. You own your area day to day without needing close direction, and you report to the Director, Product & Innovation.
What You'll DoProgram Ownership & Request Intake (Offers)- Serve as the single intake point for Offers changes and bugs. Evaluate each request for its impact on data transformation, business logic, UI/rendering, content, and downstream tools.
- Route each piece of work down the right path. Minor fixes go to LCOM or LDA Tools. Logic and data changes go to the Psyduck or Meerkat scrum teams. Large initiatives get estimated and planned. Upstream OAT changes go to the platform partner, copy and disclaimer changes go to Content, and unclear behavior gets a research spike.
- Represent Product in the biweekly Incentive Status meeting with Account and 5A, and in the weekly Offers sync owned by the platform partner. Help manage dependencies and priorities across teams.
- Maintain RACI, use-case flows, and runbooks so that everyone knows who owns what across the Client, Account, 5A, platform partner, dev teams, and Content.
Backlog & Delivery- Write epics, stories, spikes, and bugs in Team One's ticket format (Tool Area | Role | Component | Description), with clear acceptance criteria. Split work by discipline (XD/VD, BE, UI, Content).
- Run refinement with engineering and design. Get stories to Definition of Ready, and partner with Platform Producers on sprint planning and release timing.
- Make sure every change has a ticket. Own traceability, follow-up, and closure.
- Shape regulatory and compliance work into deliverable scope. One example is the California EV incentive programs (MyFirstEV / MyLexusEV), which included ZIP-code targeting and content authoring guides.
Validation, Quality & Incident Response- Own pre-release validation: endpoint checks, functional QA, and staging review.
- Run monthly post-release validation. That means a full endpoint review for completeness and consistency, plus ZIP-code testing across West, East, North, and South regions.
- Monitor Offers health. Lead triage when production breaks, write or coordinate the RCA, and turn its lessons into resiliency work such as data health checks, monitoring, and OAT validation.
- Accept stories only when they meet the agreed criteria.
Internal & LDA Tools Product Ownership- Own the roadmap and backlog for a portfolio of internal tools. Examples include FlightDeck 2.0 (Ad-ID creation, Donovan codes, bulk upload), the Facebook Tool, Click-to, LMDS, DIS validations, new dealer-site launches, and a custom finance tool (SSO provisioning, roles, access control).
- Work day to day with a small dedicated engineering team. Set priorities, unblock work, and agree ETAs.
- Partner with internal users (Traffic/Ad Ops, Business Affairs, Finance, LDA) to turn their real workflow pain into scoped enhancements. Evaluate integration requests from partners and vendors.
Documentation & Product Expertise- Become the go-to expert on how your products behave, including their business rules, data sources, and system dependencies.
- Keep Confluence documentation current, including program overviews, process flows, authoring guides, and status pages, so that the product can survive handoffs.
- Use AI tools to speed up analysis, documentation, and validation.
What You Bring- 3-5 years of experience in Product Ownership, Product Management, Business Analysis, or a related technical role on digital products.
- A Bachelor's degree in Computer Science, Information Systems, Business, or a related field, or equivalent practical experience.
- A track record of owning a backlog end to end: gathering requirements, writing user stories with clear acceptance criteria, prioritizing, and accepting work.
- Working knowledge of Scrum and the software development lifecycle, and comfort as a full member of a scrum team.
- Enough technical fluency to reason about data flowing from an upstream API into a front end. That includes reading an endpoint response, spotting a data problem versus a rendering problem, and talking through feasibility with engineers.
- Hands-on QA and UAT habits. You test in staging and production yourself rather than relying only on reported results.
- Experience coordinating across several teams, including external partners or vendors, where you hold the process together without formal authority over every party.
- Clear written communication, both docs and tickets that other people can pick up and act on, and the ability to explain technical issues to Account and client-facing teams.
- Calm, structured judgment during production issues, from triage through RCA to follow-up.
Nice to Have- Experience with Jira, Confluence, Postman, and API documentation.
- Familiarity with Adobe Experience Manager (AEM) or another content management system, including content fragments and authored configuration.
- Experience with automotive retail, dealer networks, incentive or pricing programs, or other regulated offer content.
- Exposure to ad operations or media workflows, such as Ad-ID, traffic, and trafficking platforms.
- Experience with monitoring and observability tools (for example, Dynatrace) or data-validation checks.
- Practical use of AI tools (Claude, ChatGPT, Copilot) for analysis, documentation, or prototyping.
- Spanish/English bilingual, which helps when working with our nearshore engineering partners.