Mechatronics Engineer
Carry a connected product from schematic and layout through production firmware to the bench rig that checks every release.
We design connected hardware and write the software behind it. This role sits where those two meet, so the same person takes a circuit from schematic through firmware to the rig that tests it.
Most of our hardware work arrives half-finished. There's a board from a vendor, a firmware contractor who has moved on, and a cloud team still waiting on device data. Getting those three to agree with each other is usually the job before anything can ship.
What You Would Work On
- Schematic capture and board layout for sensor, power, and microcontroller circuits, rigid and flex, with revisions driven by what the bench and the firmware tell us.
- Production firmware in C++ on modern 32-bit microcontrollers, most recently Renesas and Arduino parts, covering sensor drivers, calibration and self-test routines, event detection, alarm handling, and the protocols the device speaks.
- Timing work on multi-channel analog front ends, where the shape of the acquisition loop decides whether the data is good enough to act on.
- Over-the-air updates for constrained parts. That means owning how an image is packaged and shrunk, how a device works out which build applies to it, and how a release reaches one unit before it reaches the fleet.
- Radio bring-up, plus the connectivity the device speaks to the outside world over BLE, WiFi, and MQTT.
- Battery and low-power work, from charge behavior and state-of-charge monitoring through to sleep modes and the rails that stay energized when you thought they were off.
- Design review of vendor deliverables. We read a package for BOM completeness, clean rule checks, and connector and harness detail, then write up what has to change before anything gets fabricated.
- Manufacturing handoff, which means schematics and layout files, BOM and Gerbers, assembly and test notes, hardware-in-the-loop rigs, and the flash and provisioning scripts a contract manufacturer builds from.
- Regulatory groundwork alongside the design, covering radio certification and the conditions that come with a pre-certified module, plus environmental and vibration qualification.
What We Look For
- You've shipped firmware that went into production on a real product, and you can talk about how it behaved in the field.
- You're fluent in C and C++ on bare metal or a thin RTOS, and you'll open a datasheet when you need I2C, SPI, or UART to behave.
- You read schematics and lay out boards yourself, and you have views on grounding, decoupling, and connector choice that you can defend.
- Analog and mixed-signal front ends are familiar ground, and you know what a calibration has to prove before a unit leaves the bench.
- You've taken a design through a contract manufacturer at least once and know what they need from you and when.
- You write clearly. A good share of this work is telling a client, in writing, exactly what's wrong with a deliverable and what it will cost to fix.
Nice to Have
- Renesas RA, Nordic nRF, STM32, or Espressif parts.
- Multilayer stackups, impedance control, and EMC work.
- Motor control, power electronics, or RF design.
- Test fixtures and calibration tooling, including the software an operator runs on the production floor.
- Battery shipping classification work such as UN 38.3.
- Embedded Linux, Yocto, or A/B update systems, since our device work spans both ends.
- Quick-turn prototype assembly and overseas part sourcing.
Nobody has all of these. If you have most of the section above and two or three of these, we'd like to hear from you.
How Hiring Works
You send a resume and a note. If it looks like a fit we'll have a call about the work you've done, then a longer technical conversation with the people you'd be working beside. We don't ask for unpaid take-home projects.
Before you write
The most useful thing you can send is a specific account of something you built and what was hard about it. Our own work is described on these pages if you want a sense of what we mean.
Apply for Mechatronics Engineer
Attach a resume and tell us about work you've done that's close to this. A few paragraphs is plenty.