Supplier Warranty Cost Lead

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Rivian" (company description) and "Role Summary". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading. Include a section ONLY when posting has real, specific content for it. So we need to decide which sections to include. We have content: - About Rivian (company description) – could be "About the role"? Actually "About Rivian" is about company, not role. The instruction list includes "About the role" as example heading. But we could use "About Rivian" as heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are typical headings but we can use others? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Probably they expect those exact headings if applicable. However we have "About Rivian" which is not exactly "About the role". Could we treat that as "About the role"? The role summary is separate. The "About Rivian" is company overview; maybe we can include as a

without heading? The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but suggests using those for sections. Safer to map content to those headings: we have role summary (could be "About the role")? Actually "Role Summary" is present. Could map to "About the role". Then we have Responsibilities (present). Qualifications (present). Pay (present). Benefits (present). Skills? Not explicitly a separate list; qualifications include skills. Could combine. Schedule? Not present. So we will not include Schedule. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the Equal Opportunity, Candidate Data Privacy, How We Use AI, etc. Also remove application instructions lines like "You can apply for this role through careers.rivian.com..." etc. Also remove duplicated salary disclosure lines (there are two identical for Plymouth, MI and Normal, IL). We need to keep salary range info but not duplicate. The posting includes two salary disclosures for different locations. We need to preserve ALL substantive information; but if they are duplicated with only location changed, we might need to keep both? The instruction: "Do NOT repeat the job title as a heading ... and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." For duplicated lines, we should remove duplicated lines. So we should keep one salary disclosure but maybe note both locations? The substantive info includes salary range for Plymouth, MI based applicants and also for Normal, IL based applicants. They are same range but different location. Could combine: "The salary range for this role is $89,900 - $112,400 for Plymouth, MI and Normal, IL based applicants." That preserves info without duplication. That's acceptable. Also we need to keep benefits description. Keep pay disclosure. Keep qualifications. Keep responsibilities. Keep role summary. Keep about Rivian? Could be included as a short paragraph maybe under a heading "About Rivian"? But not in list. Could we include as a

without heading? The instruction says output ONLY the HTML fragment; we can include

for prose. So we can include a paragraph about Rivian without heading. That seems fine. We need to avoid headings with filler text. So we will include headings only for sections with real content: About the role (role summary), Responsibilities, Qualifications, Pay, Benefits. Possibly Skills? Not separate. We need to use

• for any list of duties/requirements/benefits. So responsibilities list should be
  . Qualifications list maybe bullet points. Benefits list maybe bullet points. We need to preserve all substantive information; not invent or summarize away detail. So we need to keep each bullet point as is, not condense too much. However we can combine similar bullet points? The instruction: "Prefer a few substantive sections over many thin ones." But we must not lose detail. We'll keep bullet points as separate
  • items. Let's extract responsibilities bullet points from the text: Responsibilities section: "Oversee all aspects of the fair resolution of financial responsibility associated with Supplier Warranty claims" "Execute the financial responsibility resolution portion of Rivian’s Supplier Warranty Partnership Program, including all direct financial recoveries, facilitation of supplier negotiations, data gathering, and technical validation for establishment of normal ratios during serial production" "Be the subject matter expert and resource for the global supply base regarding Supplier Warranty financial resolution while leading supplier training webinars and facilitating transaction closure though efficient dispute resolution" "Work closely with supplier warranty technical leads to coordinate the issuance of Warranty Supplier CorrectiveAction Requests (WARSCAR) and tracking of supplier 8D reports, ensuring root causes are technically documented and resolved" "Act as a dynamic bridge between technical analysis and financial recovery, ensuring cost recovery is fair and goals are met while building strong, collaborative networks across Rivian and our supplier base" "Serve as the primary point of contact for the IT team for all Supplier Warranty financials, resolve SAP errors through collaborative problem solving, and build out invoicing solutions through the Rivian Basecamp supplier portal" "Lead technical warranty discussions with DREs, SDEs, and Manufacturing to ensure consistent evidence-based messaging to the supply base" We need to keep them exactly as written (maybe fix minor typos like "though" should be "through"? but we must not invent or summarize away detail; we can keep as is). We'll keep them. Qualifications bullet points: "Bachelor’s in Business, Finance, Engineering, Supply Chain, or a related technical field" "5+ years of experience in warranty recovery, quality, supplier management (development, purchasing), or customer account management within an automotive or complex manufacturing environment" "Basic understanding of automotive systems and how components fail/interact within a vehicle" "Familiarity with structured problem-solving (8D, 5-Why) and a 'work smarter' mindset focused on automation" "Knowledge of automotive warranty standards (AIAG CQI-14, VDA Field Failure Analysis)" "Ability to navigate complex technical discussions with suppliers while maintaining strong relationships" "Familiarity with Google Workspace, Jira, SAP, Hex, Databricks, AI tools" "Willingness to work in a strong cross-functional environment" "Comfortable working in a manufacturing / production environment" "Travel 10%" We need to keep Travel 10% as a bullet? It's a qualification. Benefits description: "We offer a comprehensive package of benefits for full-time and part-time employees, their spouse or domestic partner, and children up to age 26, including but not limited to paid vacation, paid sick leave, and a competitive portfolio of insurance benefits including life, medical, dental, vision, short-term disability insurance, and long-term disability insurance to eligible employees. You may also have the opportunity to participate in Rivian’s 401(k) Plan and Employee Stock Purchase Program if you meet certain eligibility requirements. Full-time employee coverage is effective on their first day of employment. Part-time employee coverage is effective the first of the month following 90 days of employment. More information about benefits is available at rivianbenefits." We can turn that into a
    list? It's prose; we could keep as

    . But instruction: Use

    • for any list of duties/requirements/benefits. Benefits is a list; we could bullet each benefit: paid vacation, paid sick leave, life insurance, medical, dental, vision, short-term disability, long-term disability, 401(k) Plan, Employee Stock Purchase Program. Also mention coverage effective dates. Might be better to keep as

      to preserve detail. However instruction says use

      • for any list of duties/requirements/benefits. So we should convert benefits to list. But we must preserve ALL substantive information; converting to list may lose some nuance like "including but not limited to". But we can still include the phrase as a

        preceding list? The instruction says use

        • for any list of duties/requirements/benefits. It doesn't forbid also having a

          before. So we can have a

          summarizing then

          for specific benefits. Pay section: we need to include salary range and note about location and bonus/equity. We'll put as

          . Schedule: not present, omit. Now about the role summary: we have "Role Summary" paragraph. We'll put under heading

          About the role

          and then

          with the role summary text. About Rivian: we can include as a

          before any heading or after? Probably at top as introductory paragraph. No heading needed. Now we need to remove boilerplate: Equal Opportunity, Candidate Data Privacy, How We Use AI, application instructions, etc. Also remove duplicated salary lines. Let's craft HTML. Structure:

          About Rivian paragraph...

          About the role

          Role Summary text...

          Responsibilities

          • ...
          ...

          Qualifications

          • ...
          ...

          Pay

          Salary range text...

          Benefits

          Benefits intro...

          • Paid vacation
          • Paid sick leave
          • Life insurance
          • Medical insurance
          • Dental insurance
          • Vision insurance
          • Short-term disability insurance
          • Long-term disability insurance
          • 401(k) Plan
          • Employee Stock Purchase Program

          Full-time employee coverage is effective on their first day of employment. Part-time employee coverage is effective the first of the month following 90 days of employment. More information about benefits is available at rivianbenefits.com.

          We need to ensure we didn't miss any substantive info: The role summary includes: "The Supplier Warranty Cost Lead directs the fair and timely recoupment of warranty costs by leading commercial negotiations and resolving disputes across a global vendor base. Serving as a vital link between engineering failure data and financial operations, this role ensures fair cost-recovery targets are achieved while preserving collaborative, productive vendor relationships. In partnership with internal technical, manufacturing, and IT teams, you will oversee root-cause corrective action tracking and refine enterprise invoicing systems. Ideal candidates bring over five years of automotive or manufacturing warranty and supplier management experience, paired with strong cross-functional communication skills and a deep understanding of industry quality standards". That's the role summary paragraph. We need to keep that exactly. Now check responsibilities bullet points for any missing nuance: The first bullet: "Oversee all aspects of the fair resolution of financial responsibility associated with Supplier Warranty claims". Good. Second: "Execute the financial responsibility resolution portion of Rivian’s Supplier Warranty Partnership Program, including all direct financial recoveries, facilitation of supplier negotiations, data gathering, and technical validation for establishment of normal ratios during serial production". Good. Third: "Be the subject matter expert and resource for the global supply base regarding Supplier Warranty financial resolution while leading supplier training webinars and facilitating transaction closure though efficient dispute resolution". Note "though" maybe typo but we keep. Fourth: "Work closely with supplier warranty technical leads to coordinate the issuance of Warranty Supplier CorrectiveAction Requests