Enabling organisations to get valuable working software out in front of active users and improving the quality of digital services.
This occupation is found in a wide and diverse range of public and private sector organisations, from tech start ups through government departments to multinationals. Essentially any organisation of any size that builds and/or operates modern IT services.
The broad purpose of the occupation is to enable organisations to get valuable working software out in front of active users, both external and internal, frequently and safely, reducing time to market, delivering increased value - both with respect to the end user and the business - and improving the quality of digital services. At its simplest, DevOps is a philosophy and way of working that brings together two historically disparate parts of the IT organisation, namely those who develop the software and those who are then required to support it in the live environment. The DevOps Engineer encapsulates both disciplines, requiring the individual to understand and appreciate how their code functions when being used in the real world and troubleshoot any issues that may arise, while taking a cloud-infrastructure focused perspective. This means taking responsibility for all aspects of the development and operations process - the design, build, test, implement, release and continual iteration of products. Utilizing the advantages of Cloud computing to enable infrastructure to be defined in code moves the operations side away from traditional system administrator roles which are focused on troubleshooting traditional infrastructure-as-hardware. The convergence of these two topics drives DevOps culture and ways of working and creates the need for the new role of DevOps Engineer that works within the delivery team. The DevOps Engineer applies all the DevOps culture and software engineering disciplines to codified infrastructure.
In their daily work, an employee in this occupation interacts with other members of agile development teams, other areas within the organisation’s IT department and business areas, as well as 3rd-party suppliers. This is an office based or remote working role, with co-location preferable.
An employee in this occupation will be responsible for working collaboratively with a minimum of direct supervision within broad but generally well defined parameters, requiring the application of knowledge and understanding, skills and methods in a broad range of complex or technical work activities, performed in a variety of contexts. They will address problems which are non-routine while normally fairly well defined, taking responsibility for courses of action, including, where relevant, responsibility for the work of others and allocation of resources. They will typically pair with other technical roles, or work alone at times, and provide input to the planning of work and advise on design.
Individual employers will set the selection criteria, but this is likely to include A levels; a level 3 apprenticeship or other relevant qualification; relevant experience and/or an aptitude test.
| Duty | KSBs |
|---|---|
|
Duty 1 Script and code in at least one general purpose language and at least one domain-specific language to orchestrate infrastructure, follow test driven development and ensure appropriate test coverage. |
K4 K5 K6 K7 K8 K11 K12 K13 K14 K20 |
|
Duty 2 Initiate and facilitate knowledge sharing and technical collaboration with teams and individuals, with a focus on supporting development of team members. |
|
|
Duty 3 Engage in productive pair/mob programming to underpin the practice of peer review. |
|
|
Duty 4 Work as part of an agile team, and explore new ways of working, rapidly responding to changing user needs and with a relentless focus on the user experience. Understand the importance of continual improvement within a blameless culture. |
|
|
Duty 5 Build and operate a Continuous Integration (CI) capability, employing version control of source code and related artefacts. |
|
|
Duty 6 Implement and improve release automation & orchestration, often using Application Programming Interfaces (API), as part of a continuous delivery and continuous deployment pipeline, ensuring that team(s) are able to deploy new code rapidly and safely. |
|
|
Duty 7 Provision cloud infrastructure using APIs, continually improve infrastructure-as-code, considering use of industry leading technologies as they become available (e.g. Serverless, Containers). |
K1 K2 K3 K7 K8 K11 K12 K13 K14 K15 K17 K21 K24 |
|
Duty 8 Evolve and define architecture, utilising the knowledge and experience of the team to design in an optimal user experience, scalability, security, high availability and optimal performance. |
K1 K3 K4 K6 K7 K8 K9 K10 K11 K12 K15 K21 K24 |
|
Duty 9 Apply leading security practices throughout the Software Development Lifecycle (SDLC). |
K3 K4 K5 K6 K7 K8 K9 K10 K11 K12 K16 |
|
Duty 10 Implement a good coverage of monitoring (metrics, logs), ensuring that alerts are visible, tuneable and actionable. |
|
|
Duty 11 Keep up with cutting edge by committing to continual training and development - utilise web resources for self-learning; horizon scanning; active membership of professional bodies such as Meetup Groups; subscribe to relevant publications. |
|
|
Duty 12 Look to automate any manual tasks that are repeated, often using APIs. |
|
|
Duty 13 Accept ownership of changes; embody the DevOps culture of 'you build it, you run it', with a relentless focus on the user experience. |
K1: Continuous Integration - the benefits of frequent merging of code, the creation of build artefacts and ensuring all tests pass, with automation throughout - including common tooling.
Back to Duty
K2: The principles of distributed Source Control, including how to exploit the features of the tool, such as branching.
Back to Duty
K3: How to use data ethically and the implications for wider society, with respect to the use of data, automation and artificial intelligence within the context of relevant data protection policy and legislation.
Back to Duty
K4: The business value of DevOps in terms of Time, Cost, Quality, with an emphasis on building in internal Quality throughout the lifetime of the product.
Back to Duty
K5: A range of modern security tools and techniques - e.g. threat modelling, vulnerability scanning and dependency checking, with a general awareness of penetration testing - in order to deal with threats and attack vectors within code and across the cyber domain.
Back to Duty
K6: A range of problem solving techniques appropriate to the task at hand, such as affinity mapping, impact maps, plan-do-check-act/Deming.
Back to Duty
K7: General purpose programming and infrastructure-as-code.
Back to Duty
K8: Immutable infrastructure and how it enables continuous refreshing of software, namely the updating of the operating system, container and security patching.
Back to Duty
K9: Different organisational cultures, the development frameworks utilised and how they can both complement each other and introduce constraints on delivery.
Back to Duty
K10: How the user experience sits at the heart of modern development practices in terms of strategies to understand diverse user needs, accessibility and how to drive adoption.
Back to Duty
K11: Monitoring and alerting technologies and an awareness of the insights that can be derived from the infrastructure and applications - collecting logs and metrics, configuring alerting thresholds, firing alerts and visualising data.
Back to Duty
K12: The persistence/data layer, including which database/storage technologies are appropriate to each platform type and application when considering non-functional and functional needs; e.g. monolith, microservice, read heavy, write heavy, recovery plans.
Back to Duty
K13: Automation techniques, such as scripting and use of APIs.
Back to Duty
K14: Test Driven Development and the Test Pyramid. How the practice is underpinned by unit testing, the importance of automation, appropriate use of test doubles and mocking strategies, reducing a reliance on end-to-end testing.
Back to Duty
K15: The principles and application of Continuous Integration, Continuous Delivery and Continuous Deployment, including the differences between them.
Back to Duty
K16: How best to secure data; e.g. encryption in transit, encryption at rest and access control lists (ACL).
Back to Duty
K17: What an API is, how to find them and interpret the accompanying documentation.
Back to Duty
K18: Roles within a multidisciplinary team and the interfaces with other areas of an organisation.
Back to Duty
K19: Different methods of communication and choosing the appropriate one - e.g. face-to-face (synchronous, high bandwidth), instant messaging, email (asynchronous, low bandwidth), visualisations vs. words.
Back to Duty
K20: Pair/mob programming techniques and when to use each technique.
Back to Duty
K21: Architecture principles, common patterns and common strategies for translating user needs into both cloud infrastructure and application code.
Back to Duty
K22: How their occupation fits into the wider digital landscape and any current or future regulatory requirements.
Back to Duty
K23: The importance of continual improvement within a blameless culture.
Back to Duty
K24: The difference between Software-as-a-Service (SaaS) v bespoke v enterprise tooling and how to make an informed choice that suits each use case.
Back to Duty
K25: Maintain an awareness of cloud certification requirements.
Back to Duty
S1: Communicate credibly with technical and non-technical people at all levels, using a range of methods; e.g. ‘Show and Tell’ and ‘Demonstrations’.
Back to Duty
S2: Work within different organisational cultures with both internal and external parties
Back to Duty
S3: Translate user needs into deliverable tasks, writing clear, concise and unambiguous user stories that the whole team can understand.
Back to Duty
S4: Initiate and facilitate knowledge sharing and technical collaboration
Back to Duty
S5: Deploy immutable infrastructure
Back to Duty
S6: Install, manage and troubleshoot monitoring tools
Back to Duty
S7: Navigate and troubleshoot stateful distributed systems, in order to locate issues across the end-to-end service.
Back to Duty
S8: Work in agile, multi-disciplinary delivery teams, taking a flexible, collaborative and pragmatic approach to delivering tasks.
Back to Duty
S9: Application of a range of cloud security tools and techniques - e.g. threat modelling, vulnerability scanning, dependency checking, reducing attack surface area - incorporating these tools and techniques into the automated pipeline wherever possible.
Back to Duty
S10: Assess identified and potential security threats and take appropriate action based on likelihood v impact.
Back to Duty
S11: Employ a systematic approach to solving problems, using logic and hypotheses / experimentation to identify the source of issues.
Back to Duty
S12: Automate tasks where it introduces improvements to the efficiency of business processes and reduces waste, considering the effort and cost of automation.
Back to Duty
S13: Engage in productive pair/mob programming.
Back to Duty
S14: Write tests and follow Test Driven Development discipline in various different contexts.
Back to Duty
S15: Release automation and orchestration as part of a Continuous Integration workflow and Continuous Delivery pipeline, automating the delivery of code from source control to the end users.
Back to Duty
S16: Invest in continuous learning, both your own development and others, ensuring learning activities dovetail with changing job requirements. Keep up with cutting edge.
Back to Duty
S17: Code in a general purpose programming language.
Back to Duty
S18: Specify cloud infrastructure in an infrastructure-as-code domain-specific language.
Back to Duty
S19: Interpret logs and metrics data within the appropriate context to identify issues and make informed decisions.
Back to Duty
S20: Writing code in such a way that makes merging easier and facilitates branching by abstraction - i.e. feature toggling.
Back to Duty
S21: Application of lightweight modelling techniques, such as whiteboarding, in order to gain consensus as a team on evolving architecture.
Back to Duty
S22: Incremental refactoring by applying small behaviour-preserving code changes to evolve the architecture.
Back to Duty
B1: Exhibits enthusiasm, openness and an aptitude for working as part of a collaborative community; e.g. sharing best practice, pairing with team members, learning from others and engaging in peer review practices.
Back to Duty
B2: Invests time and effort in their own development, recognising that technology evolves at a rapid rate.
Back to Duty
B3: Displays a commitment to the mantra 'You build it, you run it', taking ownership of deployed code and being accountable for its continual improvement, learning from experience and taking collective responsibility when things fail.
Back to Duty
B4: Is inclusive, professional and maintains a blameless culture.
Back to Duty
4
24
| Version | Change detail | Earliest start date | Latest start date |
|---|---|---|---|
| 1.0 | Approved for delivery | 12/03/2020 | Not set |
Crown copyright © 2024. You may re-use this information (not including logos) free of charge in any format or medium, under the terms of the Open Government Licence. Visit www.nationalarchives.gov.uk/doc/open-government-licence