Senior Staff Technical Product Manager-Service Intelligence

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate. We need to parse the posting. First part: intro about Scout Motors, heritage, etc. That's likely "About the role" or maybe "Overview". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide appropriate headings. We have sections: Overview (intro), What you’ll do (list of duties), Location & Travel Expectations, What you’ll bring (requirements/qualifications/skills), What you'll gain (benefits), Pay Transparency (pay info). Also maybe "Education" etc. We need to preserve all substantive info, not invent. We must not include sections with placeholder like "commensurate with experience". Pay Transparency includes base salary and bonus but not specific numbers; still it's substantive: says eligible to receive base salary and annual performance bonus program. That's enough for Pay section? It says "Final salary offered will be determined based on factors...". That's still substantive. So we can include Pay section. Schedule: location & travel expectations includes expectation of 1-3 days per week in office, remote possible. That's schedule info. So we can include Schedule section. Benefits: they list benefits: competitive insurance, 401k, PTO, parental leave, etc. So Benefits section. Qualifications: Education, AI-related certification required, etc. Also maybe "What you'll bring" includes experience, technical expertise, skills. Could split into Requirements (experience) and Qualifications (education) and Skills. But we can combine. We need to avoid duplication. Let's extract content. First, "Overview Join an iconic brand..." That's description of role. Could be About the role. We'll create

About the role

then

with that paragraph. Then Responsibilities: "What you’ll do" includes bullet points (Define and Lead Strategy, Complex Decisioning & Problem Solving, Lead Product Development, AI & Intelligence Enablement, Stakeholder Leadership, Operationalize a Pre-Launch Platform, Drive Technical Excellence, Live Decision Intelligence). Each has sub-bullets. We'll need to output

• for each duty. Could nest? Probably just top-level items. We'll need to preserve all details inside each bullet. Might be long but okay. We'll need to convert each bullet's subpoints into maybe separate
  inside? The instruction: Use
  • for any list of duties/requirements/benefits. It doesn't forbid nested lists. We'll keep simple: each main duty as
  • with its description as text (maybe includes semicolons). Could also break into multiple
  • for subpoints but that may lose grouping. Probably fine to keep as one
  • with sentences. Next, Location & Travel Expectations -> Schedule section. We'll have

    Schedule

    with that paragraph. Next, What you’ll bring -> could be Requirements and Qualifications and Skills. We'll split: Requirements (experience), Qualifications (education/certification), Skills (skills list). But we need to ensure we don't create empty sections. Let's extract: What you’ll bring paragraph: integrity, curiosity, resourcefulness, positive attitude, growth mindset, comfortable with change, flexible, collaborative approach. Then "Here's what else you'll bring:" then list: - 12+ years of product management experience with deep focus on technical platforms, complex systems, or decisioning engines. - Experience working with AI/ML technologies in a product, engineering, or business context - Proven experience leading 0‑to‑1 products in pre‑launch, startup, or transformation environments. - Track record of building logic‑heavy or intelligence‑driven systems that coordinate multiple inputs and constraints. - Technical Expertise - Strong understanding of distributed systems, APIs, data architectures, and real‑time processing. - Hands‑on experience working with AI/ML systems, rules engines, optimization problems, or decision frameworks. - Ability to reason deeply about tradeoffs between accuracy, speed, explainability, and scalability. - Comfort working closely with engineers and data scientists on system design. - Experience owning backend or platform products where value is delivered through system behavior and decision quality rather than user interfaces. - Skills - Demonstrated ability to define strategy in highly ambiguous environments. - Strong ability to influence senior leadership and align diverse stakeholders. - Exceptional analytical and structured problem‑solving capabilities. - Ability to define complex logic and decision flows with precision. - Strong written and verbal communication skills; able to simplify complexity without oversharing sensitive information. - Data‑driven mindset; comfortable working with metrics, experimentation, and system telemetry. - High tolerance for ambiguity; energized by building something new where the path is not fully defined. - Education - Bachelor’s degree in Computer Science, Engineering, Mathematics, or a related field. - Advanced technical degree or MBA preferred. - AI-related certification required. We could make sections: Requirements (experience), Qualifications (education + certification), Skills (skills list). Also maybe "Attributes" for integrity etc. Could include under Requirements or a separate "Qualities". But we can include them under Requirements as bullet. We'll create:

    Requirements

    • ... (list of experience items)

    Qualifications

    • ... (education items)

    Skills

    • ... (skills items)
    We also need to include the earlier paragraph about integrity etc. Could be part of Requirements as a bullet or separate

    . Probably include as a

    before the list. Now Benefits: we have bullet list: Competitive insurance including: Medical, dental, vision and income protection plans; 401(k) program with: An employer match and immediate vesting; Generous Paid Time Off including: 20 days planned PTO, as accrued; 40 hours of unplanned PTO and 14 company or floating holidays, annually; Up to 16 weeks of paid parental leave for biological and adoptive parents of all genders; Paid leave for circumstances related to bereavement, jury duty, voting time, or military leave. We'll output as

    • each. Pay Transparency: paragraph: "This is a full-time, exempt position eligible to receive a base salary and to participate in an annual performance bonus program. Final salary offered will be determined based on factors including but not limited to the candidate's skills and experience. The annual performance bonus program is preset and not cand" (cut off). We'll keep what we have. We'll output

      Pay

      ...

      Now ensure we don't include any boilerplate like cookie/navigation/legal/EEO etc. The text didn't have those. Now produce HTML fragment. We need to be careful to not include markdown fences. Let's craft. First, About the role: combine the overview paragraphs: "Join an iconic brand that is redefining the pickup truck and rugged SUV marketplace. As Senior Staff Technical Product Manager – Service Intelligence for a confidential digital initiative, you will lead the strategy and execution of a foundational backend intelligence platform that powers critical decision‑making across Scout’s direct‑to‑consumer retail and service ecosystem. This role focuses on designing a backend‑driven decisioning and orchestration system that evaluates complex, interdependent operational inputs to produce reliable, scalable outcomes in real time. The platform is being built ahead of Start of Operations and will play a central role in how Scout coordinates resources, responds to events, and enables consistent execution across locations. This role operates at a cross-domain level, shaping how multiple systems, products, and operational workflows interact through centralized decision intelligence. Initially, there is no end‑user interface or traditional UX design responsibility associated with this position; success is defined by system behavior, decision quality, and operational outcomes. This is a deeply technical, AI‑driven and analytical role requiring strong systems thinking and comfort operating in a highly ambiguous, 0‑to‑1 environment. The successful candidate will help shape core capabilities from the ground up, owning both initial delivery and long‑term evolution of a mission‑critical intelligence platform while maintaining strict discretion around sensitive product details." We'll put that in

      . Now Responsibilities: we need to capture each main duty with its subpoints. Let's list them: 1. Define and Lead Strategy - Define, evolve, and drive the product and ecosystem strategy for a confidential, intelligence‑driven core platform supporting Scout’s operations and service experience. - Define how complex operational signals, constraints, and policies are modeled into automated decision logic. - Lead early-stage platform definition ahead of Start of Operations, building foundational capabilities with no existing baseline. - Accountable for system performance across Scout’s direct‑to‑consumer retail network, ensuring decisions are reliable, explainable, and scalable. - Influence senior leadership and align platform strategy with long-term company objectives while protecting sensitive capabilities. - Identify new problem spaces and expansion opportunities for decision intelligence across additional domains and systems. 2. Complex Decisioning & Problem Solving - Frame and solve highly ambiguous, cross-functional problems through intelligent system design and decision frameworks. - Model operational constraints, dependencies, and priorities as structured logic, rules, or machine‑assisted decision frameworks. - Drive solutions where “missing inputs” require downstream actions to resolve constraints rather than blocking outcomes. - Navigate ambiguity inherent to 0‑to‑1 product development, making informed tradeoffs as requirements and dependencies evolve. - Evaluate tradeoffs involving accuracy, speed, scalability, and explainability, including intangible system behaviors. - Ensure system behavior is consistent, explainable, auditable, and adaptable as business rules change. 3. Lead Product Development - Guide product development across multiple related initiatives, teams, and domains to ensure alignment with strategic objectives. - Lead end‑to‑end product development for a highly complex, logic‑heavy platform from concept through scale. - Collaborate closely with Engineering, Data Analytics, AI/ML teams, IT, and Operations to: * Translate operational needs into system logic and technical requirements. * Define data models, decision flows, signal ingestion, and output generation. * Balance deterministic rules with AI‑assisted approaches where appropriate. * Ensure platform extensibility as new use cases and domains are added over time. - Establish best practices and frameworks for decisioning platforms adopted across related systems and teams. 4. AI & Intelligence Enablement - Champion the use of AI, machine reasoning, and advanced analytics to enable scalable decision‑making. - Define where AI augments human decision processes versus fully automated execution. - Ensure models and logic are transparent, testable, and continuously improvable. - Collaborate with data partners to ensure high‑quality inputs, feedback loops, and monitoring. 5. Stakeholder Leadership - Influence and align senior leadership, engineering, and cross-functional stakeholders on strategy, priorities, and tradeoffs. - Serve as a trusted partner to Business, Software Engineering, fellow Digital Product Customer Experience team, and Leadership teams. - Translate complex, cross‑functional needs into a shared technical and product vision without exposing sensitive strategy externally. - Lead alignment across teams with differing priorities, timelines, and constraints. - Build long‑term trust in the platform through transparency, reliability, and outcomes. 6. Operationalize a Pre‑Launch Platform - Build readiness for a mission‑critical platform before Start of Operations. - Define rollout strategies, guardrails, fallback behaviors, and manual override paths. - Ensure the platform supports consistent execution independent of location or context. - Define scalable operating models for how decision intelligence is embedded across systems and workflows. 7. Drive Technical Excellence -