Building software & products

Computer Science

Making the apps, websites and systems people use every day.

What the work actually is

What the work is actually like

Less typing than people imagine. A working day is reading existing code to understand why it does what it does, a couple of hours of actual writing, reviewing colleagues' changes, and meetings deciding what is worth building at all. A large share of the job is maintaining and changing software that already exists and that someone else wrote, often years ago.

The catch

The knowledge decays: tools and frameworks you are expert in today are legacy in six years, so you are signing up to keep learning for the whole career. The work is also sedentary and screen-bound, remote roles can be isolating, and entry-level hiring is now genuinely competitive — 'learn to code and get hired' was true a decade ago and is a weaker promise today.

What people get wrong about it

That it is a solitary job for people who like machines more than people. Past the first year or two, the constraint on your work is almost always communication — explaining a trade-off, disagreeing well in a review, understanding what the person asking actually needs.

The jobs inside this area

Software engineer
Frontend / backend developer
Mobile developer
DevOps / platform engineer
QA engineer
Product manager

A list, not a recommendation — you narrow it, we don’t.

What this kind of work usually offers

Earning well · Making things · IndependenceA generalisation about the sphere, not a promise about a salary. Pay and security vary enormously by country and employer.

How you get there

The one-line version

A CS degree or self-taught — either works if you ship projects. The one thing that matters: write a lot of code.

Stage by stage

While you are still at school
Write code weekly, on things you personally want to exist. One finished, used, deployed small project teaches more than ten tutorials, and it is also the only evidence anyone can look at.
What you study
A CS degree gives you the durable half — algorithms, systems, networks, how a computer actually works — which is the part that does not go stale. Self-teaching genuinely works in this field, but it puts the burden of that foundation on you, and visa routes to work abroad usually assume a degree.
How the first years actually go
You join a team and spend months reading its codebase before you meaningfully change it. First tasks are small bug fixes and tests, deliberately: they are how you learn the system and how the team learns to trust you.

Test it this month

Free, and finishable in a few evenings

Build one small thing you will actually use, put it online, and give the link to someone. The distance between 'it works on my machine' and 'a stranger used it' is where the profession lives.