Shape how research becomes a product, we’re building autonomous ground systems that operate in some of the world’s most demanding environments.

As our Strategic R&D organisation grows, we’re looking for a Senior Software Architect who enjoys solving complex engineering problems and thinking beyond a single product or software component.

This isn’t a traditional architecture role.

It’s about understanding how different systems fit together, helping research mature into products, and making architectural decisions that will still make sense years from now.

You’ll work at the intersection of Strategic R&D, Product Engineering and Product Management, helping connect ideas, technology and people.

What you’ll spend your time doing

You’ll work across multiple international R&D programmes focused on autonomy, communications, control systems and distributed software.

Some days you’ll be discussing architecture with researchers.

Other days you’ll be helping product teams understand how research can become something maintainable, scalable and ready for customers.

You’ll influence architectural direction across multiple projects while remaining close enough to the technology to challenge architectural decisions, prototype ideas when needed, and understand the practical trade-offs that complex systems require.

One thing matters more than anything else

This role doesn’t come with a large team or direct reports.

Instead, we’re looking for someone who naturally brings people together around good technical decisions.

You’ll spend a lot of time working across Strategic R&D, Product Engineering and Product Management, helping different teams solve shared problems, align on architectural direction and build software that can evolve.

If you enjoy creating clarity, challenging assumptions respectfully, and earning trust through good engineering rather than hierarchy, you’ll probably enjoy this role.

We’re probably looking for you if…

You enjoy questions like:

• Where should the system boundaries be?

• What belongs in the platform and what belongs in the product?

• How should different software components communicate?

• How do you make today’s prototype become tomorrow’s product?

• How do multiple engineering teams build independently without creating architectural chaos?

You’re comfortable thinking strategically, but you’re equally happy getting into technical discussions when needed.

You don’t need to know everything.

You do need to enjoy solving difficult engineering problems.

Your background might include

• Software Architecture

• Principal or Lead Engineering

• Embedded Software

• Distributed Systems

• Robotics

• Industrial Automation

• Telecommunications

• Automotive

• Aerospace

• Defence

• Safety-critical or mission-critical software

Experience with technologies such as C/C++, Python, Rust, ROS 2, Linux or real-time systems would be valuable. What matters most, though, is your ability to see the bigger picture. You won’t be expected to be the expert in every technology. Instead, you’ll help teams make good architectural decisions, understand trade-offs, and bring different engineering disciplines together around a shared technical direction.