Software Engineer
You build the apps, sites, and tools other people use every day. In 2026 more of the first draft comes from the tools, so the part that’s really yours is steering them and judging whether what they hand back is any good.
Related: Founder, Product Manager, Data Analyst
The day in the life
club-signup · draft
export default function App() {
// TODO: the one thing it does
return <main>Club shifts</main>
}an empty shell, waiting on your call
Riley wants all of this. What does your app actually do this afternoon?
Try a day as a software engineer
A short, playful taste of the real work.
There will be lots of these jobs for years to come, but the ones a beginner can get are the hardest to find right now.
Degree helps, but isn’t required.
BLS Occupational Outlook Handbook, software developers (SOC 15-1252), May 2024.
What you’d actually do
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.
More and more of the job is steering the tools that draft the code, then 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 new code is under half the day. Most of your time goes on reading what is already there, testing it, and hunting down what is broken.
Approximate, from labor-market research. Varies by company and role.
“Software engineer” covers wildly different jobs depending on what you build.
- Frontendbuilding the part users actually click, the buttons and layouts on screen.
- Backendbuilding the servers and databases behind the scenes that make everything work.
- Mobilebuilding apps meant to live on a phone, not a browser tab.
- Infrastructurebuilding the systems that keep every other engineer’s code running without falling over.
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:30Steer the next piece
Point your tools at the next problem, let them draft, then check and fix what comes 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.
The outlook
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 the drafts 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.
Would you actually like it?
Worth a look if you like making things that work and chasing down problems with no answer key.
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 reading and checking what other people wrote takes up as much of the day as writing anything new
…and it probably isn’t their thing when
- they need fast certainty and hate being stuck with no answer key
- they pictured working alone all day with their head down, and really it is a lot of checking other people’s work, meetings, and telling the AI what to do next
Ship Your First Web App
Pick one thing you wish existed, build it with an AI tool that writes the code for you, and put it online so your friends can open it and use it. You do the whole thing once, deciding, building, fixing and sharing, faster than any explainer can describe it.
Or try one of these