Career areas
Five crafts, one team
Engineering, design, data, delivery and advisory. Every client team mixes them, and each is treated as a craft worth getting good at.
See open roles
We do not split thinking from doing. The people who advise a client on what to build sit beside the people who build it, and the people who build it stay to run it. Whatever your area, you will see your work through.
A typical team has three or four engineers, a designer, someone from data and a delivery lead, with an advisory partner close by.
Titles are short and levels are published. What changes as you grow is the size of the problem you are trusted with.
The areas
What each area does on a client team
Engineering
Platform, backend, frontend, security, integration and quality engineers. You write production code, review it, test it and run it, and you are expected to have an opinion about how it should be built.
Our engineers work across modernization, cloud platforms and product builds, and many spend time on KIASA Canopy, keeping client platforms running.
Engineering rolesDesign
Product designers, service designers, researchers and accessibility specialists. You talk to the people who will use what we build, and you stay in the team while it is built, not just until the handoff.
Design rolesData
Data engineers, analytics engineers, data scientists and machine learning engineers. You build data platforms people trust, and put models to work only where the numbers say they help.
Data rolesDelivery
Delivery leads, engagement managers and delivery managers. You keep the plan honest, the client informed and the team free to work. You know the code well enough to ask good questions about it.
Delivery rolesAdvisory
Strategists, architects and due diligence specialists. You help clients decide what to build, in what order and at what cost, and you stay accountable for that advice once the building starts.
Advisory roles
How teams form
Mixed teams, from the first week
Each project starts with a team of five or six drawn from several areas. The designer hears the engineering trade-offs; the engineers hear what the research found. Nobody throws work over a wall, because there is no wall.
Teams are formed in the studio, so you will usually know your colleagues before the project starts.
Changing course
Moving between areas is normal
Some of our best data engineers started as backend engineers. Some of our delivery leads started as designers. If you want to move, tell your career coach. We will find you a project where you can try the new work with support around you.
About one in ten of our people change area in a given year.
Learning and growthThe areas, by the numbers
- 5
- career areas, each with published levels and pay bands.
- 1 in 10
- of our people move to a different area each year.
- 6
- people on a typical team, drawn from at least three areas.
KIASA internal records, 2025. Sample figures.
“I joined as a backend engineer and spent two years being curious about why our pipelines kept breaking. Now I lead the data work for the same client. Nobody made me apply for anything. I said what I wanted, and the next project gave me room to try it.”
Find your area, then find your role
Open roles in all five areas, across our studios.