"Software developer" isn't one job — it's a whole family of different day-to-day work. Here's what ten common CS/IT roles actually involve: the tasks you'd do most days, a real example scenario, the tools you'd touch, and 2024 median U.S. pay (BLS).
The biggest CS job category by far — about 1.7 million people in the U.S. hold this title. Day to day, it's rarely "build a whole app" — it's small, scoped pieces of a much bigger system.
| What you'd actually do |
|---|
| Build app features, fix bugs, write backend APIs, write database queries, add login/payment/search features, write tests, review teammates' code, document how systems work. |
You make sure the developers' code actually works before real users touch it — and that a new feature didn't quietly break an old one.
| What you'd actually do |
|---|
| Write test plans, manually test websites/apps, automate repetitive tests, find and report bugs with clear repro steps, re-test old features after new changes ship ("regression testing"). |
Less "build the app," more "figure out what the data is actually saying" — and explain it to people who don't code.
| What you'd actually do |
|---|
| Clean messy spreadsheets/databases, write SQL and Python scripts, build dashboards and charts, train simple prediction models, find patterns, present findings to managers in plain English. |
You're the one watching for the break-in — and cleaning up if one happens.
| What you'd actually do |
|---|
| Monitor security alerts, investigate suspicious logins, scan systems for vulnerabilities, help patch them, manage firewalls/encryption, write incident reports, check compliance rules. |
You keep the databases that everything else depends on fast, backed up, and secure.
| What you'd actually do |
|---|
| Write and optimize SQL queries, back up databases, fix slow-running reports, manage who has access to what data, monitor performance, migrate data between old and new systems. |
Servers, accounts, backups, and the network itself — the stuff that has to just keep working.
| What you'd actually do |
|---|
| Monitor servers and networks, create user accounts, apply security patches, manage permissions, troubleshoot outages, check backups, set up VPN/remote access. |
Half tech, half translator — you turn "what a department actually needs" into something developers can build.
| What you'd actually do |
|---|
| Interview staff about pain points, write technical requirements, draw process diagrams, test software changes before rollout, act as the bridge between users and developers. |
The most common first job in tech — and a real stepping stone, not a dead end.
| What you'd actually do |
|---|
| Answer support tickets, reset passwords, install software, troubleshoot Wi-Fi/VPN/printers, set up new employees' laptops, document how you solved each issue. |
If a job involves maps and real-world location data, this is the role — very common in government and public-service agencies.
| What you'd actually do |
|---|
| Work with map/location datasets, clean location data, build interactive map dashboards, write Python scripts for geospatial analysis, maintain map databases. |
Someone has to keep a multi-month system rollout from falling apart — that's this job.
| What you'd actually do |
|---|
| Track deadlines and budgets, schedule meetings between developers/analysts/agency staff, update project plans, flag risks early, report progress to leadership. |
Salary figures: U.S. Bureau of Labor Statistics, May 2024 Occupational Employment and Wage Statistics. Actual pay varies a lot by location, employer, and experience.