ZEIRO
A day in the life

Software Engineer

Software Engineers build and maintain the systems a product actually runs on.

TechnologyTypically 9:30–6, with on-call rotations at most companies$110k–$150k to start
A Software Engineer at work

Don't just read it — play it

Clock in at 9am and make the calls a Software Engineer makes all day. Six decisions, real consequences, a score at 5pm.

Play this day

What this role really is

Software Engineers turn requirements into working systems and keep them running. The job is far more reading, designing and debugging than typing. You'll spend real time in code review, in design docs, and in production logs figuring out why something broke. Feedback loops are fast and objective: it works or it doesn't.

  • Design and ship features
  • Debug production issues under pressure
  • Review other engineers' code
  • Improve reliability and performance
  • Turn requirements into working systems

What it pays

Entry level
$110k–$150k
Mid career
$160k–$210k
Senior
$250k+

Typically 9:30–6, with on-call rotations at most companies

Majors that get you here

Computer ScienceComputer EngineeringSoftware EngineeringMathPhysics

Entry roles: SWE Intern · New Grad Engineer · Platform Engineer

Your 9-to-5, hour by hour

A realistic ordinary day — not the highlight reel.

  1. 9:30 AM

    Standup and code review

    You start by reviewing two teammates' pull requests, leaving comments on edge cases, then give a 60-second update in standup.

  2. 10:00 AM

    Deep work block

    Headphones on. You implement the piece of the feature you designed yesterday, writing tests alongside it and running things locally.

  3. 12:30 PM

    Lunch and reading

    You eat with the team, then skim a design doc from another team that touches your service and leave one comment about a failure case.

  4. 1:30 PM

    A bug from production

    An alert fires. You read logs, reproduce the issue, find a null check that was never there, ship a fix behind a flag and watch the dashboard recover.

  5. 3:30 PM

    Design discussion

    Forty-five minutes at a whiteboard with a senior engineer arguing about whether to queue the work or process it inline. You leave with a plan and tradeoffs written down.

  6. 5:00 PM

    Push and wrap

    You open your pull request, respond to review comments, update the ticket and note where to pick up tomorrow.

Great for you if

  • You like problems with a clear right answer eventually
  • You enjoy long stretches of focused, uninterrupted work
  • You're stubborn about figuring out why something broke

Probably not for you if

  • You want your day to be mostly people and persuasion
  • You dislike sitting with a problem for hours

Skills that matter

Problem solvingSystems thinkingDebuggingCollaboration

Similar days worth reading