Who Does What: Roles in a Tech Team

When you join a tech company, you will hear the same role names every day. Knowing exactly what each one owns helps you introduce yourself clearly and direct your questions to the right person. This lesson covers the roles used inside companies like Stripe, Google, and Shopify, and the English patterns for talking about them.

The core roles

Most modern software teams are built around three core roles, supported by a few specialists.

| Role | What they own | Common title | | ------------------------ | --------------------------------------------------------- | ----------------------------- | | Software Engineer | Writing and reviewing code, fixing bugs, technical design | Engineer, Developer, SWE | | Product Manager (PM) | The roadmap, priorities, and what gets built next | PM, Product Lead | | Designer | How the product looks, feels, and works for users | Product Designer, UX Designer |

You will also meet DevOps or Site Reliability Engineers (SREs), who keep services running and deployments smooth, and Data Scientists or Analysts, who measure what is happening with the numbers.

How to introduce yourself

The clearest pattern is my role is [title] on the [team] or I work as a [title].

• My role is software engineer on the payments team.
• I work as a product manager on the growth team.
• I'm a product designer at a SaaS company.

Avoid the common transfer error I am working as engineer. The present continuous (am working) describes a temporary action, and the article a is missing. For a permanent role, use the present simple: I work as a software engineer.

Engineer, developer, or programmer?

These words overlap, but there is a register difference in tech culture.

• Software Engineer is the most common professional title. Companies like Google and Stripe use it in job postings.
• Developer is slightly more casual and common in job descriptions at smaller companies.
• Programmer sounds dated. Native speakers rarely use it as a job title today.

When in doubt, use software engineer. It is the safest and most professional choice.

Lead versus manager

These two words confuse many learners because both describe senior people.

• A Lead (Tech Lead, Design Lead) guides the work and the technical direction, but may not manage people or run performance reviews.
• A Manager (Engineering Manager, Design Manager) owns the people: hiring, promotions, one-on-ones, and performance.

So a Tech Lead decides how to build a feature, while an Engineering Manager decides who builds it and how they grow.

Practice

Rewrite each introduction in clear professional English:

1. I am working as PM in the company.
2. He is lead of my team, but no manager.
3. She do the design for our app.

Possible answers:

1. I work as a product manager. (or: My role is product manager.)
2. He is the tech lead on my team, but he doesn't manage people.
3. She is the product designer for our app.

Interactive drills

When you can name every role confidently, your standups, introductions, and LinkedIn profile all sound more professional. In the next lesson, you will learn the vocabulary of the tools and workflows these roles use every day.