Career guide

What's actually inside a tech company

Most people picture a tech company as a room full of programmers. It isn't. A product reaches you because 17 different teams each did a different job - and plenty of them never write a line of code.Here is every one of them: what they do on an ordinary Tuesday, which ones will hire you with no experience, and what to learn for each.

Look up a job title
17
teams in a normal company
10
that hire people with no experience
5
where you never write code
217
job titles explained below

Start here: how one feature travels through a company

Every job below exists because the work has stages. Read this once, top to bottom, and the rest of the page stops looking like an arbitrary list of titles.

  1. 1

    Someone asks for it

    Should we build this at all?

    A customer complains, a rival ships something, or a metric dips. Product and leadership pick what is worth doing next - and, mostly, what is not.

    Who does this:
  2. 2

    It gets drawn

    What should it look like and feel like?

    Before any code, someone sketches the screens and the wrong turns a user might take. Changing a drawing costs minutes; changing shipped software costs weeks.

    Who does this:
  3. 3

    It gets built

    How do we actually make it work?

    Frontend builds what you touch, backend builds the part that stores and calculates, mobile builds the phone version. They agree on how the pieces talk to each other.

    Who does this:
  4. 4

    Someone tries to break it

    What did we get wrong?

    QA hunts for the case nobody thought about. Security asks how an attacker would abuse it. Both are cheaper before release than after.

    Who does this:
  5. 5

    It goes live

    How does it reach real users safely?

    Platform engineers move the code onto servers, usually to a few percent of users first, with a way to undo it in one click if the graphs turn red.

    Who does this:
  6. 6

    It has to keep working

    Is it still up at 3am?

    Something will break at an inconvenient hour. Someone is on call, gets woken by an alert, and fixes it. This never stops - which is why it is a permanent job.

    Who does this:
  7. 7

    People find out and get help

    Does anyone know it exists, and can they use it?

    Marketing explains it, sales sells it, support answers the person who is stuck. Their notes become the complaint that starts the next loop.

    Who does this:

The teams

Open as many as you like - they stay open so you can compare two side by side.

Showing 17 of 17 teams

Heard a title you don't recognise?

Titles in tech are not standardised. The same job is a “Software Engineer” here, an “SDE” there and a “Developer” somewhere else - while two different jobs both shorten to TPM. Look one up.

217 titles and 131 other names for them.

About the pay bands: Bands compare roles with each other, not with a payslip. Actual pay swings by a factor of five or more between countries and company sizes, and a senior engineer at a large firm can out-earn a director at a small one.

Product Management

Design & User Experience

Frontend Engineering

Backend Engineering

Mobile Engineering

Data & Analytics

AI & Machine Learning

Quality & Testing

Platform, DevOps & Reliability

Security

IT & Internal Systems

Customer Support & Success

Marketing

Sales

People & Recruiting

Finance & Legal

Leadership (the C-Suite)

How to read a title you've never seen

Almost every title is three slots filled in. Once you can see the slots, an unfamiliar title stops being a new job and becomes a combination you already know.

1

Level

How much scope you are trusted with. No word at all usually means mid-level - the default.

InternJuniorAssociate(none)SeniorStaffPrincipalLeadHead ofDirectorVPChief
2

Area

Which part of the work. Often missing, in which case the team you join decides it.

FrontendBackendMobileDataSecurityPlatformMLQA
3

Craft

The kind of work. This is the part that rarely lies.

EngineerDeveloperAnalystDesignerManagerArchitectScientist
Senior Backend Engineer
Senior · Backend · Engineer - experienced, server-side, writes code.
SDE II
Amazon's ladder. SDE = Software Development Engineer; II = mid-level. Same job as 'Software Engineer'.
Staff ML Engineer
Staff (very senior, still hands-on) · Machine Learning · Engineer.
Head of Design
Head of (runs the function) · Design · - a manager, not a designer who draws all day.

Levels are company-specific. Google's L5, Amazon's SDE III and Meta's E5 are roughly the same seniority as a plain "Senior Engineer" elsewhere. Never assume a number means the same thing at two companies.

Titles people mix up

These sound interchangeable and are not. Getting them the wrong way round is the most common way to apply for a job you did not mean to.

Data Analyst, Data Scientist, Data Engineer, Analytics Engineer?

Data Analyst
Answers questions with existing data. SQL and dashboards. The most common way in.
Analytics Engineer
Builds the clean, trusted tables the analysts query. Sits between engineer and analyst.
Data Engineer
Builds the pipelines that move data into the warehouse. Mostly software engineering.
Data Scientist
Uses statistics and models to predict or explain, not just report. Heavier maths.

DevOps, SRE, Platform Engineer, SysAdmin?

SysAdmin
The older title. Keeps servers and internal systems running, often by hand.
DevOps Engineer
Automates build, test and release so developers can ship themselves.
SRE
Site Reliability Engineer. Treats uptime as an engineering problem, with error budgets and on-call.
Platform Engineer
Builds the internal tooling other engineers deploy onto. Their customer is the dev team.

Product Manager, Project Manager, Program Manager, Product Owner?

Product Manager
Decides what gets built and why. Owns the outcome.
Product Owner
A Scrum role: keeps the backlog ordered. At many companies the same person as the PM.
Project Manager
Owns dates, scope and dependencies for one project. Cares that it lands on time.
Program Manager
Coordinates several related projects across teams. TPgM if it is technical.

Software Engineer, Developer, Programmer, SDE?

Software Engineer
The standard title. SWE.
SDE
Software Development Engineer. Amazon's name for exactly the same job.
Developer
Same job. More common in Europe, agencies and smaller firms.
Programmer
Same job, older word. Rare in job ads now, common in conversation.

UI Designer, UX Designer, Product Designer, UX Engineer?

UI Designer
How it looks: layout, colour, type, the visual system.
UX Designer
How it works: flows, structure, what happens when the user goes wrong.
Product Designer
Both of the above, plus a say in what gets built. The most common modern title.
UX Engineer
Writes the front-end code for the design system. An engineer, not a designer.

QA Engineer, Tester, SDET, Automation Engineer?

Manual Tester
Uses the product deliberately trying to break it. No code required.
QA Engineer
Owns quality for a product area - plans what to test and why.
Automation Engineer
Writes scripts that re-run the tests on every change.
SDET
Software Development Engineer in Test. A full software engineer whose product is the test system.

Software Architect, Solutions Architect, Solutions Engineer?

Software Architect
Designs how the internal system is structured. Internal-facing.
Solutions Architect
Designs how the product fits a specific customer's setup. Often pre-sales, often cloud.
Solutions Engineer
Sits in sales calls and proves the product works. Also called Sales Engineer or pre-sales.

Security Analyst, Security Engineer, Penetration Tester?

Security Analyst
Watches alerts and investigates them. Usually in a SOC. The usual way in.
Security Engineer
Builds the defences - access control, scanning, hardening.
Penetration Tester
Attacks the company's own systems on purpose and writes up what worked.
GRC Analyst
Governance, Risk and Compliance. Proves to auditors the controls exist. Little to no code.

Technical Writer, Content Writer, UX Writer?

Technical Writer
Writes the documentation developers read. Needs to understand the product deeply.
Content Writer
Writes marketing material - blog posts, landing pages, case studies.
UX Writer
Writes the words inside the product: buttons, errors, empty states. Sits with design.

Staff Engineer or Engineering Manager - which is the promotion?

Senior Engineer
The point where the ladder forks. Most companies stop expecting you to climb further.
Staff / Principal Engineer
The technical track. More scope, still hands-on, no direct reports. Pays like management.
Engineering Manager
The management track. A different job - people, priorities and hiring, little coding.

And then there's seniority

Every team above has the same ladder running through it. It is one idea, not a hundred job titles: the work stays similar, but the size of the decision you are trusted with grows.

  1. Intern / Trainee

    0 yrs

    Given a well-defined task and someone to ask.

    Step 1
  2. Junior

    0–2 yrs

    Does tickets that are already broken down. Expected to ask questions constantly.

    Step 2
  3. Mid-level

    2–5 yrs

    Takes a feature and delivers it without supervision.

    Step 3
  4. Senior

    5+ yrs

    Owns a system, makes design decisions, and grows the people around them.

    Step 4
  5. Staff / Principal

    8+ yrs

    Solves problems that cross several teams. Still hands-on - this is the alternative to managing.

    Step 5
  6. Manager

    A different job, not a promotion from senior: the work becomes people and priorities.

    Step 6
  7. Director / VP

    Runs a whole function through other managers. Rarely writes code.

    Step 7
  8. C-level

    15+ yrs

    Accountable for the entire company to the board.

    Step 8

Worth knowing early: becoming a manager is a change of job, not a reward for being a good engineer. Most companies have a parallel track - Staff, Principal - that pays the same and stays hands-on.

Found one that sounds like you?

Pick the team, then take the courses attached to it. If you would rather be told the order to do things in, the learning paths lay it out week by week.