Who Is Who: Roles in an IT Team
Sandra, an HR specialist, explains who works in an IT team, which business stakeholders bring requirements, and what HR does.
Getting to know the company
Hi! Welcome to the company 👋 I’m Sandra, an HR specialist. I run the onboarding for everyone new.
What’s your name? I’ll set up your pass and your access.
Hi! My name is .
Great, , your pass will be ready by lunch!
While we wait, let me tell you who’s who. A tester works with almost everyone, so it’s important to know who to go to with which question.
Sure! Who is in my team?
You’re joining a product IT team. It usually has these roles:
- Team lead — leads the team: assigns tasks, helps people grow and removes blockers. Your team lead is Alex, who is in charge of the testers.
- Developer — writes the code: the frontend is what the user sees, the backend is the server and the database.
- Designer (UX/UI) — decides how the product looks and how to make it easy to use. The designer’s mockups are requirements too: you can test against them.
- Product manager (PM) — decides what the team builds and why: collects wishes, writes requirements and sets priorities.
- Tester (QA) — that’s you! Checks that the product works as intended, finds defects and writes bug reports.
- Analyst — not every team has one. Digs into the business problem and turns it into detailed requirements.
What exactly does a designer do?
A designer thinks about the user. They study how people use the product, draw the screens and turn them into a clickable prototype — usually in Figma. That way, before any code, you can see where the buttons are, what happens after a click and what the error messages will say.
This matters for you: a mockup is a requirement too. If a button on the site is a different colour, a text gets cut off, or a screen on a phone doesn’t look like the mockup — that’s a defect. And if something in the mockup is inconvenient or unclear, tell the designer: they’ll be glad to hear it.
Got it! Isn’t an analyst the same as a PM?
Close, but no. The PM decides what to do and in what order. The analyst describes in detail how it should work: fields, rules, limits. If the team has no analyst, the PM writes the requirements.
My tip: if something in the requirements is unclear, don’t guess — ask the PM or the analyst. A question asked in time is a bug found before the code is even written.
Got it. And who is there besides the team?
There are also business stakeholders — people from other departments who care about what the team delivers. They don’t write code, but they often bring requirements:
- Sales — talk to customers and know what they need. They bring requests for new features and customer complaints.
- Compliance — make sure the product follows the industry rules: for example, requirements for payments or data protection.
- Legal — take care of the legal side: terms of use, consent to process personal data (GDPR), contract texts.
Why does a tester need to know about legal and compliance?
Because their requirements are requirements too! If a payment form is missing the mandatory “I agree to the terms” checkbox, it’s a defect, even if everything else works. Mistakes like that can cost the company big fines.
I see. And what does HR do?
We in HR take care of people: hiring, onboarding, training and development, feedback and the atmosphere in the company.
Here’s what you can always come to me with:
- Holidays — how to book them, when to apply and how many days you have left.
- Sick leave — if you get ill, let your team lead and me know, and I’ll tell you which documents you need.
- Health insurance — what it covers, how to sign up and who to contact.
- The best coffee in the area — I know every café around the office and I’m happy to share ☕
Thanks! Are there other teams in the company?
Of course! We have five teams, and they’re set up in a similar way: a team lead, developers, a designer, a PM and testers. You’ll meet them a bit later.
There’ll be plenty of chances. We often have all hands — a meeting of the whole company where we share news and plans, and teams show what they’ve done. And in summer we have Summer Days — a big summer celebration for everyone in the company. Don’t miss it!
Great! Thanks, Sandra, now I know who to go to.
One last thing, and the most important one. Kadri is your main mentor — you’ll meet her soon. Listen to her carefully: that way you’ll settle in faster, pass your probation period and handle all your tasks successfully.
And don’t be shy about asking questions — Kadri really loves it!
Nice to meet you, ! You can pick up your pass at reception. Now go and see Alex, your team lead: he’s waiting for you and will explain how the internship works. Good luck 🍀
Quick reference
The IT team
The team lead leads the team and helps people grow. Developers write the code, the designer owns the look and usability, the product manager (PM) owns what the team builds and why. The tester checks that the product works as intended. Some teams also have an analyst who writes detailed requirements.
Business stakeholders
People from other departments who care about the result: sales bring customer requests, compliance makes sure the product follows the industry rules, legal takes care of the legal side, such as consent to process data (GDPR).
HR
Takes care of people: hiring, onboarding, holidays, training and development, feedback. You can come to HR with a question about your contract or for advice.
What it means for a tester
Requirements don’t come only from the PM: the designer’s mockups and the rules from compliance and legal are requirements too. If something is unclear, ask the PM or the analyst before you start testing.