About Moment

Moment Motor Company converts iconic classic cars into high-performance electric vehicles. We've been doing this since 2017, and we've been featured in the Wall Street Journal, the New York Times, Bloomberg, and MotorTrend. Our shop in Austin builds 25+ cars at any given time — Porsches, Land Rovers, Mustangs, Alfas, Broncos, Mercedes, you name it — each one a fully bespoke conversion that has to look stock and drive like a modern EV. We're a team of about 15 people who care a lot about what we put on the road.

What this role is

We're hiring an EV Controls & Commissioning Engineer to own the electronics side of getting cars from "fully built" to "ready to drive." This is the person responsible for making the firmware, the software, the GUI and gauges, and all of the EV-specific electronics actually work together on every car we deliver — and for continuously building the tools and processes that let our shop do this faster, more predictably, and with fewer surprises.

This is not a desk-bound validation or DVP&R role. You're going to be on the shop floor with cars in front of you, with a laptop in one hand and a multimeter in the other, every week.

What you'll actually do

Start up cars - Every car we build goes through a commissioning phase before it can drive. You'll own that process: gather and validate the build configuration, flash firmware on the VCU, ECUMaster PMU (Power Management Unit), and BMS, configure the GUI and gauges, load and adapt the appropriate config files, validate every input and output, and drive the car through full functional checkout before it goes to the test driver.

Troubleshoot - A car logs an obscure OBD error code on its first drive. A pack voltage reading doesn't make sense. The heater contactor isn't firing. The SOC won't reset. The charger throws a fault on a customer's car halfway across the country. Our VCU is monitoring hundreds of signals and managing devices in every part of the vehicle, and the cars we build are intricate, one-off, and complicated — so things will misbehave when these systems first fire up. Your job is to get to the bottom of it: working with a technician to track down a bad crimp in a wiring harness, reading CANbus traffic to uncover a firmware bug in a vendor's component, sometimes with the vendor on the phone, sometimes alone in front of the car or working remotely from the logs.

Build tools and processes - A meaningful slice of this role is making the next car easier than the last. That looks like log viewers, gauge test programs, diagnostic scripts with proper version control, and process documentation that lets our technicians do more of the prep work upstream of you. The bar here is judgment: we want someone who reaches for a tool when it will pay back the time, and who knows when the right move is to just solve the problem in front of them. We're not looking for the engineer who builds an elaborate framework instead of fixing the bug.

Use AI - We expect you to be fluent with Claude, Cursor, or whatever you prefer — for analyzing logs, generating diagnostic scripts, writing tools, and summarizing what cars are telling you. We're not looking for someone who has heard of AI; we're looking for someone who already uses it daily and can show us things we haven't thought of.

What a typical week looks like

• Mon–Wed: You're commissioning a Porsche 911 conversion. You flash the VCU and PMU, configure the GUI and gauges for the customer's chosen layout, validate every accessory through the PMU, and drive the car through checkout. Halfway through, a customer's Mercedes 280SL across the country logs an obscure error — you pull the logs remotely and trace it to a bad CAN message coming from a vendor BMS.
• Thu: Deep work day. You're 70% done with a Python tool that parses one of our log formats and produces a diagnostic summary. You finish it, push it to the shared drive, and walk a technician through how to use it.
• Fri: A customer drops in to see his Bronco a few days before it ships. He drives it around the block and tells you the throttle map feels too aggressive at low speed. You sit with him at the car, smooth out the curve, update the calibration, and he leaves thrilled — his car, the way he wants it.

You should apply if

• You hold a BS in Electrical Engineering, Computer Engineering, or Computer Science — or you've taught yourself the equivalent and can prove it through projects.
• You have real EV systems experience: battery packs, motors, inverters, DC/DC converters, contactors, thermal management. Aftermarket, motorsport, or small-EV-startup experience is preferred over big-OEM experience.
• You can read a raw CAN trace and find a problem in it — building or editing DBC files, terminating networks correctly, debugging missing or malformed messages.
• You've flashed firmware on a VCU, BMS, or comparable device and have hands-on experience handling bootloader recovery, version mismatches, and config rollbacks when things don't go to plan.
• You're comfortable with at least one of the EV / aftermarket electronics ecosystems we work with: Ampere, Cascadia, ECUMaster, AEM (we no longer install AEM products in new builds, but their support is still relevant for cars in the field), and SME / Netgain. Equivalent experience with MoTeC, or with advanced non-EV-specific tools from Holley or similar, is acceptable.
• You can read a wiring schematic and trace a fault with a multimeter or oscilloscope. PicoScope experience is a particular plus.
• You write code — Python plus at least one C-family language. You've shipped tools that other people on a team relied on.
• You already use AI in your daily workflow and can describe specific things you've built or shipped with it.

Bonus points if

• You've worked in a small shop, motorsport team, or early-stage EV startup (5–50 person engineering org).
• You can solder, rework boards, and use a scope without thinking twice — extra credit for PicoScope fluency.
• You have public projects — GitHub, build threads, YouTube — that show what you tinker on for fun.
• You have a personal project car or a hobby that keeps your hands dirty.

You probably won't love this role if

• Your career has been pure validation, DVP&R, or test-plan execution at a Tier 1 or OEM with no integration or build-from-scratch experience.
• You need a written diagnostic procedure before you can start a debug.
• You don't have any code in your portfolio — not even a script.
• You think AI is a fad you'll get to eventually.

Pay: $40.00 - $60.00 per hour

Benefits:

• Flexible schedule

Application Question(s):

• Tell us about the most challenging EV (or vehicle) troubleshooting case you've personally solved, end-to-end. What were the symptoms, what was your hypothesis, how did you instrument it, and what did you find?

Experience:

• Automotive diagnostics: 3 years (Required)

Ability to Commute:

• Austin, TX 78745 (Required)

Work Location: In person