Une candidature complète en une minute
Un CV et une lettre de motivation personnalisés, prêts à envoyer.
Pure Resourcing Solutions Limited is seeking a Lead Software & Systems Engineer to lead the R&D software and systems within a growing team in Norfolk. The role combines hands-on coding with setting direction, defining how code is written, reviewed, merged, tested and released.
You’ll drive modular architecture, introduce proper verification/validation, and mentor a small team of engineers across physics, controls, and electronics. Occasional UK travel may be required.
Norfolk, on-site | £65k-£85k (some flexibility both above and below that range for exceptional candidates)
Would you like to lead the next phase of how an R&D team builds software, at a company that genuinely wants modern practice, not just talks about it?
Defence experience isn't required, so if you've fancied moving into the sector, this is a strong way in.
My client designs and builds complex defence systems. Their R&D team works three to five years ahead of live programmes, working out what the next customer requirement will be before anyone’s asked for it. Small team, around eight engineers, hard technical problems. They're growing it now, and this is one of the key leadership roles they're creating to do that.
You’ll lead software and systems within R&D. What’s there works, but it has grown organically: lots of branches, everyone doing things slightly differently, an architecture built on older thinking. Your job is to bring structure without killing the pace. Define how code is written, reviewed, merged, tested and released. Then make it stick.
It’s hands-on to start. The team is small right now, so you’ll be writing code as well as setting direction, then building the team underneath you.
You get to shape the next phase of how a department builds software
Interesting problems: real-time computation, sensor data, physics-heavy systems
A new role, not a backfill, with a team to build under you
A director who actively wants the change, rather than a "we'll modernise one day" setup