BRINC
Software Engineer, Embedded
About this role
BRINC, a public safety technology company, seeks an experienced embedded software engineer to design and develop on-device software for their drone and hardware product line. You'll own the full software development lifecycle for flight-critical systems serving over 600 public safety agencies.
What you'll do
- Develop flight-ready embedded software primarily in C/C++ for drones, controllers, and support hardware
- Design system architectures and establish implementation methodologies for the engineering team
- Collaborate with electrical, mechanical, perception, and manufacturing teams on hardware integration
- Debug field issues, gather customer feedback, and support product deployments
- Document and version-control all technical contributions
- Conduct hardware bring-up and validation testing
What they're looking for
- C/C++ and Python programming
- Embedded systems development and optimization
- Standard embedded interfaces (I2C, SPI, UART, CAN)
- Experience with SoC and MCU platforms
- Hardware bring-up and testing
- Debugging and performance optimization
- Real-time operating systems (RTOS)
- Embedded Linux/Yocto
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.
BRINC
BRINC builds drone systems and cloud platforms that enable public safety agencies to deploy drones to emergency response situations like 911 calls. The company is hiring for engineering roles across navigation and sensing, electrical systems, RF communications, embedded software, and fullstack web development to support their drone hardware and LiveOps platform.
- Website
- brinc.io
Likely interview questions
- Walk us through your experience developing embedded software in C/C++ for resource-constrained devices. What challenges have you faced optimizing for memory and performance?
- Describe your experience bringing up new hardware and working with embedded interfaces like I2C, SPI, UART, and CAN. How have you debugged hardware-software integration issues?