Adventure Readiness Specialist

We need to output HTML fragment with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: - About Rivian (company description) but not "About the role". There's a Role Summary paragraph. Could treat that as "About the role"? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create headings matching content: maybe "About the role" for Role Summary. There's also "About Rivian" but that's company overview; could be omitted or maybe part of About the role? The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short

for company overview? Might be considered substantive. The instruction: "Prefer a few substantive sections over many thin ones." We can include sections: About the role (Role Summary), Responsibilities, Qualifications (maybe combine Requirements and Qualifications?), Benefits, Pay. Also maybe Skills? The posting includes qualifications list includes many items; could treat as Qualifications. There's no explicit Skills separate. Could combine. We must not create sections with filler like "commensurate with experience". Pay is present: hourly range $18.17 to $20.80 for Missouri based applicants. Also mention annual performance bonus. So Pay section. Benefits: described: comprehensive package of benefits for full-time and part-time employees... includes paid vacation, sick leave, insurance, 401(k), ESPP, etc. So Benefits section. Schedule: The posting mentions "Ability to work a flexible 40-hour week, which may include varied shifts, weekends, and holidays." That's schedule info. So we can include Schedule section. Requirements: The qualifications list includes many items; could be Requirements. But we already have Qualifications. Might combine Requirements and Qualifications into one section? The instruction says use headings for those categories if content exists. We have both Requirements and Qualifications content. Could split: Requirements (e.g., age, driver's license, ability to work flexible schedule, physical exertion, etc.) and Qualifications (education, technical experience, desire to learn, etc.). But there is overlap. Let's parse: Qualifications section in posting: "Qualifications High School Diploma, GED, or other recognized high school equivalency credential preferred.Previous technical experience (e.g. automotive repair, mechanical maintenance, or electrical work) or experience in an adjacent technical industry (e.g. aviation, HVAC, or manufacturing) is highly preferred.A strong desire to learn, a high degree of adaptability, and a passion for working with your hands.Excellent communication and teamwork skills.Must be at least 21 years old and possess a valid driver’s license with no driving-related suspensions or revocation of Driver’s License (within a 3-5 year period).Ability to work a flexible 40-hour week, which may include varied shifts, weekends, and holidays. Physical exertion may be required to perform occupational tasks (sitting, standing, walking, bending, kneeling, carrying, reaching, pushing, pulling, and lifting up to 50 lbs.Frequent use of hands for purposes of grasping and using tools correctly, entering data, writing communications, or calling customers or internal partners.Ability to see, read, and interpret documents such as governmental regulations, safety rules, operating and maintenance instructions or schematics.This role may require regular interaction with customers and their families, 3rd party affiliates, and suppliers within Rivian facilities, on mobile service routes, or at community outreach events." That's a big block that includes both qualifications and requirements. Could treat as "Qualifications" section. Then we might not need separate Requirements. The instruction says include a section ONLY when the posting has real, specific content for it. So we can have Qualifications with that block. For Requirements maybe we don't have separate distinct list; we could omit Requirements section. Skills: Not explicitly listed separate; could be part of Qualifications. So we may omit Skills. Thus sections: About the role (Role Summary), Responsibilities, Qualifications, Benefits, Pay, Schedule. Check each for substantive content: - About the role: Role Summary paragraph: "As an Adventure Readiness Specialist, you are a critical part of the Rivian Service team during our peak seasonal periods, helping us provide seamless care that keeps owners focused on their adventure and their Rivians ready for the journey ahead. During our seasonal surges in delivery and service demand, you’ll be on the front lines, helping our team navigate the high-volume peaks and ensure every owner’s journey continues uninterrupted. This role is also an exciting entry point, offering a hands-on, development experience that is specifically focused on preparing you for a future as a Service Technician." That's substantive. - Responsibilities: bullet list under three key areas: Vehicle & Site Operations, Service Production Support, Training & Career Development. We need to preserve all substantive information. Use

• for any list of duties/requirements/benefits. So we need to output a list. Could flatten or keep subheadings? The instruction: use

  for section headings,

  • for any list of duties/requirements/benefits, and

    for prose. So within Responsibilities section, we can have a

    with items. Should we include subheadings like Vehicle & Site Operations as
    • ? Probably just list each duty as
    • . Could also include nested lists? Simpler: each duty as
    • . We'll need to capture all duties listed. Let's extract duties: Vehicle & Site Operations: - Receive, inspect, and process incoming vehicle inventory. - Maintain the quality and delivery readiness of our vehicles through washing, detailing, and charging. - Manage vehicle logistics, including lot organization, shuttling vehicles, and secure key management. - Maintain a clean, safe, and highly organized service center environment, adhering to 5S principles. Service Production Support: - Assist technicians with basic vehicle repairs, focusing on Pre-Delivery Inspection (PDI) tasks and Express Lane work. - Learn to safely use basic hand tools and power tools under direct supervision. - Support the workshop by maintaining tool and equipment readiness. Training & Career Development: - Participate in our TRAIL program—a guided path through hands-on learning, technical training, and professional growth. - Receive mentorship and on-the-job training for the Service Technician role. - Complete Rivian Learning Network (RLN) modules. - Explore a dedicated pathway into a long-term career as a Service Technician. - Maintain a flexible, “all-hands-on-deck” mindset by providing cross-functional support to other areas of the business as needed, ensuring overall site success while prioritizing primary technical training objectives. That's all. - Qualifications: The block includes many items. We'll output as
      • each item. Need to split by sentences? The block is a run-on. We'll parse into logical items: - High School Diploma, GED, or other recognized high school equivalency credential preferred. - Previous technical experience (e.g. automotive repair, mechanical maintenance, or electrical work) or experience in an adjacent technical industry (e.g. aviation, HVAC, or manufacturing) is highly preferred. - A strong desire to learn, a high degree of adaptability, and a passion for working with your hands. - Excellent communication and teamwork skills. - Must be at least 21 years old and possess a valid driver’s license with no driving-related suspensions or revocation of Driver’s License (within a 3-5 year period). - Ability to work a flexible 40-hour week, which may include varied shifts, weekends, and holidays. - Physical exertion may be required to perform occupational tasks (sitting, standing, walking, bending, kneeling, carrying, reaching, pushing, pulling, and lifting up to 50 lbs. - Frequent use of hands for purposes of grasping and using tools correctly, entering data, writing communications, or calling customers or internal partners. - Ability to see, read, and interpret documents such as governmental regulations, safety rules, operating and maintenance instructions or schematics. - This role may require regular interaction with customers and their families, 3rd party affiliates, and suppliers within Rivian facilities, on mobile service routes, or at community outreach events. We could also include "Ability to work a flexible 40-hour week..." which overlaps with schedule but okay. - Benefits: The block: "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.com." We'll output as
        • items. - Pay: "The hourly range for this role is $18.17 to $20.80 for Missouri based applicants. This is the lowest to highest hourly rate we in good faith believe we would pay for this role at the time of this posting. An employee’s position within the hourly range will be based on several factors including, but not limited to, specific competencies, relevant education, qualifications, certifications, experience, skills, geographic location, shift, and organizational needs. The successful candidate may be eligible for annual performance bonus." We'll output as

          maybe with

          for bullet? It's prose; we can use

          . - Schedule: The posting includes "Ability to work a flexible 40-hour week, which may include varied shifts, weekends, and holidays." That's schedule info. Could also mention shift variability. We'll output as

          . Now ensure we don't include boilerplate: Remove EEO, legal, privacy, AI, etc. Also remove application instructions lines: "You can apply for this role through careers.rivian.com (or through internal-careers-rivian.icims.com if you are a current employee). This job is not expected to be closed any sooner than 09/21/26." Remove. Also remove "About Rivian" company description? It's not a heading but could be considered part of About the role? The instruction says do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

          or drop it. The About Rivian paragraph is company overview; could be considered minor metadata? Might be okay to keep as a short

          under About the role? But we already have About the role section with Role Summary. Could we include both? The About Rivian is not about the role; it's about company. Could be considered filler? The instruction says prefer a few substantive sections over many thin ones. The company description is substantive but not about the role. However the instruction's example headings include "About the role". Not "About the company". So maybe we should omit the company description to keep focus on role. It's not required to preserve all substantive information? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." That suggests we should keep all substantive info, including company description. But we need to fit into headings. We could include a short

          under About the role that includes company description? Or we could add a separate section like "About Rivian" but not in allowed headings. The instruction says use

          for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't