Jobs · Marketing · Michigan

Senior Product Owner

700Credit · Southfield, MI · 1 mo ago
On-siteMarketingFull-time
We need to output HTML fragment with sections for headings present: About the role? Actually description includes "About 700Credit" then "Summary". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We have content: About 700Credit (company description) maybe treat as "About the role"? Actually "About 700Credit" is about company, not role. But we can still use heading "About the role"? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we can use appropriate headings based on content. We have "Summary" which could be considered role summary. Could use "About the role" heading for summary. Then "Responsibilities" heading. Then "Requirements" heading (includes Required Skills & Experience and Preferred Skills & Experience). Could also split into "Qualifications" and "Skills"? But we have both required and preferred; we could keep as Requirements section with subpoints. The instruction: Prefer a few substantive sections over many thin ones. So we can have sections: About the role (summary), Responsibilities, Requirements (combining required and preferred). Possibly also "Qualifications" but we can incorporate into Requirements. No Pay, Schedule, Benefits mentioned (though they said "offers an excellent compensation/benefit package" but no specifics, so we should NOT create Benefits section because no specific content. So omit. We need to use
  • for any list of duties/requirements/benefits. So under Responsibilities we need list items. Under Requirements we need list items for required and preferred maybe separate lists? Could do two lists: Required Skills & Experience and Preferred Skills & Experience each as
      . Or combine? Probably separate headings inside Requirements? But we said prefer few sections; we could keep Requirements section with two subheadings? But subheadings would be

      ? Not allowed? Only said use

      for section headings. Could still use

      for subheadings? Not prohibited but better to avoid extra headings. Could just make one list with all items, but we need to differentiate required vs preferred? Could keep as two lists with preceding

      indicating required vs preferred. That's acceptable. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all bullet points from responsibilities and requirements. Let's extract responsibilities list: - Own Product Strategy & Roadmap: Set the multi-quarter vision for the dealer and F&I product portfolio, aligned with company strategy and market opportunity rather than just feature-level roadmaps. - Drive Prioritization & Trade-off Decisions: Make the call on what gets built across competing initiatives, balancing value, dependencies, risk, and strategic fit, and defend those decisions with data. - Own Competitive Intelligence & Market Positioning: Maintain a current, in-depth view of the automotive credit, compliance, and F&I technology market to translate competitor insights into roadmap decisions that extend 700Credit's market leadership. - Lead the Product Development Lifecycle: Manage feature development across new and existing product lines end to end, balancing dealer needs, compliance requirements, and market demand. - Serve as F&I Domain Expert: Act as the product authority on the dealership finance workflow, including credit pulls, prescreen and prequalification, compliance, identity verification, fraud, and lender connectivity. - Mentor & Advance the Product Org: Coach other Product Owners on backlog management, story writing, and agile execution while partnering with the Agile Transformation Office to improve sprint planning and delivery outcomes. - Manage the Product Backlog: Create, refine, and prioritize the backlog based on value, dependencies, and strategic goals tied to customer requirements. - Author Functional Requirements: Partner with Business, Development, and QA to produce detailed Functional Requirements Documents and clear, testable user stories. - Define & Track Success Metrics: Establish KPIs and OKRs upfront, then measure ROI, adoption rates, and business impact post-release using tools like PowerBI. - Lead Stakeholder & Executive Communication: Deliver data-driven presentations to Senior Management and manage expectations across F&I, product design, credit reporting, and external partners including lenders and credit bureaus. - Guide UI/UX Enhancements: Partner with the UI/UX Designer to ensure dealer and F&I facing workflows are usable and aligned to strategic design goals. Now requirements: Required Skills & Experience: - 10+ years of experience as a Product Owner or Product Manager with a focus on automotive finance, F&I, lender technology, or credit and compliance solutions - Bachelor's degree in Business, Technology, Finance, or a related field, or equivalent work experience - Demonstrated strategic-level product ownership, including setting vision and roadmap rather than just executing a backlog - Experience mentoring or leading other product professionals - Proficiency with Azure DevOps or similar tools and experience managing products across web, mobile, and digital platforms - Strong track record collaborating with cross-functional teams including Marketing, Product Development, UX/UI, Strategy, and Compliance - Deep expertise in agile methodologies, credit bureau operations, and the automotive credit and F&I competitive landscape - Strong analytical, problem-solving, and executive-level communication skills Preferred Skills & Experience: - Direct experience in automotive F&I or dealership operations, including familiarity with DMS platforms and workflows such as menu selling and deal structuring - Familiarity with lender and credit platforms such as RouteOne and Dealertrack - Understanding of automotive lending, risk assessment, fraud prevention, and F&I compliance frameworks such as ECOA/Reg B, GLBA, Red Flags Rule, and OFAC - Experience with API integrations, SaaS product development, or large-scale digital transformation initiatives - Understanding of data security standards such as PCI-DSS and the NIST Cybersecurity Framework Also summary paragraph: "700Credit is looking for a reliable Senior Product Owner to join our team at our headquarters in Southfield, MI. The Senior Product Owner will lead the strategy, development, and growth of our dealer and F&I focused product lines. As a Senior Product Owner, you will own the product vision for a portfolio of solutions at the center of the dealership finance process, including credit reporting, prescreen and prequalification, compliance, identity and fraud, and lender connectivity. The ideal candidate should have strong skills in agile methodologies, competitive market analysis, and strategic product leadership. This role is essential to the continued success of 700Credit's expansion efforts and will have a direct impact on achieving company goals." Also about 700Credit paragraph: "About 700Credit 700Credit is the industry leader in providing cutting-edge credit and compliance solutions to the automotive sector. As the largest provider in the field, we are passionate about innovation, growth, and delivering the best for our clients. 700Credit is a dynamic, exciting place to work. 700Credit offers an excellent compensation/benefit package." We need to include that as maybe "About the role" or "About the company"? The instruction says use

      for section headings (e.g. About the role, Responsibilities...). So we can make a section "About the role" containing the summary paragraph. The "About 700Credit" could be placed as a short

      before the heading? Or we could incorporate into About the role? But the summary already includes role details. The about 700Credit is company description; we could include it as a brief

      before the heading or as part of About the role? Probably better to have a short paragraph about the company then heading About the role with summary. Since we cannot invent headings for company description, we can just put it as a

      before the first heading. Thus output:

      About 700Credit 700Credit is the industry leader in providing cutting-edge credit and compliance solutions to the automotive sector. As the largest provider in the field, we are passionate about innovation, growth, and delivering the best for our clients. 700Credit is a dynamic, exciting place to work. 700Credit offers an excellent compensation/benefit package.

      About the role

      700Credit is looking for a reliable Senior Product Owner to join our team at our headquarters in Southfield, MI. The Senior Product Owner will lead the strategy, development, and growth of our dealer and F&I focused product lines. As a Senior Product Owner, you will own the product vision for a portfolio of solutions at the center of the dealership finance process, including credit reporting, prescreen and prequalification, compliance, identity and fraud, and lender connectivity. The ideal candidate should have strong skills in agile methodologies, competitive market analysis, and strategic product leadership. This role is essential to the continued success of 700Credit's expansion efforts and will have a direct impact on achieving company goals.

      Responsibilities

      • Own Product Strategy & Roadmap: Set the multi-quarter vision for the dealer and F&I product portfolio, aligned with company strategy and market opportunity rather than just feature-level roadmaps.
      • Drive Prioritization & Trade-off Decisions: Make the call on what gets built across competing initiatives, balancing value, dependencies, risk, and strategic fit, and defend those decisions with data.
      • Own Competitive Intelligence & Market Positioning: Maintain a current, in-depth view of the automotive credit, compliance, and F&I technology market to translate competitor insights into roadmap decisions that extend 700Credit's market leadership.
      • Lead the Product Development Lifecycle: Manage feature development across new and existing product lines end to end, balancing dealer needs, compliance requirements, and market demand.
      • Serve as F&I Domain Expert: Act as the product authority on the dealership finance workflow, including credit pulls, prescreen and prequalification, compliance, identity verification, fraud, and lender connectivity.
      • Mentor & Advance the Product Org: Coach other Product Owners on backlog management, story writing, and agile execution while partnering with the Agile Transformation Office to improve sprint planning and delivery outcomes.
      • Manage the Product Backlog: Create, refine, and prioritize the backlog based on value, dependencies, and strategic goals tied to customer requirements.
      • Author Functional Requirements: Partner with Business, Development, and QA to produce detailed Functional Requirements Documents and clear, testable user stories.
      • Define & Track Success Metrics: Establish KPIs and OKRs upfront, then measure ROI, adoption rates, and business impact post-release using tools like PowerBI.
      • Lead Stakeholder & Executive Communication: Deliver data-driven presentations to Senior Management and manage expectations across F&I, product design, credit reporting, and external partners including lenders and credit bureaus.
      • Guide UI/UX Enhancements: Partner with the UI/UX Designer to ensure dealer and F&I facing workflows are usable and aligned to strategic design goals.

      Requirements

      Required Skills & Experience

      • 10+ years of experience as a Product Owner or Product Manager with a focus on automotive finance, F&I, lender technology, or credit and compliance solutions
      • Bachelor's degree in Business, Technology, Finance, or a related field, or equivalent work experience
      • Demonstrated strategic-level product ownership, including setting vision and roadmap rather than just executing a backlog
      • Experience mentoring or leading other product professionals
      • Proficiency with Azure DevOps or similar tools and experience managing products across web, mobile, and digital platforms
      • Strong track record collaborating with cross-functional teams including Marketing, Product Development, UX

Similar jobs

Senior Product Owner

Southwest AirlinesDallas, TX· 1 mo ago
Marketing$120k/yrapply on careers.southwestair.com

Senior Product Owner

Spectrum EquityLocation, WV· 1 mo ago
Marketing$500k/yrapply on careers.spectrumequity.com

Senior Product Owner

Blue Cross NCRaleigh-Durham-Chapel Hill Area· 1 mo ago
$108k–$173k/yrapply on bcbsnc.wd5.myworkdayjobs.com

Senior Product Owner

ICW GroupSan Diego, CA· 1 mo ago
Marketing$106k–$189k/yrapply on rr.jobsyn.org