This is for someone whos comfortable getting hands:on. Someone who can plug into a board, trace a fault, challenge assumptions, and help ship something solid.
Youll be in the guts of embedded systems, working alongside engineers who actually build the thing. Code, hardware, firmware : all of it. The brief is simple: make sure it works properly, under real conditions, not just in theory.
What youll be doing
Youll sit inside a multi:disciplinary engineering team, not off to the side.
Day to day, that means validating embedded software and firmware running on real hardware : not simulators alone. Youll be setting up tests, breaking things (on purpose), figuring out why they broke, and working with the people who wrote the code to fix it.
Youll help shape how testing is done : environments, tooling, approach. If somethings clunky or inefficient, youll be expected to improve it.
Theres a strong system:level angle here too. Youll be looking at fully integrated products : software, electronics, and mechanical elements all working together : and making sure they behave as they should in the real world.
Its an Agile setup, so youll be part of stand:ups, reviews, and the usual cadence. Nothing ceremonial : just enough structure to keep things moving.
And yes, youll document what matters: what you tested, what failed, what got fixed.
What you need to bring
Youve worked with embedded software, low:level stuff, typically in C or C++. You understand how it interacts with hardware because youve seen it, not just read about it.
Youve done testing, validation, or debugging in a real system : not just writing test cases in isolation. You know how messy things get when hardwares involved, and youre comfortable operating in that space.
You understand the software lifecycle, but more importantly, you know where testing actually adds value within it.
This role suits someone whos practical. You dont wait for perfect specs : you get stuck in, investigate, and move things forward.
Useful extras (not deal:breakers)
If youve worked in regulated or safety:critical environments, thats a plus : youll already understand the level of rigour expected.
Experience with comms protocols like UART, RS232 or CAN will help, especially when youre digging into system behaviour.
If youve touched test frameworks, automation, or built test setups before, even better.
Basic electronics knowledge goes a long way here : being able to read a schematic or understand what the hardwares doing will make your life easier.
Exposure to C, or .NET is useful, but not essential.
Tools and environment
Youll be working with embedded C/C++, standard version control (Git), and a mix of debugging and test tools. Nothing overly restrictive : the focus is on getting the job done properly.
The practical bits
Youll need to be eligible for SC clearance.
There may be occasional travel : typically to suppliers or customers : but its not a constant.