Automotive engineer to robotics jobs: what transfers?

What does the Mind Robotics hire say about robotics jobs?

Mind Robotics named Doug Field its president on 13 October 2026, and the hire tells you precisely where robotics money is going: toward people who know how to build physical products at volume. Field was Tesla's chief vehicle engineer on the Model 3, ran Apple's special projects group, and led Ford's EV and software division from 2021 until he stepped away this past April. He was also employee number one at Segway. Mind Robotics itself was spun out of Rivian in November 2025, with founder RJ Scaringe as acting CEO and chair, and has since raised more than a billion dollars from Accel, Andreessen Horowitz, Eclipse, Kleiner Perkins, and the venture arms of Volkswagen and Salesforce.

Read the company's strategy and the logic gets sharper. Mind Robotics is building purpose-built industrial robots running on foundation models, and Scaringe has been explicit that it won't try to copy human biomechanics the way some humanoid programmes do. Its advantage is Rivian: a live, high-volume manufacturing environment for training and deploying models, with Rivian as first customer. That framing matters to you more than the funding round does. The company is betting the hard part isn't the demo — it's getting hardware to survive a real factory at rate. Surviving a real factory at rate is what automotive engineering is, and has been for a century.

This isn't one executive's career move either. Robotics startups raised more capital in the first half of 2026 than in all of 2025, humanoids are running paid pilots on lines at BMW, Mercedes-Benz and Amazon, and recruiters are openly pulling candidates out of autonomous vehicles, industrial automation and aerospace. One analysis of active US postings puts open robotics engineering roles above 65,000. If you've been reading the headlines about which EV jobs still keep hiring in 2026 and wondering where the exit ramp is, this is it — but the ramp is a vocabulary problem before it's a skills problem.

Which automotive skills do robotics employers actually pay for?

Robotics companies pay the most for four things automotive engineers already have: high-volume manufacturing and DFM judgement, supplier industrialisation, functional safety competence, and electromechanical actuator design. Read an actual posting and it's unmistakable. A humanoid robotics manufacturing engineering role will ask for direct application — not awareness — of PPAP, APQP, process FMEA, control plans, MSA and SPC, plus 8D root-cause work, GD&T and metrology, on-site supplier process audits, and familiarity with ISO 9001, IATF 16949 or AS9100. It will then list automotive high-reliability electromechanical environments as preferred background. That is your résumé, almost word for word, filed under a different industry label.

Functional safety transfers more cleanly than most people realise. If you've built a safety case to ISO 26262 — hazard analysis and risk assessment, safety goals, ASIL decomposition, diagnostic coverage — you already think in the structure that machinery safety uses. Robotics simply speaks IEC 61508's other dialects: ISO 13849-1 performance levels, IEC 62061 SILs, the ISO 10218-1 and -2 series updated in 2025, ISO/TS 15066 for collaborative operation, and ANSI/RIA R15.06 and R15.08. Senior functional safety postings in robotics ask for exactly that lifecycle experience, vendor and lab validation management, and tools like SISTEMA. Say so in those words and you stop looking like a career changer.

Hardware and controls follow the same pattern. Actuator work in robotics means BLDC servos, harmonic drives, dual encoders, motor drivers, thermal derating and duty-cycle modelling, talked about over CAN and EtherCAT — all of which an e-axle, inverter or e-motor engineer has lived in. Controls roles want real-time C++, model predictive control, and simulation in MuJoCo, Drake or MATLAB. Validation engineers want HIL rigs, DV and PV test plans, and reliability growth. The same mapping exercise applies if you're weighing where high-voltage and battery QA skills transfer next across adjacent industries rather than robotics specifically.

Stack experience, recruiters say, predicts fit better than years served. So lead with the stack.

Which parts of your automotive CV should you cut?

Cut anything whose meaning dies outside your old OEM. Internal programme codes, gateway names, vehicle nameplates nobody outside the business recognises, and sentences built around "J1" or "Job 1" read as noise to a robotics hiring manager and give an ATS keyword set that matches nothing in the posting. Homologation and type-approval work — FMVSS, ECE regulations, emissions certification — has almost no counterpart in industrial robotics, so it earns a line at most. The same goes for NVH tuning aimed at passenger comfort, interior trim fit and finish, showcar builds, and dealer or aftermarket programmes. None of it is unimpressive. It's just untradeable.

Trim the platform-specific software too, unless you're aiming at embedded roles. Deep AUTOSAR Classic configuration, diagnostic trouble code catalogues, and OEM-specific toolchains are worth one line in a skills section, not a paragraph each. Replace the space with what robotics does buy: the number of units you shipped, the rate you held, the yield you moved, the suppliers you qualified, the standard you certified against. Two more structural fixes matter as much as the wording. Drop to two pages — robotics startups screen fast — and drop the dense, paragraph-style programme narrative that automotive CVs drift into. Bullets with numbers survive a six-second scan; prose doesn't.

One honest warning about job titles. "Automotive Engineer" or "Vehicle Integration Engineer – Programme X" tells a robotics parser nothing, and most career changers overcorrect by inventing a title they never held. Don't. Keep the real title and add a plain-language scope clarifier in the same line, then let the bullets carry the robotics keywords. If you want a second opinion on which of your experience actually crosses over, a CV review built for career changers and transferable skills will surface the lines that read as industry-locked before a recruiter decides for you.

How do you rewrite EV program bullets into robotics language?

Rewrite each bullet by keeping the scale and swapping the vocabulary — the achievement stays, the standards and stack names change. Here's the first, a supplier bullet. Before: "Led supplier quality for EV battery module programme, managing 14 Tier 1 suppliers through PPAP to SOP." After: "Owned supplier industrialisation for 14 electromechanical suppliers: on-site process audits and capability assessments, PFMEA and control-plan sign-off, Cp/Cpk studies and 8D root-cause closure; took a 400-part assembly from prototype builds to rate production." Same work, same numbers — swap in your real ones — but now it hits supplier industrialisation, production readiness and rate production, which is the exact language robotics manufacturing postings use.

Second, functional safety. Before: "Responsible for ISO 26262 compliance of traction inverter control software (ASIL C)." After: "Delivered the functional safety case for a high-power motion control unit: HARA, safety goals, ASIL C decomposition and diagnostic coverage targets, validated with supplier labs — directly mappable to ISO 13849-1 PL d and IEC 62061 architectures for robot safety functions such as safe torque off and speed-and-separation monitoring." Third, hardware. Before: "Designed and validated e-axle actuator assembly; reduced warranty claims 22%." After: "Designed a BLDC-driven actuator module — harmonic drive, dual encoders, CAN and EtherCAT feedback — through DV and PV testing; cut field failures 22% in service, with thermal derating and duty-cycle models rebuilt for continuous-duty operation."

Notice what each rewrite does: it names the standard the new industry cites, names the bus and the component, and keeps one hard number. Do that across eight to twelve bullets and the CV reads as a robotics hardware engineer who happens to come from cars. That's also the point where tooling earns its keep: paste the robotics job description into HRLens's AI CV builder with your existing CV and refine the bullets by chat, in six ATS-friendly templates. Then tighten the story behind the move — how to answer why you're changing careers is the same argument your bullets make, spoken out loud.

What robotics job titles and keywords should you target?

Target the titles where automotive experience makes you the scarce candidate, not the marginal one: Manufacturing Engineer (Electromechanical), Supplier Industrialisation or Supplier Quality Engineer, NPI Engineer, Functional Safety Engineer, Actuator or Mechatronics Engineer, Controls Engineer, Robot Integration Engineer, and Test and Validation Engineer. Avoid, at least for your first move, perception, whole-body control and vision-language-action roles. The pool with hands-on experience on real legged or dexterous hardware is tiny — recruiters talk about a couple of thousand engineers nationally — and every funded programme is bidding for them. You won't win that fight with a six-week course, and you don't need to.

Here's my unpopular opinion: learning ROS 2 to "break in" is usually the wrong first investment. It's a reasonable second one. What almost nobody in robotics has is a person who has shipped hundreds of thousands of electromechanical units with a PPM target and a warranty budget attached. That scarcity is your leverage, and it's priced accordingly — US robotics engineer pay averages around $132,000 on 2026 aggregator data, roughly $25,000 to $40,000 above typical automotive engineering averages, with humanoid and general-purpose programmes paying well above that at senior level. Learn enough ROS 2, Gazebo and Isaac Lab vocabulary to hold a conversation. Sell manufacturing scale.

Two practical notes before you apply. Pay isn't guaranteed to rise — moving from a senior OEM grade into an integration role can still cost you, and it's worth modelling what a career-change pay cut actually costs against your own numbers rather than the sector average. And tailor per posting: robotics job ads vary wildly in stack, so one generic CV will miss most of them. Run the file through a free AI CV analysis with the job description pasted in, check your ATS compatibility and the missing skills it flags, and fix those before you send. Expect three to six months of applications, not three weeks.

Frequently asked questions