A roster list is only useful if it tells you what each pick is for, so that is what this does.
Short answer
Learn two: one that is forgiving and one that fits how you already want to play. Breadth comes later.
- Check the patch date on any ranking you are reading.
- Learn one forgiving option properly before adding a second.
- Check the version you are actually running before assuming anything is broken.
Siege rewards knowing the building more than knowing the gun, which is why map knowledge outranks aim here. Tier lists describe a skill bracket, and most of them do not say which one. Balance passes usually move numbers rather than reworking a kit, so the character still plays the same way.
Why tier lists disagree
Screenshots age faster than text, which is why this describes rather than shows. Role coverage inside a team matters more than the individual rating of any one pick. The strongest pick in professional play is often the worst pick in a solo queue. A single check up front replaces a lot of guessing later.
New additions are typically overtuned at release and corrected within two patches. A difficult pick with a high ceiling is worse than an easy one until you have put the hours in. If your result differs from what is described here, note what is different first rather than starting over.
Good places to start
Every roster has one entry that is quietly excellent and permanently unpopular. Rainbow Six Siege is not shy about hiding useful information two menus deep, so some of this is simply knowing where to look. Patch notes move numbers around constantly; the shape of the answer holds even when a specific value shifts.
- Expect a new release to be nerfed within a month.
- Watch one match of the pick before committing time to it.
- Prefer the in-game option over an external tool when both exist.
- Pick a role before picking a character.
The picks that punish beginners
Half the pages on this topic were written for a build that no longer exists, which is why they stop matching what you see. Most of the disagreement you will find online is two people describing different builds. None of this needs a paid tool, a third-party launcher or an account on a site you have never heard of. Where two approaches both work, the one with fewer moving parts is the one to keep.
Do the cheap check before the expensive one — that ordering alone saves most of the frustration. The awkward part is rarely the step itself, it is knowing which step comes first. There is usually a fast way and a reliable way, and it is worth knowing which one you are choosing.
How the roster breaks down
Where something depends on your platform or region, that is called out rather than glossed over. The developers have changed their mind about this at least once, which explains the older advice. What follows assumes you are on a current install and have not modified it.
Everything below is framed around the current state of Rainbow Six Siege rather than a launch-week impression. There is no hidden trick here that the game is keeping from you. It helps to understand why a step exists, because then you can adapt it when your situation is slightly different.
What changes between patches
The short version is near the top on purpose; the reasoning is there if you want to know why. If you are coming to this after a long break, the terminology has probably moved on. Treat anything stated without a version number as provisional.
Where people go wrong
- Treating a rare edge case as the normal behaviour and planning around it.
- Downloading a helper tool for something the game already does in its own menu.
- Rushing the last step, which is usually the one with the actual requirement in it.
- Skipping the prerequisite because it looked optional in someone else's summary.
Siege FAQ
Does this work the same on console and PC?
The logic is identical. Menu paths and button prompts differ, and any real difference is flagged above.
Is the newest addition overpowered?
Usually at release, briefly. Balance passes have corrected almost every launch outlier so far.
How long does this take?
Minutes if it goes cleanly, an evening if you hit the edge case in the caveats list. Neither is unusual.
What if none of this works for me?
Then something in your setup differs from the assumption — version, region or platform. Check those three before anything else.
If you only take one thing from this: the answer near the top is the part that matters, the rest is context.