Not every company interviews the same way. A 30-person startup in Lahore, a scale-up in Dubai, and Google want different things and interview differently. This chapter maps the landscape so you can target your preparation instead of preparing generically — because the right prep for one tier is the wrong prep for another.
Prerequisites: Interview Formats Time to read: ~12 minutes
🚨 The same “system design interview” means different things at different companies. A startup may ask you to design a feature you’d actually build next week; Big Tech asks you to design Twitter and grades a formal rubric; a services company may barely do system design at all and focus on LLD. Preparing without knowing the tier wastes effort — you might over-prepare distributed consensus for a company that wants clean OOP, or under-prepare scale for one that lives and dies by it.
This part has a chapter per region/tier. This chapter gives the mental model they all build on.
flowchart TB
T1[Tier 1 — Local / Services<br/>Tkxel, Systems Ltd, Arbisoft, Netsol]
T2[Tier 2 — Product / Scale-ups<br/>Careem, Talabat, Noon, Tabby, Grab, Educative]
T3[Tier 3 — Big Tech<br/>Google, Meta, Amazon, Microsoft]
T1 -->|more scale, more rigor| T2 -->|more scale, more rigor| T3
(Pakistan/South Asia examples: Tkxel, Systems Ltd, Arbisoft, Netsol, 10Pearls, Devsinc.)
(MENA/SEA examples: Careem, Talabat, Noon, Tabby, Grab, Gojek, Delivery Hero; also Educative, Motive.)
(Google, Meta, Amazon, Microsoft, and similar.)
🚨 These tiers are a rough guide, not a caste system — a “Tier 1” company may have a world-class team, and titles/scale vary. Use them to target prep, not to rank companies or yourself.
| Dimension | Tier 1 (local/services) | Tier 2 (product/scale-up) | Tier 3 (Big Tech) |
|---|---|---|---|
| Scale in questions | App-level, practical | Real product scale (millions) | Planetary (billions) |
| System design weight | Light–moderate; often LLD | Significant, product-flavored | Heavy, formal rubric |
| Coding bar | Solid | High | Very high (DS&A) |
| Distributed systems depth | Low–moderate | Moderate–high | High |
| LLD/OOP | Common, important | Sometimes | Amazon yes; others less |
| Behavioral rigor | Moderate | Moderate–high | High (esp. Amazon LPs) |
| Process length | Shorter (1–3 rounds) | Moderate | Long (4–6+ rounds) |
🚨 The through-line: as you move up tiers, scale and formality increase. Lower tiers reward practical, buildable competence; higher tiers reward reasoning about scale and trade-offs against a rubric.
🚨 The good news: this guide covers all tiers, so preparing thoroughly here prepares you for any of them — but targeting lets you allocate limited time well.
If you’re starting out with no experience, 🚨 Tier 1 and some Tier 2 companies are your realistic entry points, and they lean on fundamentals, coding, and LLD more than deep scale — which is learnable from scratch (that’s what this guide is for). Land a role, build real experience, and Tier 2/3 open up. Don’t let “I can’t design Google yet” stop you from acing the interviews you can actually get now. See getting the interview.
1. List your targets by tier. Write down 5–10 companies you’d realistically apply to and tag each with a tier. This becomes your prep-weighting guide.
2. Match prep to the mix. If most of your targets are Tier 1, put LLD and fundamentals first; if Tier 2, prioritize their domain case studies. Adjust your study plan accordingly.
3. Research one company’s process. Pick one target and find its actual interview process (Glassdoor, LeetCode discuss, blogs). Knowing the rounds ahead of time removes surprise.