Published occupation directory
Search specific job titles, aliases, work contexts, or fields. Every card opens a full occupation page and points to its career family and practical learning connections.
Browse visually
Families organize the directory without pretending that one broad pathway is a specific occupation. Choose any family to narrow the published list below.
Find a specific direction
Showing 73–96 of 142 published occupations · page 4 of 6
Information technology, data and cybersecurity
Full-stack developers work across both the interface and the services behind it, following a feature from the screen through to the database. The breadth is the point: it suits smaller teams where one person needs to carry a change end to end.
Information technology, data and cybersecurity
Mobile application developers build apps for phones and tablets. Alongside writing code they deal with the constraints of the platform: limited battery and memory, patchy connectivity, permission prompts, and app store review before anything ships.
Information technology, data and cybersecurity
Web developers build and maintain websites and web applications, from marketing sites to logged-in tools. The role often mixes coding with content management systems, hosting, and the practical work of keeping a live site healthy.
Information technology, data and cybersecurity
Game developers write the code that makes a game run, covering gameplay rules, graphics, physics, input, and audio. The work is highly collaborative, sitting between designers who decide how the game should feel and artists who supply what it looks like.
Information technology, data and cybersecurity
Test automation engineers write code whose job is to test other code. They build and maintain automated test suites and the pipelines that run them, so that a broken change is caught by a machine rather than by a user.
Information technology, data and cybersecurity
DevOps engineers build the machinery that gets code from a developer's machine into production safely. They automate builds, deployments, and infrastructure, and they are usually the people other teams come to when a release or environment misbehaves.
Information technology, data and cybersecurity
Site reliability engineers keep production systems running and treat reliability as an engineering problem rather than a manual chore. They set service level objectives, automate away repetitive operational work, and lead the response when something breaks. On-call rotations are a normal part of the role.
Information technology, data and cybersecurity
Cloud engineers design, build, and run systems hosted on cloud platforms. The job mixes networking, security, and automation: provisioning resources in code, controlling who can access what, and keeping an eye on how the environment is configured over time.
Information technology, data and cybersecurity
Solutions architects decide how a system should be put together to meet a business need, then explain that decision to both engineers and non-technical stakeholders. Much of the value is in the trade-offs: what to build, what to buy, and what constraints the design has to respect.
Information technology, data and cybersecurity
Systems administrators keep an organisation's servers, operating systems, and core services running. The work is a mix of planned maintenance and unplanned problem solving, and it often includes the accounts, backups, and permissions everyone else depends on.
Information technology, data and cybersecurity
Network administrators design, configure, and maintain the networks that connect an organisation's devices, sites, and services. When connectivity fails, they are the people who work out whether the problem is a cable, a configuration, or a provider.
Information technology, data and cybersecurity
Network technicians install, test, and repair the physical and logical parts of a network. Compared with an administrator the work is more hands-on and site-based: running and terminating cable, swapping hardware, and confirming links behave as expected.
Information technology, data and cybersecurity
IT support technicians are the first point of contact when someone's technology stops working. They diagnose hardware, software, account, and connectivity problems, fix what they can, and hand on what they cannot with enough detail for the next team.
Information technology, data and cybersecurity
Database administrators look after the systems where an organisation's data lives. They handle installation, access control, backup and recovery, and performance, and they are accountable when a query slows the business down or a restore is needed.
Information technology, data and cybersecurity
Data engineers build the plumbing that moves data from where it is created to where it is analysed. They write pipelines, model warehouse tables, and put checks in place so that analysts and models are working from data that is complete and on time.
Information technology, data and cybersecurity
Machine learning engineers take models out of notebooks and into production systems. The role sits between data science and software engineering: building training and serving pipelines, watching for drift once a model is live, and handling the failure modes that only appear at scale.
Information technology, data and cybersecurity
Penetration testers are paid to attack systems with permission, to find weaknesses before someone else does. Every engagement runs inside an agreed written scope, and the deliverable is a report that explains each finding, its impact, and how to fix it.
Information technology, data and cybersecurity
Embedded software developers write the code that runs inside physical products, from appliances and vehicles to medical and industrial equipment. Memory, power, and timing are tight, and testing usually means working with real hardware on a bench.
Manufacturing, production and quality
CNC programmers turn a part drawing or CAD model into the toolpaths and machine code that will cut it. They choose cutting strategies, tooling, and speeds and feeds, then simulate the program to catch collisions before it reaches the shop floor. The role sits between design and production and usually involves close work with machinists.
Manufacturing, production and quality
Production supervisors run a shift, line, or cell: allocating people, keeping the schedule moving, and dealing with whatever interrupts it. They sit between operators and plant management, so the job mixes hands-on troubleshooting with coaching, safety enforcement, and reporting. Most supervisors come up from the floor and keep detailed knowledge of the process.
Manufacturing, production and quality
Manufacturing technicians keep production equipment and processes running to specification, sitting between operators and engineering. They set up equipment, run trials, chase down faults, and implement small changes that improve yield or reliability. The work is diagnostic: much of it is figuring out why a process that worked yesterday is drifting today.
Manufacturing, production and quality
Process technicians run and monitor continuous or batch production processes, often from a control panel or system as well as at the equipment itself. They watch temperatures, pressures, flows, and yields, make controlled adjustments, and respond when a process alarms. The role carries real safety weight because process upsets can escalate quickly.
Manufacturing, production and quality
Production planners decide what gets made, on which line, in what order, and with which materials. They balance customer demand against capacity, material availability, and changeover cost, then re-plan whenever a machine goes down or a delivery slips. The work is analytical but highly interruptible, since the plan rarely survives contact with the shop floor unchanged.
Manufacturing, production and quality
Industrial maintenance technicians keep production machinery working, covering planned servicing as well as breakdown repair. The work spans mechanical, hydraulic, pneumatic, and often electrical and control systems, so diagnosis is a core skill. Breakdown work can be pressured, because the line is usually stopped while the fault is found.
Need a guided route?
