In this chapter
We'll walk through the engineering roles in a real tech team — software, DevOps, cloud, data, AI/ML, QA, security, databases, systems, networks and support — and what each one is responsible for.
The Problem in Real Life
After lunch, John says, "Grab your notebook. We're taking a walk." He means through the office — fifteen desks, and almost every one does something different.
Anna expected a room full of people writing code. Instead, one person is watching graphs of server health, one is reading a list of suspicious login attempts, one is testing the checkout on four different phones, and one is answering a customer whose QR code won't scan.
Writing code is one job here. Keeping it running, safe and useful is about ten more.
John
"Everyone Codes" vs. Who Actually Does What
Too many titles
DevOps, data engineer, QA, security — the titles blur together until you see what each person actually does.
Every role touches the same product
All these jobs exist to keep one thing working: a fan buying a ticket and getting into the show.
The Engineering Roles in a Tech Team
John stops at each desk and explains the role in one sentence — always by what that person protects or delivers for the ticket buyer.
- Software engineer: designs and writes the code for features — the seat map, the checkout, the email confirmation.
- DevOps engineer: builds the path from code to running software, and keeps it running — deployments, servers, monitoring.
- Cloud engineer: sets up and manages the rented computers, storage and networks the app runs on.
- Data engineer: moves and organises data so it can be analysed — like collecting every sale into one reporting system.
- Data scientist: finds answers in that data — which shows sell out, when prices should change.
- AI/ML engineer: builds features that learn from data — like recommending shows a fan might like.
- QA (quality assurance) engineer: tests the product to find problems before customers do.
- Cybersecurity engineer: protects accounts, payments and data from attackers.
- Database administrator (DBA): keeps databases fast, backed up and correct.
- System administrator: manages servers, operating systems and internal computer systems.
- Network engineer: designs and maintains the networks that connect computers.
- Technical support: helps users when something doesn't work, and reports real bugs to the team.
| Problem | Role that handles it first |
|---|---|
| Checkout button does nothing | Software engineer |
| Website is down for everyone | DevOps / cloud engineer |
| New release breaks on one phone | QA engineer |
| Strange logins from another country | Cybersecurity engineer |
| Sales report shows wrong totals | Data engineer |
| Customer's QR code won't scan | Technical support |
At a startup like BlueTicket, one person often covers two or three of these roles. At an enterprise, each one may be a whole team. The work is the same; only the number of people changes.
Key Takeaway
A software product needs far more than code. Every engineering role exists to protect one part of the user's experience — building it, running it, testing it, securing it, or helping when it fails.
Why This Matters
Knowing who owns what is how real problems get fixed fast. Later this year, when something breaks at 10:00 AM on Sale Day, Anna will need to know exactly which part of the system — and which person — to look at first.
Anna's notebook now has twelve roles and one sentence for each. But one word keeps coming up in every introduction — "senior" — and her own badge says "Associate." What do those words actually mean? That's next.