The whole site in one number
0 of 0 IT roles need no code at all.
You were told IT means programming. It does not. Below is every major role in the industry, laid out by whether the job asks you to write code. Open one and read what the work actually involves — including the parts nobody advertises.
The map
Every role, four levels deep
Start at the centre. Open a branch, then a domain, then a role. One branch stays open at a time so the map never turns into a knot. Keyboard works throughout — arrow keys move, Enter opens, Escape closes. Open a branch, then a domain, then a role. Tap any role to read what that job actually involves, including the parts nobody advertises.
Drag to pan · scroll to zoom · click a node to open it
Where the work happens
Coding is one stage out of seven
This is how software actually gets made, start to finish. Follow the row of roles underneath each stage — six of the seven stages are full of people who never open a code editor.
Effort against reward
How hard to enter, how long it takes
All 47 roles plotted. Left and low is the easiest corner to start from. Click any marker to read the full role.
Role finder
Three questions, then a shortlist
Answer honestly. A flattering answer gives you a role you will not enjoy.
Question 1 of 3
Last thing
Pick one. Not five.
The mistake is not choosing wrong. The mistake is choosing four roles at once, studying a bit of each, and being hireable for none of them after a year.
Take the one role that made you sit up while you were reading. Give it ninety days of real work — the tools, one project you can show, and a conversation with someone already doing it. If it still fits after ninety days, keep going. If it does not, come back to the map. You will have lost three months and learned something true about yourself.
— Kavis Network
Go back to the map