Five Minutes with James Stevens


16 Apr 2026

5MW Web (5)

Our Systems Engineering team develop and maintain efficient systems, ensuring all components work together and meet the needs of our customers. We checked in with Head of Systems Engineering, James Stevens to find out more about what his team does at SEA.

Hi James, could you tell us more about your role at SEA?

As the Head of Systems Engineering at SEA, I’m responsible for a team of approximately 70 people; covering people, tools, and process for that area. Systems Engineering in itself is a discipline that focuses on analysing problems, developing requirements, architectures, then integrating, and testing the products against the initial requirements.

From a strategic perspective, systems engineering underpins SEA’s identity as a product-based organisation. By aligning with ISO 15288 methodologies, we ensure that what we build does exactly what it’s designed to do, and that it can be verified and validated with confidence. Ultimately, systems engineering helps derisk delivery and supports SEA’s long-term product strategy.

How did you become Head of Discipline at SEA?

I joined SEA, because I was encouraged by a former colleague in North Devon, where I grew up. After successfully applying, I joined in a systems role. I worked on our towed sonar product, KraitArray, and did some integration and trials work. In the time following, I was offered the Head of Systems Engineering position.

The role has evolved significantly since then. Initially, I acted as a systems subject matter expert. Over time, it’s become a full-time leadership position, focusing much more on building the discipline through people, tools, and robust processes.

What was it like transitioning from the Royal Air Force to civilian life?

Moving from the RAF to civilian life is a major change. The military provides a very structured environment - career progression, healthcare, and daily routines are all laid out for you. In civilian life, you suddenly need to manage those things independently, including your own career. Working on familiar platforms softened the adjustment. My RAF experience still benefits me today, particularly in terms of discipline, systems thinking, and understanding complex, safety critical environments.

My advice to others considering the transition is simple: don’t overthink it, just do it. There’s excellent resettlement support available, including training, funding, and workshops. Joining organisations with existing former service member communities can also make a huge difference.

How do you see Systems Engineering developing over the next few years?

One of the most significant developments is the increasing adoption of model-based systems engineering (MBSE). This approach reduces reliance on heavy documentation and allows engineers to focus more on system thinking and design.

Looking ahead, artificial intelligence (AI) is likely to be transformative. I expect we’ll see a shift from engineers doing first-pass work to engineers validating and assuring outputs generated by AI. Code generation, rapid prototyping, and virtual modelling will all accelerate development cycles. That said, defence remains relatively risk-averse, so we may adopt these technologies later than other industries; but the direction of travel is clear.

What advice would you give to someone who wants to follow in your footsteps?

The biggest advice is to keep doors open. Say yes to opportunities, even if they don’t seem like obvious fits. Systems engineering attracts people from a wide range of backgrounds, and that diversity is its greatest strength, everyone brings something different to the table. Systems engineering is a challenging but deeply rewarding career, and it plays a crucial role in bringing complex products to life.

Thank you, James.

Want to find out more? Have a look at What We Do