Placement Checklist
A practical 20-point checklist to get your profile, skills, stories and job search ready before you start applying.
Whether you are a fresher, switching jobs or getting back on your feet after a layoff, most rejections come from gaps you can close in a few focused weeks: a weak resume, no visible proof of work, rusty problem solving or stories you have never said out loud.
Work through one group at a time and tick items only when they are genuinely done. You do not need everything perfect before applying; once the first two groups are solid, start applying while you finish the rest.
Profile & resume
The first 10 seconds a recruiter spends on you.
1One-page ATS-friendly resumeResume
A single-column, one-page resume in a plain font that applicant tracking systems can parse. Each bullet should show impact with a number, not just list duties.
- Skip tables, photos, icons and text boxes; export as a text-based PDF.
- Mirror keywords from the job description honestly.
- Bullet formula: action verb + what you did + measurable result.
Reduced p95 API latency from 820 ms to 190 ms by adding Redis caching and batching DB calls, cutting infra cost by 18%. Sections: Contact | Summary (2 lines) | Experience | Projects | Skills | Education
2Updated LinkedIn profileProfile
Recruiters search LinkedIn before they read resumes. Make sure your headline, About section and experience match your resume and say what role you want next.
- Headline: role + stack + focus, e.g. "Backend Engineer | Java, Spring, AWS".
- Turn on Open to Work (recruiters-only if you prefer privacy).
- Add your projects and a professional photo; ask two colleagues for recommendations.
Proof of work
Show, don't just tell.
32 deployed projectsProjects
Two projects that are live on a public URL beat ten tutorial clones on your laptop. Pick problems you can explain deeply, ideally close to the roles you want.
- Include auth, a real database and at least one non-trivial feature.
- Free tiers on Render, Vercel, Railway or Fly.io are enough.
- Put the live link and the repo link on your resume.
4Clean GitHub READMEsProjects
A README is your project's landing page. A reviewer should understand what it does, see it working and know how to run it in under a minute.
- Add a screenshot or GIF and the live link at the top.
- Pin your best repos on your GitHub profile.
- Remove secrets and dead code before sharing.
# Project name - one-line pitch Live: <url> | Demo GIF ## Features ## Tech stack & architecture (diagram) ## Run locally ## What I learned / next steps
5System design of your own projectDesign
Be ready to draw your project's architecture and defend each choice: data model, APIs, caching, scaling and what would break first at 100x traffic.
- Know your trade-offs: why this database, why this queue, why not something else.
- Prepare one thing you would redesign today and why.
- Practise on a whiteboard or in Excalidraw.
Problem solving & core
The technical bar every round checks.
6250+ DSA problems, pattern-wiseDSA
Solve problems grouped by pattern (sliding window, two pointers, BFS/DFS, DP...) rather than at random. Pattern recognition is what lets you crack unseen questions.
- Mix of roughly 40% easy, 50% medium, 10% hard.
- Revisit problems you failed after 3 and 7 days.
- Say your approach and complexity out loud before coding.
710 timed online assessmentsOA
Online assessments are a different skill from untimed practice: reading fast, handling edge cases and managing a clock. Simulate the real thing at least ten times.
- Typical format: 2-3 problems in 60-90 minutes.
- Grab partial points with a brute force first, then optimise.
- Practise on HackerRank and CodeSignal-style platforms you will actually face.
8Aptitude practiceAptitude
Many companies, especially service firms and campus drives, filter with quantitative, logical and verbal aptitude tests. A few weeks of steady practice is usually enough.
- Focus on percentages, ratios, time-speed-distance, probability and puzzles.
- Do 20 timed questions a day and review every mistake.
9One programming language learned properlyLanguage
Go deep in one language rather than shallow in four. You should know its collections, memory model, common pitfalls and standard library without searching.
- Java: HashMap internals, equals/hashCode, streams, threads.
- Python: list/dict complexity, generators, GIL basics.
- Use the same language for every interview round.
10Core CS notes (OS, DBMS, CN, OOP)Core CS
Keep short revision notes for the four subjects interviewers love. Aim to explain each concept in two or three sentences with an example.
- OS: processes vs threads, deadlock, paging, scheduling.
- DBMS: normalisation, indexing, transactions and ACID, isolation levels.
- CN: TCP vs UDP, what happens when you type a URL, HTTP/HTTPS. OOP: the four pillars, SOLID.
1150 SQL queries practisedSQL
SQL shows up in OAs, backend rounds and data roles. Practise joins, grouping, subqueries and window functions until they feel routine.
- Classic asks: Nth highest salary, duplicates, running totals, top N per group.
- Know the difference between WHERE and HAVING, and between RANK and DENSE_RANK.
Communication & stories
Most offers are won or lost on how you explain things.
12"Tell me about yourself" in 60 secondsIntro
Your opening answer sets the tone for the whole interview. Keep it to about 60 seconds: present, past, the one achievement that matters, and why this role.
- Do not recite your resume line by line.
- If you were laid off, one calm, factual line is enough, then move forward.
Present: I'm a <role> with <N> years in <domain/stack>. Past: At <company> I <biggest relevant achievement + number>. Skill: I'm strongest at <2 skills that match the JD>. Now: I'm looking for <type of role> and <company> excites me because <reason>.
132-minute project walkthroughProjects
Be able to explain your best project in two minutes: the problem, your design, the hardest challenge and the outcome. Expect deep follow-up questions on anything you mention.
- Lead with the problem and the user, not the tech stack.
- Own your part clearly: say "I", not just "we".
- Record yourself once and trim the filler.
145 STAR storiesBehavioural
Prepare five real stories you can adapt to most behavioural questions: a conflict, a failure, leadership, a tight deadline and going beyond your role.
- Spend most of the time on Action, and end with a measurable Result.
- Keep each story to about 2 minutes.
Situation: context in 1-2 lines (team, project, stakes) Task: what you were responsible for Action: 3-4 concrete steps YOU took Result: outcome with a number + what you learned
153 mock interviewsPractice
Do at least three mocks with a friend, mentor or peer platform before real interviews. Thinking aloud under observation feels very different from solo practice.
- Cover one DSA, one system design or project, and one behavioural round.
- Ask for blunt feedback and fix one thing before the next mock.
Job search engine
Treat applying like a system, not a lottery.
16Referrals from 20 seniors or ex-colleaguesReferrals
Referrals get far more callbacks than cold applications. Reach out to 20 people with a short, specific message and make it easy for them to help.
- Share the job ID or link, your resume and a 2-line summary of fit.
- Former colleagues and managers are your strongest network after a layoff.
- Follow up once after a week, politely.
Hi <name>, hope you're well! I'm applying for <role> (Job ID <id>) at <company>. I have <N> yrs in <stack> and recently <one achievement>. Would you be open to referring me? Resume attached. Thanks a lot!
17Job application trackerTracker
A simple spreadsheet stops applications slipping through the cracks and shows which channels actually get you interviews.
- Update it the same day you apply or hear back.
- Review weekly: low response rate usually means the resume needs work.
Company | Role | Link | Source (referral/portal) | Date applied | Status (applied/OA/interview/offer/rejected) | Next step & date | Contact | Notes
18Check careers pages dailyRoutine
Early applicants are more likely to be seen. Keep a list of target companies and check their careers pages and job alerts every day.
- Set alerts on LinkedIn and company portals for your role and location.
- Budget 30 focused minutes a day instead of endless scrolling.
Interview day
Finish strong and handle the money talk.
192 smart questions for the interviewerQuestions
"Do you have any questions?" is part of the evaluation. Ask two thoughtful questions that show curiosity about the team and the work.
- Good: "What does success look like in the first 90 days?"
- Good: "What is the biggest technical challenge the team faces this year?"
- Avoid asking about leave or perks in early rounds.
20A prepared expected-CTC answerSalary
Research the market range for the role and city before the call, then give a confident, reasoned range instead of a guess. Practise saying it out loud.
- Use levels.fyi, Glassdoor, AmbitionBox and peers to benchmark.
- Give a range whose bottom you would still be happy with.
- If asked about current CTC after a gap, be honest and steer to market value.
"Based on my research for <role> in <city> and my experience with <skills>, I'm looking for a range of <X> to <Y>. I'm flexible on structure and most interested in the role and growth here."
Quick tips
- Start applying once your resume and projects are ready; keep preparing in parallel.
- Rejections are data, not verdicts. Note why, adjust one thing and keep going.
- Protect a daily routine: a few problems, a little revision and some outreach every day.
- After a layoff, lean on your network early; most people genuinely want to help.
- Look after sleep and health; a rested mind solves problems faster in interviews.
Topic list based on the free Everything You Need to Get Placed checklist by Mohammad Fraz. Explanations and examples are original.