system-design

Getting the Interview

All the design skill in the world is useless if you never get in the room. For many people — especially fresh grads and career-changers — getting the interview is the hardest part. This chapter covers resume, projects, networking, and applications: how to actually land the interviews you’ve been preparing for.

Prerequisites: none — but pair with Build-It Projects Time to read: ~13 minutes

The uncomfortable reality

🚨 Preparation gets you through interviews; getting them is a separate skill most people neglect. You can be interview-ready and still get zero callbacks if your resume doesn’t pass the filter, you have no projects to show, and you only apply cold through portals. This chapter fixes that. It’s especially critical for fresh grads with no work history — you have to manufacture signal.

The resume

Recruiters spend seconds per resume. Make yours pass the filter:

One page (early career), clean, scannable. No walls of text.
Lead with impact, quantified. “Built X that did Y, reducing Z by N%” beats “responsible for X.” Numbers catch the eye.
Projects front and center if you lack experience — 🚨 this is where fresh grads win (below).
Relevant skills/tech clearly listed; match keywords to the job (many resumes are ATS-filtered).
No fluff, no lies. Every line should earn its place; be ready to discuss anything on it.
Tailor per role — at least the top section/keywords to the specific job.

🚨 For no-experience candidates: projects, internships, open-source, coursework, hackathons, and freelance work all count as “experience.” Present them as such with impact and tech.

Projects — your biggest lever with no experience

🚨 For fresh grads, a few strong projects are the single highest-leverage thing you can build (literally — see build-it projects):

They prove you can build, which a degree alone doesn’t.
They give concrete interview material (“I built a distributed rate limiter, here’s the trade-off I hit”) — directly feeding your design and behavioral rounds.
They stand out on a resume with no jobs.
Quality over quantity: two or three real, non-trivial, finished projects (deployed, on GitHub, with a README explaining the design) beat ten half-done tutorials.

Great candidates: a small version of a system from this repo (URL shortener, chat app, a mini message queue), an app that solves a real problem, or a meaningful open-source contribution. Write a short blog post or README explaining the design and trade-offs — it doubles as portfolio and interview rehearsal.

Networking — the highest-conversion channel

🚨 Referrals convert far better than cold applications — a referred resume is many times more likely to get a callback. Networking isn’t sleazy; it’s how hiring actually works.

Referrals: reach out to people at target companies (alumni, ex-colleagues, LinkedIn connections, people you meet at meetups) — politely ask about their team and whether they’d refer you. A warm intro beats the portal every time.
LinkedIn: a complete, keyword-rich profile; connect with engineers and recruiters in your target companies/region; engage genuinely (comment, share, ask thoughtful questions).
Communities: tech meetups, Discord/Slack groups, university networks, open-source communities, Twitter/X tech circles. Regionally, local dev communities (Pakistan/MENA/SEA tech groups) are active and full of referral opportunities.
Recruiters: build relationships with tech recruiters; they want to place you. Respond, stay in touch.

🚨 The ask is simple and low-pressure: “Hi, I’m interested in [team/company]; could you tell me about your experience there / would you be open to referring me if it’s a fit?” Most engineers are happy to help.

Applying effectively

Apply early — many roles fill fast; early applications get seen.
Target, don’t spray — a tailored application to a well-chosen role beats 100 generic ones (though volume has its place; balance both).
Use multiple channels — referrals (best), company career pages, recruiters, LinkedIn, job boards, and the region’s job communities.
Follow up — a polite follow-up after applying (especially with a referral) keeps you visible.
Track everything — a spreadsheet of applications, contacts, statuses, follow-up dates.

Online presence

GitHub: pin your best projects with good READMEs; green-ish activity signals you actually code.
LinkedIn: complete, professional, keyword-optimized; a clear headline.
A simple portfolio/blog (optional but strong): a page with your projects and a few write-ups on what you built and learned. 🚨 Technical blogging is a huge differentiator with no experience — it shows communication and depth.

The mindset (especially for fresh grads)

🚨 Rejection is the norm, not a verdict on you. Strong candidates get rejected constantly — response rates are low, most applications go unanswered, and that’s the game, not a personal failing. Play the numbers, improve each cycle, and persist. It only takes one yes.

And remember the tiers: target companies you can realistically land now (local/ services/startups for fresh grads), get in, build experience, and level up. The first job is the hardest to get; each one after is easier.

🚨 Common pitfalls

Only applying cold through portals — neglecting referrals, the highest-conversion channel.
No projects — for no-experience candidates, this is fatal; build 2–3 real ones.
A generic, unquantified resume — no impact, no numbers, not tailored.
Weak/empty online presence — no GitHub, incomplete LinkedIn.
Giving up early — the funnel is brutal; persistence and volume matter.
Only targeting Big Tech — apply to the tiers you can realistically get, then level up.

🛠️ Try it

1. Rewrite your resume with impact. Turn every “responsible for X” into “did X, achieving Y (N%).” Get it to one clean page. Put projects up top if you lack experience.

2. Ship and pin two projects. Build two real projects (start with a build-it project), deploy them, write READMEs explaining the design, and pin them on GitHub. Write one blog post about a trade-off you hit.

3. Ask for three referrals this month. Identify three people at target companies (alumni, LinkedIn, meetups) and send a polite, specific message asking about their team and a possible referral. Track responses.