Lead Software Architect(.net)

Leonardo; Luton; On-site; GBP 60,000 - 80,000; Full time

Job summary

A leading defence engineering firm in Luton is seeking a Software Architect (.NET) who can define solutions for mission planning and analysis tools. Ideal candidates will have experience in Agile methodologies and stakeholder management. The role prioritizes flexible working and offers great benefits, aiming to foster career growth in a supportive environment.

Benefits

Flexible working

Supportive environment

Career growth opportunities

Qualifications

• Strong experience as a software architect, particularly in Agile environments.
• Ability to define and influence solutions and requirements.
• Experience in leading technical solutions.

Responsibilities

• Define mission planning and analysis tools.
• Collaborate with stakeholders on requirements.
• Guide the development approach in the team.

Skills

Agile methodologies

Mission planning and analysis

Stakeholder management

Job description

Social network you want to login/join with:

Are you a software architect with the drive and experience to develop world-class engineering solutions?

Do you value flexible working with great benefits and an emphasis on work-life balance?

Do you want to grow your career and support others to do the same in an organisation with a wealth of support and opportunities?

Do you want to deliver technical leadership within multidisciplinary Agile teams working on the forefront of defence engineering projects?

If so, then you should apply for our SOFTWARE ARCHITECT (.NET) role.

What will a typical week look like?

• Defining solutions for mission planning and analysis tools
• Working with wider stakeholders to define and influence requirements
• Guiding the development approach considering modularity and reuse, best practice, toolchains, and much more
• Collaborating in the technical solutions with the systems engineering teams
• Learning and growing within a supportive environment

Below is a list of skills for the role; however, we favour behaviours and experience over a specific toolset, programming language, etc., so please use this as a guide, not a strict requirement.