Meet Max - Capability Integration Engineer

Why did you become an engineer?

I started my career in BAE Systems as a graduate on Typhoon. I realised quickly that I enjoy bringing groups together to collaborate on projects and break down silos. I’m now a member of the Institute of Engineering and Technology (IET), and I plan to become a Chartered Engineer.

In my spare time, I’m a cave leader for a caving club, as well as the secretary for the club committee. Being a cave leader means being prepared for anything - taking the time before an event to understand the intention, the strengths and weaknesses of the team, and how to navigate expected pitfalls.

At home, I like to 3D print and paint gaming models. It’s important to express a level of creativity, even when painting multiples of the same thing – improvement lies within the unexplored areas of a subject, and new tools and new processes bring out the joy in both my hobbies and my work.

What does your role involve?

As a Capability Integration Engineer, I make sure that engineering teams have the capabilities they need to perform at their best – whether it’s supporting Agile ways of working, breaking new ground with business reporting, building communication networks that unite our department, or leading continuous improvement and empowering young engineers to push for grassroots change.

What does a typical day look like for you?

My work has me engaging with a wide range of people from across the business - from experienced heads of department, to tech apprentices on their first placement.

I work closely with the Mission Systems Senior Leadership Team, facilitating their next big game-changer, elevating our work culture to one of community, transparency, and integrity. Mission Systems as a team is constantly thinking ahead, not just understanding where we are today, but also what we’ll be doing tomorrow.

I have also had the opportunity to organise and compere our team's networking events, which helped me to build networks, learn about the business and our industry, and bring our community together. The events have caught on, with other delivery teams creating their own flavours, and even approaching me to consult.

Why is Capability Integration exciting?

It's like sculpting the wet clay of the future of combat air; building a programme of intelligent design that supports our goals. I work with senior team members to understand their requirements, and I can express my full creativity within the toolsets provided.

What would you say to others looking at a career in Capability Integration?

As a development engineer, you often learn about the specific tools and skills required to do your job well, and work to support your team in their goals.

As an integration engineer, not only are you supporting your team, but you are creating solutions that support all teams – our projects help build strong working relationships across teams. These relationships are built not on inter-dependence but on good faith and the desire to change for the better. 

For an engineer, developing that wider understanding of your place in the department, or on the programme, is just as important as gaining technical experience. I firmly believe that everyone should experience an Integration role at some point in their career.

What other skills do you think are important in your role?

An understanding of the engineering lifecycle is paramount when trying to create engineering capability solutions – when you understand what an engineering manager needs to deliver, the requirements write themselves.

Are there any skills you've built in your personal life that you find useful for your role?

As a recreational cave leader, I know that communication is one of the most important skills anyone can have – not only to provide clear, concise instruction, but also the ability to provide support and empathy. Risk assessment and an understanding of risk appetite is also a core skill, which I bring with me to make a safer and more effective workplace. 

How do you think you'll feel when Tempest flies for the first time?

It feels harder for me to take the credit for my contributions to the programme, as the work I do is much less functional. But when I consider that every day, I work to make things easier, to improve clarity and productivity for others, it’s clear to me that technical integration is the whetstone that sharpens the leading edge of our programme.