In this chapter
We'll decode job titles — common IT roles, developer vs. engineer, and what junior and senior really mean — so a title tells you something real about the work.
The Problem in Real Life
Back at her desk, Anna looks at her badge: Associate Software Engineer. John's says Senior Software Engineer. Another colleague calls herself a developer, and the job board she used last month listed "SDE-1," "Engineer II" and "Lead Developer" for what looked like the same work.
Is an associate the same as a junior? And is a developer different from an engineer?
Anna
The Title on the Badge vs. the Work Behind It
Every company names things differently
The same job can be called associate, junior, SDE-1 or Engineer I depending on the company.
Seniority isn't years
"Senior" sounds like age or experience — but it's really about the size of problems you can own.
What Job Titles and Seniority Really Mean
"Titles are messy," John says. "Every company invents its own. So learn what they usually mean, and then always look at the actual work."
- Common IT roles you'll see in job posts: software developer or engineer, frontend, backend or full-stack developer, QA engineer, DevOps engineer, data analyst, data engineer, support engineer, system administrator.
- Developer vs. engineer: in daily use, most companies use them for the same job. When there's a difference, "engineer" stresses designing systems and making trade-offs, while "developer" stresses building features. Don't choose a job by this word alone.
- Junior (often "associate," "Engineer I" or "SDE-1"): works on well-defined tasks with guidance, and learns the codebase and the team's ways of working.
- Mid-level: owns features end to end with little help.
- Senior: owns large, unclear problems, makes design decisions, prevents problems before they happen, and helps others grow — exactly what John is doing for Anna right now.
| Level | How they handle "add group discounts" |
|---|---|
| Junior | Builds the discount from a clear spec, asks questions, gets the code reviewed |
| Mid-level | Designs and builds the feature end to end, including tests and edge cases |
| Senior | Asks whether discounts break other pricing rules, plans it with product, and coaches the junior building it |
"The jump from junior to senior isn't about typing faster," John says. "It's about how big and how unclear a problem you can take and still deliver."
Key Takeaway
A title is a label each company invents. Seniority really means the size and uncertainty of the problems you can own — and how much you help the people around you.
Why This Matters
Reading job posts, setting your own growth goals and understanding who to ask for help all depend on reading titles correctly. Anna's first year at BlueTicket is really a year of growing from "well-defined tasks" towards owning real problems.
Anna knows the roles and the levels now. What she still can't picture is how all these people actually work together to get one feature from an idea into customers' hands. John has a perfect example: the seat-selection feature.