A Quick Look at What a Software Engineer Does
Desk-bound, team-bound and meeting-heavy: here is how one shift actually splits between writing code, fixing old code and talking to other people.
By Harlan Voss · Oct 06, 2026 · 5 min read
Software engineering is sedentary, full-time and collaborative. Most of the occupation works full time (U.S. Bureau of Labor Statistics, 2026-08-27), 90% of surveyed workers report a 40-hour typical week (O*NET OnLine, 2026), and the day is split between writing and changing code, testing it, documenting it, and conferring with other people about what it needs to do.
This snapshot covers the hours, the work setting, the tasks that fill a single shift, and a short fit check you can answer about yourself. Hours, remote or on-site policy, and on-call expectations vary by employer and by state, so check the job posting itself before you assume.
At a Glance
| Item | What to expect |
|---|---|
| Typical hours | 90% of surveyed workers report a typical work week of 40 hours (O*NET OnLine, 2026); most in the occupation work full time (U.S. Bureau of Labor Statistics, 2026-08-27) |
| Work setting | Desk-based and team-based — 71% of surveyed workers call contributing to a work group or team 'extremely important' (O*NET OnLine, 2026) |
| Physical demand | Low lifting, high sitting: 95% of surveyed workers report sitting 'continually or almost continually' (O*NET OnLine, 2026) |
| People contact | 35% of surveyed workers report 'constant contact with others' (O*NET OnLine, 2026) |
| Entry requirement | A bachelor's degree in computer and information technology or a related field such as engineering or mathematics; some employers prefer a master's (U.S. Bureau of Labor Statistics, 2026-08-27) |
| Competition | 40% of surveyed workers describe the level of competition in the job as 'highly competitive' (O*NET OnLine, 2026) |
What a Typical Day Looks Like
You sit down at 8:45 a.m., read overnight messages and pull the latest branch from version control (Git on most teams). At 9:30 a.m. there is a short team stand-up, because developing software is usually a collaborative process and you work alongside others who design, develop and program the same product (U.S. Bureau of Labor Statistics, 2026-08-27). From 9:45 a.m. to 11:30 a.m. you modify existing software to correct errors, adapt it to new hardware or improve performance (ONET OnLine, 2026) — in practice, reproducing a reported bug, writing a failing test, then making it pass. At 11:30 a.m. you confer with systems analysts and engineers to obtain information on project limitations and performance requirements (ONET OnLine, 2026) for a feature starting next sprint. Lunch at 12:30 p.m., usually away from the keyboard, since 95% of surveyed workers sit continually or almost continually (O*NET OnLine, 2026). At 1:15 p.m. you review a colleague's pull request and leave comments. From 2:00 p.m. you design a piece of the application and plan how it fits with the pieces around it (U.S. Bureau of Labor Statistics, 2026-08-27), sketching a diagram for the programmers who will build it. At 4:15 p.m. you document what you changed as a reference for future maintenance and upgrades. You push your branch and log off at 5:30 p.m.
Daily Tasks You'll Actually Do
- Reproduce a reported bug, then modify the existing code to correct it (O*NET OnLine, 2026).
- Write and run tests as part of software testing or validation procedures (O*NET OnLine, 2026).
- Review a teammate's pull request in version control and leave written comments.
- Sit in a stand-up or planning call with analysts, engineers and programmers to pin down project limitations and performance requirements (O*NET OnLine, 2026).
- Analyze a user need and judge whether the design is feasible within time and cost constraints (O*NET OnLine, 2026).
- Sketch a model or diagram showing other programmers the code an application needs (U.S. Bureau of Labor Statistics, 2026-08-27).
- Write documentation for the change you shipped so the next person can maintain or upgrade it (U.S. Bureau of Labor Statistics, 2026-08-27).
- Recommend a software upgrade for an existing program or system (U.S. Bureau of Labor Statistics, 2026-08-27).
Quick Fit Check
- Can you sit at a desk for most of an eight-hour day? 95% of surveyed workers sit continually or almost continually (O*NET OnLine, 2026).
- Are you willing to spend part of each day in meetings and calls with analysts, engineers and other programmers rather than alone with the code?
- Do you accept having your work read and commented on in a pull request review, and doing the same to others' work?
- Are you comfortable spending hours on someone else's old code — correcting errors and upgrading interfaces — not only building new features?
- Will you write documentation after the code works, as a reference for future maintenance?
- Can you complete a bachelor's degree in computer and information technology or a related field such as engineering or mathematics, which is the typical entry-level education (U.S. Bureau of Labor Statistics, 2026-08-27)?
Frequently asked questions
Is "software engineer" a different job from "software developer"?
Both appear in the sample of reported job titles for the same occupation (O*NET OnLine, 2026). Which title an employer uses, and what seniority it implies, varies by company rather than by any national standard.
How much of the day is writing brand-new code?
Less than people expect. Modifying existing software to correct errors, adapt it to new hardware or improve performance is a listed task for the occupation (O*NET OnLine, 2026), and recommending upgrades to customers' existing programs and systems is another (U.S. Bureau of Labor Statistics, 2026-08-27).
Sources
- U.S. Bureau of Labor Statistics — Software Developers, Quality Assurance Analysts, and Testers (2026-08-27)
- O*NET OnLine — 15-1252.00 - Software Developers (2026)
Written by
Harlan Voss
Harlan covers the business of job-seeking itself — the coaches, platforms, and advice industries that have grown up around finding work. He writes with a skeptic's patience and a soft spot for anyone still trying.
