Principal Firmware Engineer/ Team Lead

Catapult Sports•Boston, MA

2d•Hybrid

About The Position

Catapult is building the future of sports performance technology, with a mission to Unleash the Potential of every athlete and team on earth. We don't just work in the sporting industry; we are actively changing it. Since 2006, our solutions have been leading the way in sports performance software, science, and data, in a world where 1% can literally mean the difference between winning and losing. We work with over 5,000+ teams around the world, empowering coaches, managers and trainers in premier teams in the NFL, NBA, NHL, MLS, EPL, AFL, NRL, NCAA and more. We provide the information they need to optimize athletes’ health, game-day readiness, and performance, as well as in-game tactics. Catapult is a sports technology company that empowers professional teams to make data-driven decisions. We deliver health, performance, video, and AI insights from the locker room to competitive environments, ensuring every decision is an opportunity to gain an advantage, sharpen performance, and build lasting success. WE WANT PEOPLE WHO ARE PASSIONATE ABOUT SOLVING HARD PROBLEMS We are looking for a Principal Embedded Systems Engineer to own the platform that our camera-based products run on – from the Linux user-space stack, to the C++ peripherals layer that talks to motors and sensors, to the OTA system that keeps thousands of devices in the field healthy. Based in Boston (hybrid), you will lead and player-coach a small team within the embedded systems domain, reporting to a Senior Director of Engineering. You'll be the technical owner of our on-device system supporting the movement tracking functionality of the product. This is a role for someone who thrives on breadth. In any given week, you might be making an architecture decision in the on-device system runtime, tuning a motor control loop, reviewing a schematic with an EE before a board respin, or adding new robustness to the OTA system. You needn’t be a roboticist or an EE, but excited to branch into those domains when the problems call for it. If you've owned an embedded product end-to-end – software architecture, hardware bring-up, the unglamorous parts of shipping at scale – this is your kind of problem.

Requirements

8+ years of software engineering experience, with significant time spent on embedded Linux systems or otherwise close to hardware.
Strong proficiency in C/C++ and Python – you're comfortable across the stack from real-time C++ peripherals code to Python application services.
Demonstrated experience shipping and operating embedded products at scale: OTA, fleet observability, manufacturing provisioning, and the operational realities of devices you can't easily reach.
The ability to own ambiguous problems end-to-end: scoping, prototyping, shipping, and measuring – across software, hardware, and the seams between them.
Comfort with leadership: you've mentored engineers, led technical direction, or driven cross-team initiatives, even if your title didn't say "lead."
Baseline hardware fluency – reading a schematic, debugging with a scope or logic analyzer, and collaborating with EEs.

Nice To Haves

Experience with motor control, sensor fusion, or other robotics-adjacent problems (Kalman filtering, control loops, IMU integration).
Experience with edge AI accelerators, depth cameras, or video pipelines on embedded hardware.
Microcontroller firmware experience — not required for our current platform, but useful for future work.
Experience with containerized deployment on ARM, systemd, udev, device tree, or kernel modules.

Responsibilities

Own the technical direction of our on-device platform: the Linux application stack, the C++ peripherals layer (camera driver, IMU estimation, motor control, I2C/SPI/GPIO peripherals), OTA, and the deployment to the device fleet.
Lead and mentor a small team, setting priorities, reviewing designs, and driving execution while remaining deeply hands-on in the codebase.
Make and defend architectural decisions across a multi-language system (Python, C++, containerized services on ARM Linux).
Stretch into adjacent domains as the work demands – motor control, sensor filtering, hardware debugging, board bring-up support, manufacturing/assembly-line QA tooling.
Partner with electrical engineers on hardware design changes and new product introductions: reading schematics, debugging boards with DMM/scope/logic analyzer, and feeding hardware learnings back into firmware and software.