Fleet Operations Training Lead - US & Japan

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real content. We must not repeat job title. Must preserve all substantive info, remove boilerplate (About Us, etc). We need to extract relevant content: The posting includes "About Us" (should be removed), "The role" (should be used as About the role? Actually "About the role" heading: we can put description of role). Then "Key Responsibilities" -> Responsibilities section. Then "About You" includes Essential and Desirable; we need to split into Requirements, Qualifications, Skills perhaps. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Skills). We need to decide which sections have content. We have: - About the role: description of role (the paragraph after "The role"). - Responsibilities: list of key responsibilities (bulleted). Should be

• . - Requirements: essential qualifications? Could be "Essential" list. - Qualifications: maybe "Desirable" list? Or we could treat Essential as Requirements, Desirable as Qualifications. Skills: maybe combine some skills from essential/desirable? But we have to avoid duplication. Could put Skills as separate list of skills like facilitation, communication, analytical, stakeholder-management, time-management, etc. However essential list already includes many skills. Might be better to follow instruction: Use sections only when posting has real specific content. We have content for About the role, Responsibilities, Essential (requirements), Desirable (qualifications/skills), Pay (salary range). Benefits? Not mentioned besides "competitive equity package". That's a benefit. So we can include Benefits section with equity package. Schedule? Not mentioned besides "Availability to work on-site five days a week." That's schedule info. So we can include Schedule section. Thus sections: About the role, Responsibilities, Requirements (Essential), Qualifications (Desirable), Skills (maybe we can extract specific skills from essential/desirable? But we could also omit Skills if we think it's redundant. However instruction: prefer a few substantive sections over many thin ones. We could combine Requirements and Qualifications into one? But they ask to use those headings if content exists. We have both essential and desirable; we can treat essential as Requirements, desirable as Qualifications. Skills maybe we can omit if no distinct skill list beyond those. But we could extract skills like "facilitation and communication skills", "analytical skills", "stakeholder-management skills", "time-management and prioritisation skills". Those are already in essential list. Could still make a Skills section but would duplicate. Better to omit Skills section to avoid thin/duplicate. Benefits: equity package mentioned. Also maybe "competitive equity package". So Benefits section. Pay: salary range $100,000 to $130,000. Schedule: "Availability to work on-site five days a week." Now we need to strip boilerplate: About Us, The reasonably estimated salary... we keep pay. Also remove EEO, accommodation statement, diversity statement, E-Verify notice, etc. Also remove "The role" heading? We'll use About the role heading. We need to preserve all substantive information: ensure we keep all responsibilities bullet points, essential and desirable bullet points, etc. Let's extract the responsibilities list exactly as in text: Key Responsibilities Training strategy: Develop and maintain a comprehensive training strategy and roadmap for Fleet Operations in the US and Japan, aligned with organisational priorities, operational requirements, and future geographical expansion. Learning programme development: Design, implement, and regularly update onboarding, technical, safety, compliance, and professional-development programs for Fleet Operations teams. Training needs analysis: Partner with Fleet Operations leaders and subject-matter experts to assess skills, identify capability gaps, and prioritise training requirements. Training delivery: Deliver engaging instructor-led, virtual, practical, and blended learning experiences for employees with different levels of experience and technical knowledge. Learning standards and localisation: Establish consistent training and competency standards while adapting content and delivery to local languages, cultures, regulations, and operational environments. Competency and certification: Create structured learning paths, practical assessments, competency frameworks, and certification programs that ensure employees are prepared to perform their roles safely and effectively. Training effectiveness: Define and monitor measures such as participation, knowledge retention, practical proficiency, time to competency, learner feedback, and operational performance. Continuous improvement: Use performance data, employee feedback, incident trends, and operational insights to continually improve training content, methods, and outcomes. Train-the-trainer: Develop and manage train-the-trainer programs, supporting local trainers and Fleet Operations leaders to deliver learning consistently and effectively. Learning systems and records: Use learning technologies to make training accessible, scalable, and engaging, while maintaining accurate records of training, competency, and certification. Cross-functional collaboration: Work closely with Fleet Operations, Safety, Engineering, People, and other stakeholders to ensure training reflects current technology, processes, risks, and business priorities. Operational change: Support the introduction of new technologies, vehicles, processes, policies, and programmes through structured training and change-readiness activities. Learning culture: Champion continuous learning, knowledge sharing, and professional development across Fleet Operations. Now Essential list: Essential A strong track record of developing and implementing comprehensive operational training programs, including training-needs analysis, instructional design, delivery, and evaluation. Demonstrated leadership experience within a high-velocity, safety-focused fleet, operational, or technical environment. Experience supporting training across multiple locations, regions, or culturally diverse teams. Excellent facilitation and communication skills, with the ability to make complex technical and operational information clear and accessible. Experience creating structured learning paths, practical assessments, competency frameworks, and certification programs. Strong analytical skills, with the ability to identify capability gaps and evaluate the effectiveness and operational impact of training. Strong stakeholder-management skills and the ability to collaborate with Fleet Operations, Safety, Engineering, People, and subject-matter experts. Excellent time-management and prioritisation skills, with a proven ability to respond effectively to changing requirements in a fast-paced environment. The ability to work effectively across US and Japan time zones and travel between operational locations when required. Availability to work on-site five days a week. A clean and compliant driving record in accordance with company requirements. A safety-conscious mindset, with the confidence to identify and escalate potential risks. Desirable list: Desirable Experience establishing or scaling training programs across multiple countries or geographical regions. Experience adapting training for different languages, cultures, regulatory requirements, and operational contexts. Familiarity with learning-management systems, digital learning tools, and virtual or blended learning approaches. Experience developing train-the-trainer programs or leading a distributed network of trainers. Familiarity with advanced driver-assistance systems, including sensors and onboard hardware and firmware. Experience in fleet operations, particularly data collection and closed-loop testing of ADAS functions. Experience working within the automotive, autonomous-vehicle, robotics, AI, mobility, or another safety-critical industry. Japanese-language capability or previous experience working closely with teams in Japan. Experience working in a fast-moving technology company or startup. Now About the role paragraph: The role As the Fleet Operations Training Lead for the US and Japan, you will lead the development, delivery, and continuous improvement of training across our Fleet Operations teams. You will ensure that team members have the knowledge, practical skills, and confidence required to operate safely, consistently, and effectively. Working closely with Fleet Operations, Safety, Engineering, People, and other teams across the business, you will identify capability gaps and translate complex operational and technical information into engaging, practical learning experiences. You will establish consistent training standards across both regions while adapting programs to reflect local operational, cultural, language, and regulatory requirements. We’re looking for someone who is organised, collaborative, and passionate about developing others: a pragmatic leader who is comfortable working in a fast-moving, safety-focused environment and can balance immediate training needs with a longer-term strategy. As our Fleet Operations function grows, you will develop scalable training programs and processes that can support additional geographies in the future. We'll put that under About the role. Benefits: "plus a competitive equity package." Also maybe other benefits not mentioned. So we can put that. Pay: "The reasonably estimated salary for this role ranges from $100,000 to $130,000, plus a competitive equity package." Actually equity package already in benefits; but we can still mention salary range. Schedule: "Availability to work on-site five days a week." Already in essential list; but we can also put schedule section. We must not duplicate content? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid duplication across sections, but better to avoid redundancy. However schedule info appears in essential list; we could keep it there and not repeat in schedule section. But schedule section expects schedule info; we could still include it but it's duplicate. Might be okay but better to avoid duplication. However we need to include schedule section only if posting has real specific content for it. It does: "Availability to work on-site five days a week." So we should include schedule section with that sentence. Even if it's also in essential list, it's okay to have it in both places? Might be considered duplication but not prohibited. However to keep sections thin, we could move that line from essential to schedule and remove from essential? But then we would lose that info from essential list (which is part of requirements). The essential list includes that line; we could keep it there and also have schedule section; duplication may be okay but maybe they'd consider it thin? Not sure. I'd keep it in essential list and also schedule section? Might be considered redundant but still preserves all info. I'd rather keep it in essential list and not duplicate in schedule; but then schedule section would be empty (we would not have content). So we need schedule section with content; we can take that line from essential and still keep it there? Could keep both; it's still preserving all info (just duplicated). I'd go with duplication to satisfy schedule section. Now Benefits: we have equity package. Also maybe other benefits not mentioned. We'll just put equity package. Now we need to output HTML fragment only, no /. Use

  for each section heading. Use

  • for lists. Use

    for prose. We'll structure:

    About the role

    ... paragraph ...

    Responsibilities

    • ...
    ...

    Requirements

    • ... essential items ...
    ...

    Qualifications

    • ... desirable items ...
    ...

    Benefits

    Competitive equity package.

    Pay

    The reasonably estimated salary for this role ranges from $100,000 to $130,000.

    Schedule

    Availability to work on-site five days a week.

    We need to ensure we don't include boilerplate like "About Us", "The role" heading (we used About the role). Also remove EEO etc. Check that we didn't miss any substantive info: The "About Us" paragraph removed. The "The reasonably estimated salary for this role ranges from $100,000 to $130,000, plus a competitive equity package." We split salary and equity. Good. The "We understand that everyone has a unique set of skills..." etc removed. The "At Wayve we're committed to creating a diverse..." removed. The "For more information visit Careers at Wayve..." removed. The "To learn more about what drives us, visit Values at Wayve" removed. The "For US candidates only, please visit E-Verify Notice..." removed. The "DISCLAIMER: We will not ask about marriage..." removed. All good. Now ensure we didn't miss any other substantive content like "Make Wayve the experience that defines your career!" That's part of About Us? Actually