Five Minutes With Eryk Marczak

Our systems depend on talented engineers who can navigate complex challenges, helping SEA deliver critical capabilities for our customers around the world. Eryk Marczak, Systems Engineer in Integrated Maritime Systems, works on everything from the early stages of project development to final certification activities. We checked in with Eryk to find out more about his role at SEA. 

Can you tell us a bit about your role?

My role involves moving between different projects at various stages of the engineering lifecycle. I work mainly on submarine programmes, but over the last three years, I’ve broadened my experience across multiple projects. On some projects I’m focused on final certification and qualification activities, making sure we’ve delivered what we set out to do. On others, I’m right at the start of the V model (an engineering framework that links each development stage directly to a matching testing stage); helping to develop requirements, working with customers, and preparing for design reviews. No two days are the same, which is one of the things I enjoy most.

What projects have you been most proud of since joining SEA?

The major submarine programme I’ve been involved in from the beginning. I’ve seen it progress through design reviews, manufacturing and qualification activities, and now into its final stages. Being able to look back and see how far the project has come is really rewarding. I’m also proud of the major project reviews and customer tollgates we’ve passed along the way. Those milestones represent months of work from the whole team, and it’s always satisfying when that effort is recognised with a successful outcome. I also had the opportunity to take responsibility for a smaller subsystem, which allowed me to gain experience leading a specific area of work.

What do you enjoy most about working at SEA?

The people, without a doubt. Everyone talks about SEA’s people being its biggest strength, and I think that’s true. The teams do a great job of keeping morale high, even when projects face challenges or setbacks. Engineering can be demanding, so having supportive colleagues makes a huge difference. I also appreciate the flexibility and trust that comes with working at SEA. The hybrid working environment works well, and there’s a strong culture of trusting people to get on with their jobs. That level of trust is important to me.

What has been your biggest challenge?

My biggest challenge has been working on a project that started right at the beginning of the design phase. Before joining SEA, most of my experience was on the qualification and verification side of projects, so activities such as writing requirements and developing the early stages of a design were relatively new to me. The way I overcame that was by being willing to try things, accepting that I wouldn’t get everything right first time, and learning from experienced colleagues around me. We successfully completed our Systems Requirements Review (SRR), and the feedback from the customer was very positive.

I think it reinforced an important lesson: engineering is about finding solutions, and that often means learning through trial and error rather than being afraid to make mistakes! A lot of my development has come through taking on new challenges and learning by doing. I’ve worked across different disciplines, gained experience with new processes and tools, and benefited from guidance from experienced colleagues.

How do you see Systems Engineering evolving in the future?

I hope Systems Engineering becomes even more integrated into projects from the very beginning, helping shape how work is planned and delivered. More broadly, I think the role of the Systems Engineer will remain essential because there will always be a need to bring different engineering disciplines together and ensure solutions meet requirements. Tools like Artificial Intelligence (AI) may help reduce time spent on documentation and reviews, giving engineers more time to focus on solving problems and delivering effective solutions.

Thank you, Eryk.