Networks and cybersecurity is the WEF's second fastest growing skill area to 2030, and AI engineering headlines LinkedIn's 2026 list. The builders' cluster.
21
Cybersecurity fundamentals
What it is: The everyday behaviours and basic concepts that protect accounts, devices and data: authentication, phishing awareness, updates and least privilege.
Why now: Phishing, ransomware and supply chain attacks now reach every team, so baseline security behaviour is everyone's job, not just IT's.
Build it: Work through the NCSC's free staff training resources, then switch on a password manager and multi factor authentication everywhere.
Level 3 looks like: You use a password manager and multi factor authentication everywhere, spot and report phishing attempts reliably, and never need chasing on security basics.
22
Cloud platforms
What it is: Working knowledge of the major cloud providers, their core services, and the cost and architecture choices they involve.
Why now: Most new systems are born in AWS, Azure or Google Cloud, and cloud cost and architecture choices shape what teams can build.
Build it: Each provider runs free fundamentals training and an entry certification: AWS Cloud Practitioner, Azure Fundamentals or Google Cloud Digital Leader.
Level 3 looks like: You hold or could pass an entry cloud certification, navigate your organisation's cloud console confidently, and can explain a workload's cost drivers.
23
Modern software development
What it is: Building and shipping software using current languages, frameworks and engineering practice, from version control to testing.
Why now: Software remains the highest leverage way to scale a process, and Coursera's 2026 report puts software and product development among its three in demand career areas.
Build it: freeCodeCamp and The Odin Project are free and project based. Ship one small real tool, not ten tutorials.
Level 3 looks like: You ship small working tools end to end: coded, tested, versioned and documented well enough that another developer could pick them up cold.
24
AI assisted development
What it is: Using AI pair programmers to write code faster while keeping human review, testing and judgement firmly in charge.
Why now: Tools like GitHub Copilot, Cursor and Claude have changed how code gets written. The skill is steering, reviewing and testing what they produce.
Build it: Use an AI pair programmer on a real project for a fortnight, and review every suggestion before accepting it. The discipline is the skill.
Level 3 looks like: You use an AI assistant on real projects daily, review every suggestion before accepting, and your merged code holds the same quality bar as hand written work.
25
DevOps and platform engineering
What it is: Automating how software is built, tested and released, using pipelines, containers and infrastructure as code.
Why now: Shipping safely and often is a competitive weapon, and automating build, test and deploy is what makes it routine.
Build it: Learn Git, CI/CD and containers through the free GitHub Skills courses and Docker's getting started guide, then automate one deployment.
Level 3 looks like: You maintain a CI/CD pipeline that deploys without drama, can containerise an application, and recover a failed release calmly using the runbook.
26
APIs and systems integration
What it is: Connecting systems through their interfaces so data flows automatically instead of through copy and paste.
Why now: Modern stacks are assembled, not built from scratch, and the people who connect systems quietly become indispensable.
Build it: Learn REST basics with Postman's free academy, then connect two tools your team already pays for and remove one manual handoff.
Level 3 looks like: You can read API documentation cold, build a working integration between two real systems, and have removed at least one manual handoff this year.
27
Low code and no code building
What it is: Assembling working internal tools, apps and automations on platforms such as Power Apps or Airtable without conventional coding.
Why now: Power Apps, Airtable and similar platforms let operations people ship internal tools in days, easing the developer bottleneck.
Build it: Rebuild one spreadsheet driven process as a simple app with Power Apps or Airtable, and add one automation to it.
Level 3 looks like: You have replaced a spreadsheet driven process with a working app that others use daily, including at least one automation, and you maintain it yourself.
28
Version control and collaboration
What it is: Using Git based workflows of branches, commits and reviews to change shared work safely and traceably.
Why now: Git underpins how modern teams change anything safely, increasingly including documents, data and infrastructure, not just code.
Build it: GitHub's free Skills courses cover branching, pull requests and review. Practise by versioning something you actually maintain.
Level 3 looks like: You branch, commit, raise and review pull requests correctly without guidance, and your commit history tells a story a stranger could follow.
29
Privacy and data protection practice
What it is: Applying UK GDPR principles in daily work: lawful basis, minimisation, retention and individual rights.
Why now: UK GDPR obligations and customer expectations keep rising, and privacy by design is far cheaper than retrofitting it after a breach.
Build it: Study the ICO's free guidance and checklists, then run a data audit on one process: what you hold, why, and for how long.
Level 3 looks like: You can run a basic data audit on a process you own, answer what is held, why and for how long, and you spot a privacy risk before anyone has to point it out.
30
Networks and infrastructure
What it is: How devices, networks and servers connect and fail: IP, DNS, wifi, VPNs and the basics of keeping things up.
Why now: Hybrid work, cloud and connected devices all stand on networking, which is half of the WEF's second fastest rising skill area.
Build it: Cisco's free Networking Essentials or CompTIA Network+ materials cover the foundations. Then map your own team's setup and where it could fail.
Level 3 looks like: You can map your team's network setup, diagnose common connectivity faults methodically, and explain where the single points of failure sit.