Afference
Firmware Engineer
Cleveland, OH (Remote)$113.5k–$170.3kfulltimemidAdded today
About this role
Design and develop embedded firmware for innovative haptic wearable devices in the spatial computing space. You'll own firmware architecture decisions, lead hardware bring-up through production, and collaborate across hardware and software teams to deliver reliable, cutting-edge solutions.
What you'll do
- Design, develop, and debug embedded firmware for wearable haptic hardware systems
- Drive firmware architecture decisions and technology stack selection
- Lead firmware integration, validation, and testing from early design through field deployment
- Troubleshoot complex firmware-hardware interactions and implement root cause fixes
- Port firmware across MCU platforms and develop secure update mechanisms
- Mentor team members and provide technical problem-solving support
What they're looking for
- C/C++ development for resource-constrained embedded systems
- Microcontroller (MCU) programming with deep understanding of peripherals, interrupts, and power domains
- RTOS-based systems development
- Communication protocols and hardware interfaces
- Lab equipment proficiency (oscilloscopes, logic analyzers, power analyzers)
- Firmware debugging, testing, and validation methodologies
- Hardware-firmware interaction understanding
- Technical documentation and specification writing
Opens the official application on the employer’s site. No login required.
Afference
Afference develops haptic wearable technology and custom ASIC chips for spatial computing, creating devices that deliver artificial tactile sensations through neural stimulation. The company is hiring Mechanical Engineers, Electrical Engineers, and chip design specialists to build innovative hardware and silicon solutions for next-generation wearable products.
View all jobs at AfferenceLikely interview questions
- Walk us through your experience developing firmware for power-constrained wearable devices—what challenges did you face and how did you optimize for low power consumption?
- Describe a time you debugged a complex hardware-firmware interaction issue. What tools did you use and what was your approach to isolating the root cause?