Software Engineer
If you’ve ever wanted to build the thing instead of just using it, this is the one to try first — and in 2026 the job is shifting from typing every line to directing AI and judging whether what it hands back is any good.
Related:Founder·Product Manager·Data Analyst
Worth a look if you like making things that work and chasing down problems with no answer key. Maybe not if you want clear steps and a fast, certain right answer.
The work
What you’d actually do all day
Software engineers build the apps and websites people use every day — less typing code alone in the dark, more figuring out what to build and making sure it actually works. In 2026 more of the job is pointing AI tools at the problem and judging whether what they hand back is any good — the skill that lasts is knowing what “good” looks like and catching when something’s quietly broken.
- Writing new code40%
- Reading & reviewing code18%
- Debugging & testing22%
- Meetings & planning12%
- Writing & docs8%
Even on day one, writing brand-new code is under half the day — you spend more time reading, debugging, and testing what already exists.
Approximate, from labor-market research. Varies by company and role.
A typical early-career day
- 10:00Catch up & review
Skim messages, then read teammates’ code that’s waiting on you — is it correct, is it safe, is it fast?
- 10:30Team check-in
A quick ~15-minute standup: what you did, what you’re doing, what’s stuck.
- 11:00Focused build
Heads-down on your piece in short bursts — write it, get it working, send it over for a teammate to check.
- 1:00Debug & test
Hunt down why something’s broken and make sure it holds up. This is most days, not a bad one.
- 2:30Direct the AI
Point an AI tool at the next problem, let it draft, then check and fix what it gives back. You own the result.
A rough early-career day. As you get more senior, the hands-on coding shrinks and the reviewing, design, and meetings grow — see the mix above.
Would you actually like it?
In practice, here’s when people realize this is their thing, and when they realize it isn’t.
In practice, people realize it’s their thing when…
- they make something real that people actually use
- the stuck-stuck-stuck-then-it-works puzzle feels fun, not frustrating
- they like fast, honest feedback — it works or it doesn’t, and when you fix it, it’s fixed
- they don’t mind that it’s as much reading, reviewing, and directing AI as writing fresh code
…and it probably isn’t their thing when
- they need fast certainty and hate being stuck with no answer key
- they pictured building alone, heads-down all day — the real job is a lot of review, meetings, and directing AI
Start here
Vibe-Code a Working Web App
Pick one thing you wish existed, build it with an AI app builder, and ship it to a live URL. You’ll feel the real loop — decide, build, fix, ship — faster than any explainer can describe it, and real people can use what you make.
The numbers
The real money and market
BLS Occupational Outlook Handbook, software developers (SOC 15-1252), May 2024.
Where it’s going
The field is still growing fast — about 15% through 2034, much quicker than most jobs — but the job itself is changing. Instead of writing every line, new engineers now spend more time checking what AI wrote and making the judgment calls. Big companies like IBM, McKinsey, and Stripe are even ramping up junior hiring in 2026 around these new-style roles.
Right now
The early-career door is genuinely tighter than it was a few years ago — companies are leaning on AI for the simple starter tasks juniors used to learn on. That’s the current reality, and worth knowing going in.
Sources: BLS Occupational Outlook Handbook (SOC 15-1252); Stanford Digital Economy Lab / Brynjolfsson et al., 2025; Bloomberg/IBM, Feb 2026. Dated June 2026.
The only way to know is to try it.
Pick a project and see how it feels.
Or try one of these