High integrity software engineer
- Level
- 6
- Typical duration
- 48 months (about 4 years)
- Max funding band
- £27,000
- End-point assessment
- 9 months
- Route
- Engineering and manufacturing
Developing software to support safety critical industries.
About the role
This occupation is predominately found in safety critical industries where software failure may cause serious damage or danger to life including aerospace, nuclear, automotive and process control sectors. The occupation can be found in large, medium and small employers across the world. High integrity software engineers may work on specific safety critical software products. They may also work on bespoke tooling and associated integrated environments and infrastructure. Employment fields include:
- aerospace manufacturers
- nuclear reactor controls manufacturers
- automotive safety critical software systems
- industrial process control systems
The broad purpose of the occupation is to design, develop and test, real-time safety-critical software. They develop embedded high integrity systems software and stand-alone applications used in sector specific support. They develop and test tools that support the creation of high integrity software. They support customers and suppliers by maintaining and improving software utilities and tools. They develop processes for the development and test of products. They review performance, design, test and use project management and continuous improvement techniques. They proactively find solutions to problems and identify areas for business improvement.
High integrity software engineers are typically office-based. They may be required to work in simulation rig testing facilities, or in operational environments.
In their daily work, an employee in this occupation may interact with customers. They may also interact with system operators, other specialist engineers, technicians, partners and suppliers. They also interact with colleagues across other areas in their organisation. For example, manufacturing, project management, quality assurance, finance, human resources, procurement and safety.
They typically report to senior engineers, senior specialists or chief engineers depending on the organisation.
An employee in this occupation is responsible for working ethically and professionally. They may work to regulatory requirements for sector specific industries. They must meet statutory and company regulations. For example, health and safety, environment and sustainability, cost, quality, accuracy and efficiency. High integrity software engineers work individually and as part of a team. They are responsible for the safety and security of the product they create. Depending on the size and structure of the organisation they may manage software technicians or teams of engineers.
How it compares
At 48 months (about 4 years), it is longer than average for a degree-level apprenticeship (the average across all 172 Level 6+ standards is 39 months).
The funding band — the maximum an employer's levy can contribute to training costs — is £27,000, at or above the £21,500 average for degree-level standards. Apprentices never pay tuition either way.
Entry requirements
Whilst any entry requirements will be a matter for individual employers, typically an apprentice might be expected to have already achieved academic qualifications of 96* UCAS points or above at A-Level standard or equivalent, to include two STEM-based subjects such as Maths, Physics, ICT, Computing or Electronics, plus five GCSEs at Grade 4 and above** including Mathematics, English and Double Science or equivalent qualification. (*Equal to 240 UCAS points prior to 2017, **Equal to Grades C and above).
Entry requirements are ultimately set by each employer — treat these as the baseline, not the bar.
What you come out with
- bachelor honours degree in software engineering (BEng), computer science (BSc), or other degree that directly aligns to the KSBs in the degree-apprenticeship — Level 6 (integrated degree)
- Professional recognition: The Royal Aeronautical Society — Incorporated Engineer (IEng). This degree-apprenticeship standard aligns with the Engineering Council’s learning outcomes, indicated in ‘Accreditation of Higher Education Programmes’ (AHEP) and the competence framework detailed in UK-SPEC for Incorporated Engineer (IEng). The experience gained and responsibility held by the apprentice on completion of the degree-apprenticeship will either wholly or partially satisfy the requirements for registration at this level.
- Professional recognition: The Chartered Institute for IT (BCS) — Registration for IT Technicians (RITTech). The experience gained and responsibility held by the apprentice on completion of the degree-apprenticeship will either wholly or partially satisfy the requirements for registration at this level.
What you'll learn
The official standard defines 11 core duties, 27 knowledge areas, 24 skills, 6 behaviours. This is the actual assessed content of the apprenticeship — worth reading before an interview, because competency questions are usually written straight from these lists.
Core duties 11
- Define and maintain the engineering plan detailing the implementation of software engineering solutions. In collaboration with multidisciplinary teams and organisational stakeholders.
- Identify, evaluate, derive, analyse and maintain software requirements for customer and projects.
- Define and maintain the architecture and design of software products, tools, utilities and applications to meet project requirements.
- Implement high integrity software design from combinations of new, modified and existing components to meet project requirements.
- Develop, define and execute testing of high integrity software products to verify functionality and performance.
- Analyse and review the high integrity software outputs.
- Undertake and complete build, configure and release of the high integrity software product.
- Verify that software processes and procedures comply with standards throughout the life cycle. These include local, national and international regulatory, legislative, customer and company standards. For example, cyber security, development, environmental, anti-bribery and corruption. Official Secrets Act, export control, safety standards.
- Review the in-service performance of software products, processes and systems. Assess the cause of any faults or problems and propose solutions.
- Manage stakeholders by communicating project status, technical and commercial information. For example, communicate success, risks and issues to all levels of the business.
- Define, monitor and co-ordinate the continuous improvement of software processes and methods.
Knowledge 27
- Mathematics: the mathematical techniques and analytical methods required to model software and hardware systems: algebra, calculus, geometry, Boolean Logic, trigonometry and statistics.
- Software requirements development: the requirement lifecycle from concept to release; gathering, specifications, validation.
- Software requirements engineering: maintenance, operating environment, identification of software security, modelling, human computer interaction, and identification of system safety.
- Software architecture: operating system concepts and architectural considerations.
- Software design development: structures, methodologies, techniques and validation.
- Software design engineering: software functions and interconnection, flexibility, coupling and cohesion, readability, maintainability, testability, safety, security and design verification.
- Modelling and simulation: creation and simulation of design models.
- Software implementation development: creation of executable code.
- Software implementation engineering: underlying concepts of computational thinking, abstraction, representation and modelling, language specifications including assembler, analysis, and inspection methodologies.
- Testing the software solution: test environments; debugging and profiling facilities.
- Test methodologies: methods used to test software; criticality.
- Configuration control: configuration management methods, software build processes, tools and change control.
- Software development environment: tool configurations, library functions, operating environment, compiler process and options, scripting and hardware or software integration.
- System security: statutory, regulatory, organisational and certification principles in a software product.
- Principles of quality: process conformations and assurance in a high integrity software engineering environment.
- Continuous improvement principles and techniques: Plan-do-check-act (PDCA), Lean, 6 Sigma, and Statistical Process Control (SPC). Lean manufacturing tools. Process mapping.
- Safety requirements: statutory, regulatory, organisational and certification principles (software safety integrity levels) in a high integrity software environment.
- Teamwork: conflict management, people development techniques, performance management, diversity and inclusivity.
- Information technology: general data protection regulation (GDPR), digital tools for presentation of data, digital communication and collaboration packages.
- Communication techniques: verbal, written and presentations.
- Time management techniques.
- Environment and sustainability: role of software design and implementation in the end-to-end value chain for sustainable products; optimising energy and resource consumption; relationship between obsolescence and sustainability.
- Project management: project planning, management of risks, commercial awareness, financial management and resourcing.
- Report writing techniques and methods. IT applications for technical reporting.
- Problem solving tools and techniques: lateral thinking, root cause analysis (RCA).
- Software development techniques: Waterfall, Agile, and Hybrid.
- Software integration techniques.
Skills 24
- Apply analytical methods; use mathematics and associated toolsets to characterise properties and behaviour of software.
- Read, interpret and use software engineering data. For example, requirements, design, code, test and release documentation.
- Develop and apply algorithms. For example, produce specification, design and implementation for algorithms.
- Select the design approach and tools for a given software engineering application and environment.
- Apply model-based techniques. For example, using simulations to verify the compliance to the parent requirements.
- Produce system and software designs. For example, produce state machine diagrams.
- Setup and configure tools and the environment. For example, verification tool to target hardware requirements, management tool to design tool, and configuration tool to development tools.
- Implement functional software solutions. For example, developing software solutions that incorporate new, legacy or commercial components.
- Develop and execute high integrity software test plans.
- Analyse and review high integrity software outputs. For example, design reviews, code walkthroughs, test script reviews.
- Use problem solving tools and techniques. For example: lateral thinking, root cause analysis (RCA), Kaizen, Lean manufacturing and Kanban.
- Apply configuration management and software build processes.
- Communicate with internal and external stakeholders; verbal and written.
- Write reports. For example, data, technical information, drawings, outcomes and recommendations.
- Present information. For example, presenting project progress and key performance indicators (KPI's) such as cost, quality, time, risk and opportunities. Presenting technical results into design reviews.
- Use information technology: digital tools for presentation of data, digital communication and collaboration packages.
- Use continuous improvement techniques and make recommendations. For example, Kaizen, Lean manufacturing and Kanban.
- Use project management techniques. For example, in estimating, risk, cost and budget control, time management and resource management.
- Identify and comply with legal and statutory requirements. For example: cyber security, software certification requirements, data protection, high integrity software safety, environmental protection and sustainability.
- Plan and manage own time.
- Apply and uphold ethical principles.
- Apply team working principles.
- Apply software development techniques. For example, Waterfall, Agile, or Hybrid.
- Apply software integration techniques. For example, networks, hardware or system integration.
Behaviours 6
- Lead by example and promote health and safety.
- Lead by example and promote environment, ethical and sustainable practices.
- Adapt to challenging or changing situations and be resilient to the effects.
- Collaborate and promote teamwork across disciplines.
- Lead by example to promote accessibility, diversity and inclusion.
- Commits to their own and others' professional development.
Live vacancies
No live vacancies for this course as of 2026-07-24 — new adverts appear on Find an apprenticeship daily, and many degree apprenticeship employers recruit on their own careers sites instead.
Universities registered to deliver it
2 universities are on the government provider register for this standard. Registration means they can deliver it — live vacancies depend on employer partnerships each recruitment cycle.
Related courses in Engineering and manufacturing
Advanced robotics engineer
To invent, design and implement new robotic solutions for challenges that have not currently been solved using new scientific advanced engineering methods and techniques.
Aerospace engineer
Creating aircraft components and equipment, specialising in a specific engineering discipline (for example - airframe, design and stress, systems integration, support engineering or manufacturing engineering).
Control systems engineer (degree)
Assuring that manufacturing runs smoothly in areas such as site maintenance.
Electrical and electronic engineer (degree)
Supporting the manufacturing of new products by bringing the product to life and resolving manufacturing problems.
Official sources
- Official standard page (Skills England)
- Registered training providers (Find apprenticeship training)
Occupational summary, duties, knowledge, skills and behaviours reproduced from the ST0013 apprenticeship standard (last updated 2025-01-13) — contains public sector information licensed under the Open Government Licence v3.0. Always check the official page before applying: standards get revised.