system-design

Part 14 — Company Guides

The framework and case studies are universal, but how you’re interviewed varies enormously by company. A services company in Lahore, a super-app in Dubai, and Google in Mountain View want different things. This part helps you target your preparation — and covers the two things pure design prep ignores: the behavioral round and actually landing the interview.

Time for this part: read company tiers early to shape your whole plan, then read the region/tier chapter for your targets. Come back to behavioral and getting the interview throughout your search.

The unifying idea: prepare for the companies you’re actually targeting, not a generic “FAANG” abstraction. The right prep for a services company is the wrong prep for a scale-up, and vice versa.

Chapters

Read the landscape

# Chapter What it gives you
1 Company Tiers ⭐ The map: who tests what, how to weight your prep

Your region / target

# Chapter For targeting…
2 Pakistan & South Asia Systems Ltd, Tkxel, Arbisoft, Educative, GICs, Indian product cos
3 MENA & SEA Scale-Ups Careem, Noon, Talabat, Tabby, Grab, Gojek, Shopee
4 Big Tech Google, Meta, Amazon, Microsoft
5 Startups vs Enterprises The culture/stage axis, cutting across tiers

The parts design prep forgets

# Chapter Why it matters
6 The Behavioral Round ⭐ Decides more offers than you think (esp. Amazon LPs)
7 Getting the Interview ⭐ All the skill is useless if you never get in the room

The things to remember

  1. Target your prep to the tier. Services/local → weight LLD, fundamentals, practical design. Scale-ups → their domain’s case studies. Big Tech → the full formal treatment. Don’t prepare generically.
  2. LLD is underrated regionally. In Pakistan/South Asia (and at Amazon), object-oriented design is often more tested than billion-user HLD. Prepare it deliberately.
  3. Match the company’s domain. A Careem interviewer loves a candidate fluent in ride-matching; a Noon interviewer, e-commerce. Go deep on your target’s core system.
  4. Startups want simplicity; enterprises want rigor. Same question, different emphasis — read the room and don’t over-engineer at a startup.
  5. Behavioral decides offers. STAR stories, “I” not “we”, own your failures. For Amazon, map stories to the 16 Leadership Principles — it’s often the decisive round.
  6. Getting the interview is a separate skill. Referrals beat cold applications; projects beat an empty resume; persistence beats the brutal funnel. For fresh grads, build 2–3 real projects.
  7. Target realistically, then level up. Land at a reachable company, build experience, and the next tier opens. The first job is the hardest; each one after is easier.

Before moving on

Next: Part 15 — Resources — the reading list, engineering blogs, foundational papers, tools, and cheat sheets to keep learning long after the interview.

This site is open source. Improve this page.