Technical Trainer

We need to output HTML fragment with sections: About the role? Actually we have sections: About Moove (company description) maybe not needed as heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should include only sections that have real content. The posting includes: About Moove (company description), Job Overview, Key Responsibilities, Required Qualifications, Location and Travel, About The Team, Benefits, plus some statements (Drug-Free Workplace, Safety-Sensitive Addendum, Driving Requirements, Disclaimer) which are boilerplate and should be removed. Also we should not repeat job title as heading. We should not include Job ID etc. We need to preserve all substantive information. So we need to include sections: About Moove? Possibly "About the role" could be Job Overview. But we can also have "About Moove" as a section? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings, but says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect those standard headings. We can map content: About the role -> Job Overview. Responsibilities -> Key Responsibilities. Requirements -> maybe combine Required Qualifications? Actually Requirements and Qualifications are separate headings. We have Required Qualifications (which includes experience, background, etc). Could also have Skills (maybe from Required Qualifications). But we can put Required Qualifications under Qualifications heading. Requirements could be maybe location and travel? But location is not a requirement per se. Might be better to have sections: About the role (Job Overview), Responsibilities (Key Responsibilities), Qualifications (Required Qualifications), Benefits (Benefits). Also maybe About The Team could be omitted? It's not in the list but could be included as a section? The instruction says prefer a few substantive sections over many thin ones. About The Team is substantive but not a standard heading; we could include as a section with

About The Team

. However they gave examples but not exclusive. It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should use those headings when applicable, but we can also use other headings if needed? Safer to stick to those headings. So we need to map content to those headings. We have: - About the role: Job Overview paragraph. - Responsibilities: Key Responsibilities (list). - Requirements: maybe Location and Travel? But location is not a requirement; it's a location constraint. Could be considered a requirement (must be authorized to work and reside in Phoenix, AZ, Miami or other select locations; travel up to 30%). That fits Requirements. - Qualifications: Required Qualifications (experience, background, etc). Could also include Education. - Skills: maybe we could extract from Required Qualifications: technical background, systems proficiency, high voltage experience, training ability. But we already have Qualifications; Skills could be separate but we might combine. To avoid thin sections, maybe we skip Skills and put those details under Qualifications. - Benefits: Benefits section. - Pay: not present, so omit. - Schedule: not present, omit. Thus we will output:

About the role

Moove seeks a Technical Trainer to deliver technician training, certification, and safety instruction across the fleet maintenance organization. This role reports to the Senior Technical Trainer and executes the technical development curriculum for multiple technician levels, ensuring consistent, audit-ready delivery in assigned markets. This position delivers hands-on training that bridges conventional automotive repair with advanced electric and autonomous vehicle systems. The objective is sustained vehicle readiness through standardized diagnostics, repair execution, and safety compliance.

Responsibilities

• Deliver the technician progression framework from entry level through senior specialist roles under Senior Technical Trainer direction
• Build and maintain modular training content tied to skills validation, certification, and operational readiness
• Deliver safety training to standard and provide field input to safety policy updates; ensure technicians are trained and compliant with Moove safety policies and procedures
• Support deployment and deliver training for the standardized SOP and repair execution platform; drive technician adoption of digital workflows and surface performance data that indicates retraining needs
• Deliver hands-on instruction for removal, replacement, validation, and calibration of integrated vehicle sensing and compute systems; apply standardized repair and verification procedures for complex vehicle subsystems and escalate gaps
• Deliver high-voltage safety training aligned to industry standards and Moove policy; train technicians on battery systems, isolation faults, and electrical safety response protocols
• Audit repair quality, escalation accuracy, and documentation across maintenance software; ensure standardized diagnostic logic is followed before engineering escalation
• Cross-functional training support cross-training with operations leadership to improve repair planning and execution alignment
• Coach technicians on shop floor fundamentals, quality ownership, and peer mentoring; support onboarding and ramp of new technicians without reducing bay throughput
• Certify technicians on depot equipment including vehicle lifts and non-powered vehicle movement tools

Requirements

Must be authorized to work and reside in Phoenix, AZ, Miami or other select locations. Travel up to 30 percent.

Qualifications

• Four or more years of experience in advanced automotive, electric vehicle, robotics, or complex electromechanical maintenance
• Minimum six months supporting autonomous or advanced vehicle platforms
• Strong technical background: working knowledge of advanced vehicle architectures including sensing, compute, power, and control systems; comfort working with Linux based environments for diagnostics and log review; hands-on expertise with electrical diagnostics tools including analyzers, oscilloscopes, and multimeters
• Systems and tool proficiency: working experience with digital platforms, inventory systems, and maintenance management systems
• High voltage experience: documented experience working with high-voltage systems and electrical safety standards
• Training and instruction: ability to translate engineering documentation and SOPs into effective hands-on technician training
• Education: associate degree in a technical discipline, ASE or OEM technician certification, or equivalent hands-on experience

Benefits

• Employer-paid premiums for individual health, dental, and vision insurance
• 401k with employer match
• Opportunity for rapid advancement in a growing global organization
• Paid Time Off

We should not include any boilerplate like Drug-Free Workplace etc. Also we should not include About Moove paragraph at top? The instruction says do not repeat job title as heading; but we could include a brief intro about Moove? It's not under standard headings; maybe we could include as a

before sections? The instruction says output ONLY the HTML fragment; we can include a

describing Moove as part of About the role? But About the role is about the role, not company. However we could incorporate the Moove description into About the role section? The About Moove paragraph is generic company description; could be considered part of About the role? Might be okay to include as a

before the About the role heading? But they said use

for section headings (e.g. About the role, Responsibilities...). They didn't forbid other elements like

outside headings. However they said "Prefer a few substantive sections over many thin ones." Including a separate Moove description might be thin. Could incorporate into About the role: maybe start with "Moove AV enables safe, scalable autonomy..." then go into role overview. That would preserve all info. Let's do that: About the role section includes both company description and job overview. Thus About the role

About the role

Moove AV enables safe, scalable autonomy through disciplined fleet operations and technical excellence. The company partners across the autonomous mobility ecosystem to operate, maintain, and scale advanced vehicle fleets. Moove continues global expansion and seeks experienced technical leaders who value safety, rigor, and execution. Moove seeks a Technical Trainer to deliver technician training, certification, and safety instruction across the fleet maintenance organization. This role reports to the Senior Technical Trainer and executes the technical development curriculum for multiple technician levels, ensuring consistent, audit-ready delivery in assigned markets. This position delivers hands-on training that bridges conventional automotive repair with advanced electric and autonomous vehicle systems. The objective is sustained vehicle readiness through standardized diagnostics, repair execution, and safety compliance.

That covers company description and job overview. Now ensure we didn't miss any substantive info: Key Responsibilities captured all bullet points. Required Qualifications captured all. Location and Travel captured. Benefits captured. The About The Team section is omitted; but it's substantive about team values. Could we incorporate into About the role? Maybe add a sentence about team values? The About The Team paragraph: "The Moove team values accountability, curiosity, and operational discipline. Teams move quickly, communicate directly, and focus on results. Moove supports diverse backgrounds and perspectives and hires based on capability, performance, and integrity." That's substantive; we could add to About the role section after company description. Let's incorporate. Thus About the role paragraph will include: company description, team values, job overview. Let's craft:

Moove AV enables safe, scalable autonomy through disciplined fleet operations and technical excellence. The company partners across the autonomous mobility ecosystem to operate, maintain, and scale advanced vehicle fleets. Moove continues global expansion and seeks experienced technical leaders who value safety, rigor, and execution. The Moove team values accountability, curiosity, and operational discipline. Teams move quickly, communicate directly, and focus on results. Moove supports diverse backgrounds and perspectives and hires based on capability, performance, and integrity. Moove seeks a Technical Trainer to deliver technician training, certification, and safety instruction across the fleet maintenance organization. This role reports to the Senior Technical Trainer and executes the technical development curriculum for multiple technician levels, ensuring consistent, audit-ready delivery in assigned markets. This position delivers hands-on training that bridges conventional automotive repair with advanced electric and autonomous vehicle systems. The objective is sustained vehicle readiness through standardized diagnostics, repair execution, and safety compliance.

That seems good. Now ensure we didn't include any boilerplate: Drug-Free Workplace, Safety-Sensitive Addendum, Driving Requirements, Disclaimer removed. Now output only HTML fragment. Check for any missing info: The "Key Responsibilities" includes "Deliver the technician progression framework from entry level through senior specialist roles under Senior Technical Trainer directionBuild and maintain modular training content tied to skills validation, certification, and operational readiness" Actually there is a missing space between directionBuild. In original text: "Deliver the technician progression framework from entry level through senior specialist roles under Senior Technical Trainer directionBuild and maintain modular training content tied to skills validation, certification, and operational readiness". It seems missing a period. We need to preserve as is but we can add a space? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. We should not add or remove words. The original had a missing space; we should keep it exactly? It's ambiguous. Probably we should keep the text as given but we can add a space for readability? That would be altering. Better to keep exactly as given but we can insert a space? The instruction says do not invent or summarize away detail. Adding a space is not inventing detail, it's just formatting; but it's changing the string. Safer to keep exactly as given, but we can keep the missing space as is. However it looks odd. I'd keep as given but maybe add a space after direction? I think it's okay to add a space because it's not changing meaning. But to be safe, I'll keep exactly as in source: "directionBuild". I'll keep that. Similarly other