Lexington Medical, Inc.
Embedded Software Engineer
About this role
Lexington Medical seeks an early-career Embedded Software Engineer to develop firmware for minimally invasive surgical stapling devices. You'll work on ARM-based microcontroller systems, integrate hardware communication protocols, and collaborate across engineering teams in a regulated medical device environment near Boston.
What you'll do
- Design, implement, and test embedded firmware in C/C++ for ARM Cortex-M microcontrollers
- Develop low-level drivers and communication interfaces (SPI, I²C, CAN, UART, USB) that control motors and sensors
- Support hardware bring-up, debugging, and system integration with electrical and mechanical teams
- Participate in code reviews and learn modular firmware design best practices
- Conduct bench and system-level testing to verify firmware functionality
- Document software requirements, designs, and test results per FDA and IEC 62304 standards
What they're looking for
- Embedded C/C++ programming
- ARM Cortex-M microcontrollers
- Communication protocols (SPI, I²C, UART, CAN)
- Hardware debugging tools and lab equipment
- Real-time/bare-metal embedded systems
- Motor control and sensor integration
- Electromechanical systems
- Medical device regulatory knowledge (FDA, IEC 62304)
Opens the application — the Jobs AI extension fills it for you. Set up autofill
Opens the official application on the employer’s site. No login required.
Lexington Medical, Inc.
Lexington Medical designs and develops minimally invasive surgical devices, particularly precision surgical stapling systems for advanced procedures. The company is hiring engineers to support product development, component sourcing, and manufacturing scaling across mechanical design and supply chain roles.
View all jobs at Lexington Medical, Inc.Likely interview questions
- Walk us through a past embedded project where you integrated firmware with hardware—what challenges did you face with motor or sensor control?
- Describe your experience debugging embedded code at the hardware level. What tools did you use and how did you approach a difficult hardware-firmware integration issue?