Autonomous Vehicle Technician with Mechanic Experience *To support our autonomous vehicle partner - MID-DAY SHIFT - in Mesa, AZ *
AutoNation · Mesa, CO · 1 mo ago
Management$30.69–$53.71/hrFull-time
We need to output only HTML fragment, no html/body tags, no markdown fences. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Also remove duplicated lines. Also remove keywords list? Probably not needed as it's not substantive content. Also remove "KEYWORDS:" line. Also remove "Exciting Benefits And Perks Await You" maybe part of benefits but we already have benefits section. We need to preserve all substantive information.
Let's parse the posting.
First paragraph: "The Advanced Autonomous Vehicle (AV) Technician is responsible for performing complex diagnostics, repairs, calibrations, and system integrations on autonomous vehicles. This role requires advanced troubleshooting of sensors, compute systems, networks, and mechanical/electrical components to ensure safe and reliable fleet operation. The technician collaborates closely with engineering, operations, and field safety teams to resolve escalated issues, execute technical projects, and provide subject-matter expertise on AV platforms."
That's about the role. So we can have
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Also remove duplicated lines. Also remove keywords list? Probably not needed as it's not substantive content. Also remove "KEYWORDS:" line. Also remove "Exciting Benefits And Perks Await You" maybe part of benefits but we already have benefits section. We need to preserve all substantive information.
Let's parse the posting.
First paragraph: "The Advanced Autonomous Vehicle (AV) Technician is responsible for performing complex diagnostics, repairs, calibrations, and system integrations on autonomous vehicles. This role requires advanced troubleshooting of sensors, compute systems, networks, and mechanical/electrical components to ensure safe and reliable fleet operation. The technician collaborates closely with engineering, operations, and field safety teams to resolve escalated issues, execute technical projects, and provide subject-matter expertise on AV platforms."
That's about the role. So we can have About the role
with that paragraph.
Then "Benefits" section: after that we have "Benefits We want our employees to feel happy, healthy, and valued as they work to provide a top-notch experience for our customers. We offer our full-time Associates great, competitive benefits such as: Higher income potentialFull benefits package including Paid Time Off & 401K w/ Company matchLongevity bonusesGenerous employee referral bonus program for Technicians (employees can earn up to $3,000 per Tech referral!)Employee discount on vehicle purchases, parts, & serviceAdvancement opportunitiesAnd so much more!"
That's benefits. Then later there is "Exciting Benefits And Perks Await You Competitive compensation and 401k matchingEnjoy a healthy work-life balance with insurance plans (health, dental, vision) and maternity benefits.Associate purchase and discount programs for new and pre-owned vehicles, services, parts, collision, accessories, and AutoGearAccess amazing deals and discounts through YouDecide, a website with offers from top providers and retailersJoin our DRVPNK mission to raise and donate millions of dollars to cancer research and treatment, partnering with cancer charities nationwide AutoNation is one of the largest automotive retailers..." That's more benefits and company info. We should combine benefits content, but avoid duplication. We'll include a Benefits section with bullet list of benefits.
We need to extract list items: "Higher income potential", "Full benefits package including Paid Time Off & 401K w/ Company match", "Longevity bonuses", "Generous employee referral bonus program for Technicians (employees can earn up to $3,000 per Tech referral!)", "Employee discount on vehicle purchases, parts, & service", "Advancement opportunities". Also later: "Competitive compensation and 401k matching", "Enjoy a healthy work-life balance with insurance plans (health, dental, vision) and maternity benefits.", "Associate purchase and discount programs for new and pre-owned vehicles, services, parts, collision, accessories, and AutoGear", "Access amazing deals and discounts through YouDecide, a website with offers from top providers and retailers", "Join our DRVPNK mission to raise and donate millions of dollars to cancer research and treatment, partnering with cancer charities nationwide". Also maybe "AutoNation is one of the largest automotive retailers..." is more company description, not benefit. Might be considered boilerplate? It's not a benefit but could be considered company overview. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company overview may be considered not boilerplate but maybe not needed. However we should preserve substantive information. The company overview about AutoNation may be considered substantive but not a benefit. Could be placed under About the role? Not exactly. Might be better to include a separate section like "About the company" but not in allowed headings. The allowed headings list includes only those specific ones. We should not create other headings. So we could incorporate company info into About the role or Benefits? Probably better to keep only the sections that match headings. The instruction: "Prefer a few substantive sections over many thin ones." So we can include About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have Pay: there is "$30.69 - $53.71". That's pay range. Also later "Competitive compensation and 401k matching" but we already have pay. So we should include Pay section with that range.
Schedule: there is "Working Conditions On-site role; may require evening, weekend, day shift, Night shift or Moonlight shift Work performed in shop, lab, and outdoor operational settings.Occasional travel to remote testing or operational sites." That's schedule/working conditions. So we can include Schedule section with that.
Responsibilities: we have "Key Responsibilities" with sub-bullets: Advanced Diagnostics & Repair, Sensor & System Calibration, AV Hardware & Software Support, Field Operations & Testing Support, Documentation & Continuous Improvement. Each has bullet points. We'll create a - for each responsibility, maybe nested? The instruction: Use
- for any list of duties/requirements/benefits. So we can have a top-level list for responsibilities, each item can contain the subheading as bold? But we cannot add extra tags besides
, - ,
. We could embed the subheading inside the
- as plain text. That's fine.
Requirements: there is "Required Qualifications" list. We'll treat as Requirements section.
Qualifications: there is "Preferred Qualifications". Could be Qualifications section (maybe combine required and preferred?). But we have both Required and Preferred. We could have Requirements (required) and Qualifications (preferred). The allowed headings include Requirements and Qualifications. So we can put Required Qualifications under
Requirements
and Preferred Qualifications under Qualifications
. That seems appropriate.
Skills: there is no explicit skills list, but we could infer from responsibilities? However we should only include a section if posting has real specific content for it. There's no explicit "Skills" heading. So we omit Skills section.
Now we need to remove boilerplate: lines like "KEYWORDS: ..." remove. Also remove duplicated lines like "AutoNation is one of the largest automotive retailers..." maybe considered company overview but not under allowed headings; we could incorporate into About the role? Might be okay to keep as a paragraph under About the role? But About the role already has description; adding company overview may be okay but not strictly about role. However we could add a separate paragraph under About the role that includes company info. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that company overview somewhere. Since we cannot create a new heading, we could append it to the About the role paragraph as extra sentences. That would preserve it. However it may be considered boilerplate? It's not navigation/legal/EEO etc. It's substantive about the company. So we keep.
Also remove "Even if you do not meet every requirement, we encourage you to apply." That's application instruction, remove. Also "Join our team and help us foster a culture of belonging..." that's also application encouragement, remove. Also "We value innovation, teamwork, and a commitment to making a positive impact in the world." That's also fluff, maybe considered boilerplate? It's not legal/EEO but could be considered fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those, but it's generic fluff. Might be considered boilerplate? Not sure. Safer to remove generic fluff that is not specific content. The instruction says "Prefer a few substantive sections over many thin ones." So we could keep it if it's substantive? It's vague. I'd lean to remove it as it's not specific to the role. Also "AutoNation is committed to creating a diverse, equitable, and inclusive environment..." that's EEO boilerplate, remove.
Also "AutoNation is one of the largest automotive retailers..." we kept earlier as company overview; but that may be considered generic but still substantive. I'd keep it.
Now we need to format.
Let's extract each section content.
About the role: combine first paragraph and maybe company overview.
First paragraph: "The Advanced Autonomous Vehicle (AV) Technician is responsible for performing complex diagnostics, repairs, calibrations, and system integrations on autonomous vehicles. This role requires advanced troubleshooting of sensors, compute systems, networks, and mechanical/electrical components to ensure safe and reliable fleet operation. The technician collaborates closely with engineering, operations, and field safety teams to resolve escalated issues, execute technical projects, and provide subject-matter expertise on AV platforms."
Company overview: "AutoNation is one of the largest automotive retailers in the United States, offering innovative products, exceptional services, and comprehensive solutions, empowering our customers to make the best decisions for their needs. With a network of dealerships nationwide strengthened by a recognized brand, we offer a wide variety of new and used vehicles, customer financing, parts, and provide expert maintenance and repair services."
We could also include the DRVPNK mission? That's more benefit/CSR; maybe include in Benefits? It's about raising money for cancer research. Could be a benefit/perk. We'll include in Benefits.
Now Responsibilities: list each bullet.
From posting:
Key Responsibilities
Advanced Diagnostics & Repair
- Perform complex mechanical and electrical troubleshooting on AV powertrain, braking, suspension, and high-voltage systems.
- Diagnose, repair, and validate faults involving CAN networks, LIN bus, power distribution, and AV compute hardware.
- Utilize advanced diagnostic tools to perform root-cause analysis and resolve recurring system issues.
Sensor & System Calibration
- Conduct precise calibrations of LiDAR, radar, camera arrays, GPS units, IMUs, and perception systems.
- Validate sensor alignment, accuracy, and performance to meet AV operational standards.
- Support testing and verification of updated sensor platforms or new hardware integrations.
AV Hardware & Software Support
- Install, configure, and replace complex AV components, including compute modules, communication units, wiring harnesses, and networking equipment.
- Support engineering teams with software deployments, data extraction, log reviews, and local debugging.
- Execute test plans, collect vehicle data, and provide technical feedback on firmware and hardware performance.
Field Operations & Testing Support
- Support on-road and closed-course AV testing, including real-time troubleshooting during missions.
- Respond to escalated field issues, vehicle recoveries, and operational incidents.
- Coordinate with remote monitoring teams to address live AV technical needs.
Documentation & Continuous Improvement
- Maintain detailed documentation of repairs, calibrations, and diagnostics in fleet management systems.
- Identify system trends, propose solutions, and contribute to continuous improvement initiatives.
- Provide technical guidance, mentorship, and training to AV technicians and cross-functional team members.
We'll put each as - with the subheading as part of the text, maybe bold? But we cannot use ? Not prohibited but we should stick to allowed tags? The instruction only says use
for section headings, - for any list,
for prose. It doesn't forbid other tags, but to be safe we can just include plain text. We'll include the subheading as part of the li text.
Requirements (Required Qualifications):
- 3–5+ years of experience as an automotive, EV, robotics, or AV technician.
- Strong diagnostic experience with mechanical and electrical vehicle systems.
- Hands-on experience with sensor systems (LiDAR, radar, cameras) and computer hardware.
- Prof
- for any list of duties/requirements/benefits. So we can have a top-level list for responsibilities, each item can contain the subheading as bold? But we cannot add extra tags besides
,
- ,
. We could embed the subheading inside the
- as plain text. That's fine.
Requirements: there is "Required Qualifications" list. We'll treat as Requirements section.
Qualifications: there is "Preferred Qualifications". Could be Qualifications section (maybe combine required and preferred?). But we have both Required and Preferred. We could have Requirements (required) and Qualifications (preferred). The allowed headings include Requirements and Qualifications. So we can put Required Qualifications under
Requirements
and Preferred Qualifications underQualifications
. That seems appropriate. Skills: there is no explicit skills list, but we could infer from responsibilities? However we should only include a section if posting has real specific content for it. There's no explicit "Skills" heading. So we omit Skills section. Now we need to remove boilerplate: lines like "KEYWORDS: ..." remove. Also remove duplicated lines like "AutoNation is one of the largest automotive retailers..." maybe considered company overview but not under allowed headings; we could incorporate into About the role? Might be okay to keep as a paragraph under About the role? But About the role already has description; adding company overview may be okay but not strictly about role. However we could add a separate paragraph under About the role that includes company info. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that company overview somewhere. Since we cannot create a new heading, we could append it to the About the role paragraph as extra sentences. That would preserve it. However it may be considered boilerplate? It's not navigation/legal/EEO etc. It's substantive about the company. So we keep. Also remove "Even if you do not meet every requirement, we encourage you to apply." That's application instruction, remove. Also "Join our team and help us foster a culture of belonging..." that's also application encouragement, remove. Also "We value innovation, teamwork, and a commitment to making a positive impact in the world." That's also fluff, maybe considered boilerplate? It's not legal/EEO but could be considered fluff. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not exactly those, but it's generic fluff. Might be considered boilerplate? Not sure. Safer to remove generic fluff that is not specific content. The instruction says "Prefer a few substantive sections over many thin ones." So we could keep it if it's substantive? It's vague. I'd lean to remove it as it's not specific to the role. Also "AutoNation is committed to creating a diverse, equitable, and inclusive environment..." that's EEO boilerplate, remove. Also "AutoNation is one of the largest automotive retailers..." we kept earlier as company overview; but that may be considered generic but still substantive. I'd keep it. Now we need to format. Let's extract each section content. About the role: combine first paragraph and maybe company overview. First paragraph: "The Advanced Autonomous Vehicle (AV) Technician is responsible for performing complex diagnostics, repairs, calibrations, and system integrations on autonomous vehicles. This role requires advanced troubleshooting of sensors, compute systems, networks, and mechanical/electrical components to ensure safe and reliable fleet operation. The technician collaborates closely with engineering, operations, and field safety teams to resolve escalated issues, execute technical projects, and provide subject-matter expertise on AV platforms." Company overview: "AutoNation is one of the largest automotive retailers in the United States, offering innovative products, exceptional services, and comprehensive solutions, empowering our customers to make the best decisions for their needs. With a network of dealerships nationwide strengthened by a recognized brand, we offer a wide variety of new and used vehicles, customer financing, parts, and provide expert maintenance and repair services." We could also include the DRVPNK mission? That's more benefit/CSR; maybe include in Benefits? It's about raising money for cancer research. Could be a benefit/perk. We'll include in Benefits. Now Responsibilities: list each bullet. From posting: Key Responsibilities Advanced Diagnostics & Repair - Perform complex mechanical and electrical troubleshooting on AV powertrain, braking, suspension, and high-voltage systems. - Diagnose, repair, and validate faults involving CAN networks, LIN bus, power distribution, and AV compute hardware. - Utilize advanced diagnostic tools to perform root-cause analysis and resolve recurring system issues. Sensor & System Calibration - Conduct precise calibrations of LiDAR, radar, camera arrays, GPS units, IMUs, and perception systems. - Validate sensor alignment, accuracy, and performance to meet AV operational standards. - Support testing and verification of updated sensor platforms or new hardware integrations. AV Hardware & Software Support - Install, configure, and replace complex AV components, including compute modules, communication units, wiring harnesses, and networking equipment. - Support engineering teams with software deployments, data extraction, log reviews, and local debugging. - Execute test plans, collect vehicle data, and provide technical feedback on firmware and hardware performance. Field Operations & Testing Support - Support on-road and closed-course AV testing, including real-time troubleshooting during missions. - Respond to escalated field issues, vehicle recoveries, and operational incidents. - Coordinate with remote monitoring teams to address live AV technical needs. Documentation & Continuous Improvement - Maintain detailed documentation of repairs, calibrations, and diagnostics in fleet management systems. - Identify system trends, propose solutions, and contribute to continuous improvement initiatives. - Provide technical guidance, mentorship, and training to AV technicians and cross-functional team members. We'll put each as - with the subheading as part of the text, maybe bold? But we cannot use ? Not prohibited but we should stick to allowed tags? The instruction only says use
for section headings,
- for any list,
for prose. It doesn't forbid other tags, but to be safe we can just include plain text. We'll include the subheading as part of the li text. Requirements (Required Qualifications): - 3–5+ years of experience as an automotive, EV, robotics, or AV technician. - Strong diagnostic experience with mechanical and electrical vehicle systems. - Hands-on experience with sensor systems (LiDAR, radar, cameras) and computer hardware. - Prof
- for any list,
- ,