Could I be a Software Developer?

What it is really like

Most of your day involves writing code, testing it, and fixing it when it breaks. You'll sit with an editor and a terminal open, translating requirements into actual instructions the computer understands. A lot of time gets spent reading other people's code, trying to understand what it does and why, then modifying it or building on top of it. It's absorbing work that demands focus, and many developers find the flow state of solving a concrete problem genuinely satisfying.

The harder texture comes from the fact that software rarely works first time, and hunting down why is tedious. You'll spend hours tracing through code trying to find a single line causing a problem. You also have to keep learning constantly because tools, languages and frameworks change, and what you knew five years ago may no longer be relevant. Meetings and discussions about design decisions can feel like they take time away from actual building, though getting them right upfront saves grief later.

Working with others is unavoidable. You'll review code written by teammates, explain your choices, and defend your decisions. You may inherit projects in poor shape, or discover mid-way through that the requirement you were given doesn't match what the business actually needs. The gap between what sounds simple in a meeting and what's actually possible to build reveals itself constantly, and you have to communicate that clearly without frustration.

What you would actually be doing

• You're asked to add a new feature by end of week, so you write the code, run tests, push it, and your tests pass but a user finds a case you didn't think of, so you debug and patch it.
• Two teams both need you to fix a bug in shared code, but fixing it one way breaks their system and fixing it the other way breaks the first, so you have to talk to both and decide on a solution that doesn't fully satisfy anyone.
• A developer on your team submits code for review that technically works but is written in a way you think will be hard to maintain, so you leave comments suggesting changes and they push back because they're under time pressure.

Want to feel what it is actually like?

Step into a few real situations from this role, then get an honest, behaviour-based read on how you approached the work. No score, no pass or fail.

Your first exploration is free and takes about 15 minutes. No signup needed to start.

More in the Career Library

• How Do You Know If You'd Be Good at Software Engineering?
• How Do You Know If You'd Be Good at a Career You've Never Tried?