Contents
Part 1: A resume that gets read

Audit yourself before you apply

The mistakes almost everyone with this profile makes. Do this with a friend, because you won’t see your own gaps.

Resume

CheckWhy it matters
Every link opens from a logged-out browserA 404 on a project link reads as a fake project.
Nothing listed that you can’t build liveOne failed “show me” question sinks the whole resume.
TypeScript listed if your code is TypeScriptYou’re filtered out of searches you qualify for.
No date of birth, photo, or parents’ namesNot expected in tech resumes, and invites bias.
Summary names the role and one concrete projectThe generic version is on every other resume.
Single column, plain PDF, one pageParsers scramble everything else.
Spell-checked, official tech names“Univesity” or “React js” signals carelessness.

GitHub

CheckFix
READMEs are still the default create-next-app textWrite a real README for each flagship project: what it does, live link, demo logins, screenshots, architecture, data model, hard problems solved.
Only one project is deployedDeploy all flagships, with seeded demo accounts for every role. Recruiters won’t sign up.
AI tool files in the repo root (CLAUDE.md, AGENTS.md)Move them into /docs. Don’t hide AI use, but the first screen should show your work.
Commit messages like “day3” or “update”From now on, specific messages: “add order status filter to seller dashboard”. Don’t fake history.
Empty repos, tutorial clones, untouched forksArchive or make private. Show only work you’re proud of.
No bio, no location, nothing pinnedBio with your stack and city, pin your 3 best repos.

LinkedIn

  • Headline: “Full-Stack Developer | Next.js, TypeScript, PostgreSQL | Immediate joiner | Bengaluru”.
  • Featured section: your live apps. About section: what you built, not what you’re passionate about.
  • Open to Work, visible to recruiters only.

The “defend the code” test

Ask a friend or mentor to do this before you start interviewing:

  1. They open three random files in your main project. You explain each one without notes.
  2. They name a small feature (“add a status filter to this list”). You build it without AI in 90 minutes, explaining as you go.

Any project you can’t defend this way goes into daily practice before you put it in front of an interviewer.