Staff Product Manager, Engineering Workflow Platforms

We need to output HTML fragment with sections: About the role? Actually we need to use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. The posting includes sections: About Lucid (company description), Role description, Key Responsibilities, Qualifications, Preferred (maybe skills), Compensation & Benefits (benefits). No explicit Pay or Schedule details besides "requires employees to be onsite five days a week" (Schedule). So we can include Schedule section with that detail. Pay not mentioned, so we should NOT include Pay section. Benefits section: we have compensation & benefits details. Should include Benefits heading with that content. Also we may include About the role? The posting includes "Role" paragraph describing role. Could be About the role. We'll include About the role section with that paragraph. We need to preserve all substantive info, not repeat job title. No Job ID. Remove boilerplate like EEO, diversity statements, application instructions, etc. Also remove repeated lines like "At Lucid, we don’t just welcome diversity..." etc. Also remove "Compensation & Benefits:" heading? We'll keep benefits content. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to decide what to list as lists: Key Responsibilities are bullet points; we can make

  . Qualifications are bullet points; also list. Preferred maybe list as Skills? Could be Skills section. Benefits we can list as
  . Schedule we can list as

  maybe. We must not create sections with filler. So include sections: About the role, Responsibilities, Qualifications, Skills (Preferred), Benefits, Schedule. Check each for real content. About the role: we have paragraph after "Role". Let's extract: "We are seeking a Staff Product Manager to own a sub-set of the Platform. The current capabilities are segmented and we are looking for someone who can own the vision, development, and convergence of part of our stack. You will be expected to be the product voice in front of VP-level stakeholders when the right answer is that a cross-functional process has to change. The taxonomy underneath the platform spans both the physical product and the software. You will also set how this team does product management. That means the discovery standard, the definition-of-done bar, and the mentoring of the less Senior colleagues alongside you, and it means being the person the manager can hand a portfolio-level question to and not follow up on. We are looking for someone who has replaced entrenched ways of working before and knows that the software was the easy part. This role is based in Phoenix, AZ and requires employees to be onsite five days a week." We'll put that in

  . Responsibilities: list from "Key Responsibilities". We'll capture each bullet line. Qualifications: list from "Qualifications". We'll capture each bullet. Preferred: list from "Preferred". Could be Skills section. Benefits: from "Compensation & Benefits:" paragraph. We'll list each benefit as

  • . Schedule: from role paragraph about onsite five days a week. Could be separate sentence: "This role is based in Phoenix, AZ and requires employees to be onsite five days a week." We'll put that in Schedule section as

    . We must not repeat job title. No mention of "Staff Product Manager" as heading; it's okay in prose. We must not include duplicated lines. Ensure we don't include EEO etc. Now produce HTML. Structure:

    About the role

    ...

    Responsibilities

    • ...
    ...

    Qualifications

    ...

    Skills

    ...

    Benefits

    ...

    Schedule

    ...

    Check that we don't include Pay section. Now extract bullet points precisely. From Key Responsibilities: - Capability Ownership and Platform Strategy Own the strategy, roadmap, and outcomes for a major capability area, and shape the roadmap for the platform as a whole alongside the manager. - Sequence capability delivery against real vehicle program gates, and be able to state precisely which gates a given staffing or scope decision causes us to make or miss - Stand up a committed but unstarted capability from nothing: define the scope and the phasing. - Own the platform's product narrative in Monthly Business Reviews and executive forums, reporting on adoption, data quality, and gate readiness. - Adjudicate source-of-truth decisions across systems that regularly disagree, define the reconciliation rules, and make the call when two functions want the same field to mean two different things - Protect the integrity of the model against expedient one-off requests, and be able to explain the refusal in terms the requester accepts - Partner with the manager on the trade-offs between what belongs in the data model, in a pipeline, in the application, and in a process outside the system entirely - Cross-Functional and Executive Leadership Build and hold relationships with VP-level and director-level stakeholders across Program Management, Engineering, Supply Chain, Supplier Quality, Manufacturing, and the PMO - Drive decisions that require organizational change, not just software: process ownership, accountability boundaries, and the retirement of the spreadsheets and side systems the platform replaces - Broker priority conflicts between functions with legitimate competing needs, and get to a decision that holds - Represent the platform in program reviews and gate reviews so the roadmap stays tied to what programs actually need next - Discovery, Definition, and Decisions Run deep discovery on the highest-ambiguity problems on the roadmap, including the ones nobody has been able to specify yet - Write the specifications, decision records, and proposals that set direction, covering the problem, the options considered, the trade-offs, the blast radius on live production data, and the rollout and rollback plan - Set the bar for definition quality on the team, and review the work of other product managers against it - Delivery and Launch Own launches that carry real organizational risk: phased rollout, pilot selection, readiness criteria, executive sponsorship, and a credible fallback if adoption stalls - Partner with Training and Communications on the enablement and change management that determines whether a launch actually lands - Practice and Mentorship Set the standards for how product work is done here: discovery, written definition, acceptance, AI Tooling, adoption measurement, and stakeholder engagement - Mentor colleagues on the team and raise the ceiling of what they can own independently - Provide continuity cover on portfolio priorities, so the team is not dependent on any single person remaining We need to keep each bullet as a list item. Some have sub-bullets? The formatting includes headings within responsibilities. We could keep each bullet as a separate
  • containing the sentences. The headings like "Capability Ownership and Platform Strategy" are not separate list items but could be part of first bullet? Actually they are section headings inside responsibilities. We could treat them as
  • with bold? But we only have
  • . We could include them as part of the first bullet's text. Simpler: treat each line after a dash as a bullet, ignoring the headings. But we might lose the heading meaning. However instructions: preserve ALL substantive information; we can keep the heading as part of the bullet text. Eg: "
  • Capability Ownership and Platform Strategy Own the strategy, roadmap, and outcomes..." but we cannot use ? Not prohibited but we should stick to plain text? Probably okay to include HTML tags inside
  • . Safer to just include the heading as plain text within the
  • . We'll do: "
  • Capability Ownership and Platform Strategy: Own the strategy, roadmap, and outcomes for a major capability area, and shape the roadmap for the platform as a whole alongside the manager.
  " etc. We'll need to parse each bullet. Let's list them: 1. Capability Ownership and Platform Strategy Own the strategy, roadmap, and outcomes for a major capability area, and shape the roadmap for the platform as a whole alongside the manager. 2. Sequence capability delivery against real vehicle program gates, and be able to state precisely which gates a given staffing or scope decision causes us to make or miss 3. Stand up a committed but unstarted capability from nothing: define the scope and the phasing. 4. Own the platform's product narrative in Monthly Business Reviews and executive forums, reporting on adoption, data quality, and gate readiness. 5. Adjudicate source-of-truth decisions across systems that regularly disagree, define the reconciliation rules, and make the call when two functions want the same field to mean two different things 6. Protect the integrity of the model against expedient one-off requests, and be able to explain the refusal in terms the requester accepts 7. Partner with the manager on the trade-offs between what belongs in the data model, in a pipeline, in the application, and in a process outside the system entirely 8. Cross-Functional and Executive Leadership Build and hold relationships with VP-level and director-level stakeholders across Program Management, Engineering, Supply Chain, Supplier Quality, Manufacturing, and the PMO 9. Drive decisions that require organizational change, not just software: process ownership, accountability boundaries, and the retirement of the spreadsheets and side systems the platform replaces 10. Broker priority conflicts between functions with legitimate competing needs, and get to a decision that holds 11. Represent the platform in program reviews and gate reviews so the roadmap stays tied to what programs actually need next 12. Discovery, Definition, and Decisions Run deep discovery on the highest-ambiguity problems on the roadmap, including the ones nobody has been able to specify yet 13. Write the specifications, decision records, and proposals that set direction, covering the problem, the options considered, the trade-offs, the blast radius on live production data, and the rollout and rollback plan 14. Set the bar for definition quality on the team, and review the work of other product managers against it 15. Delivery and Launch Own launches that carry real organizational risk: phased rollout, pilot selection, readiness criteria, executive sponsorship, and a credible fallback if adoption stalls 16. Partner with Training and Communications on the enablement and change management that determines whether a launch actually lands 17. Practice and Mentorship Set the standards for how product work is done here: discovery, written definition, acceptance, AI Tooling, adoption measurement, and stakeholder engagement 18. Mentor colleagues on the team and raise the ceiling of what they can own independently 19. Provide continuity cover on portfolio priorities, so the team is not dependent on any single person remaining Now Qualifications bullet list: - Substantial product management experience, including senior or lead ownership of an enterprise, internal platform, or business systems product, with a track record you can walk through end to end - Demonstrated ownership of a system of record rather than a reporting layer, including responsibility for data correctness and for the downstream consequences of getting it wrong - Proven ability to drive organizational change: you have retired an entrenched process or legacy tool, moved the people who depended on it, and can describe what it took - Executive communication and influence at VP level, including making a recommendation that a senior stakeholder does not initially want to hear and getting to a decision - Strong systems and data thinking: sources of truth, reconciliation logic, data modeling and taxonomy design, integration latency, and failure behavior when systems disagree - Excellent written communication: strategy documents, decision records, and proposals that are read and acted on without you presenting them - Data literacy sufficient to work independently: Jira and JQL, working SQL or equivalent, and the instinct to interrogate a number before repeating it - Experience owning a roadmap with hard external deadlines and real dependency structure, and the judgment to phase scope so value arrives before the deadline rather than at it - Demonstrated mentorship or practice leadership, whether or not you have carried a formal management title - Effective use of GitHub Copilot or comparable AI assistants across research, analysis, prototyping,