We are looking for an experienced embedded C/C++ contractor to help us better understand how embedded teams really work, where their tooling falls short, and how modern development tools could improve their daily workflows.
You should have:
Several years of embedded C/C++ development experience
Experience working in a larger company or as a supplier to one
Strong focus on software development, tooling, debugging, testing, and workflows
Little to no focus on FPGA or hardware design roles
No Rust specialization required
We want to learn from someone who can speak practically about:
Day-to-day embedded development workflows and pain points
Tooling choices, adoption, and decision-making in embedded organizations
Debugging, productivity blockers, and timing-sensitive firmware development
RTOS usage, low-level hardware interaction, and peripheral-heavy workflows
Compliance, requirements, testing, and certified tooling constraints
IDEs, build/debug tool fragmentation, and opportunities for improvement
AI usage, remote development, custom scripting, and non-standard setups
How embedded projects start, evolve, and choose their software tools
We are especially interested in someone who can explain not just how things are done, but why the status quo exists and where the biggest opportunities for improvement are.
