Placement Preparation — Practice Projects
Placement prep isn't a coding skill — it's a process, and the "projects" here are structured practice cycles for that process, not software builds. Each one is designed to produce a measurable artifact you can review and improve on, the same way you'd review code.
Project 1: Resume Build-and-Audit Exercise (Beginner)
Time: 2-3 days
Build a real, one-page, ATS-optimized resume following this course's Overview guidance, then audit it against a concrete checklist rather than just "does it look nice."
Steps
1.Draft a one-page resume: contact, education, skills, 2-3 projects (in STAR format — situation/task, action, measurable result), internships if any, achievements
2.Pick a real job description (any relevant listing) and check keyword alignment — does your resume use the same terms the JD uses for your actual skills?
3.Audit every project bullet: does it state a measurable result, or just describe what was built? ("Built full-stack e-commerce app" → does it say what scale, what stack, what specific improvement?)
4.Check the skills section against the "don't list" guidance — no soft skills like "good communication," no irrelevant tools
5.Get one outside review (a peer, a senior student, a mentor) and revise based on specific feedback, not just your own read
What This Produces
•A real, usable, ATS-checked resume — not a practice artifact you throw away
•A documented before/after showing what specifically improved and why
Artifact Name
resume-audit-v1 (keep versions as you iterate — the improvement trail is itself useful to look back on)
Project 2: Timed Aptitude/Reasoning Practice-Test Cycle (Intermediate)
Time: 2-3 weeks (ongoing cycle, not a single session)
Run a structured, repeatable practice cycle for the aptitude round specifically — take a timed mock test, score it by section, identify weak topics, drill them, then retest — tracking real improvement across cycles rather than one-off practice.
Steps
1.Take one full timed mock aptitude test matching the real format (60-90 min, quantitative + logical reasoning + verbal sections)
2.Score it by section, not just overall — identify your 2-3 weakest specific topics (e.g., not just "quant" but specifically "time-speed-distance problems")
3.Drill those specific weak topics with focused practice sets for several days
4.Retake a fresh mock test (not the same one) and compare section-by-section scores against the first attempt
5.Repeat the cycle at least 3 times, and keep a log: date, overall score, section breakdown, and what you drilled in between
What This Produces
•A documented score-improvement trend across multiple cycles, not just a single test result
•A clear, evidence-based picture of your actual weak areas — not a guess
Artifact Name
aptitude-practice-log
Project 3: Structured Mock-Interview Log — Technical and HR (Advanced)
Time: 2-3 weeks (ongoing)
Run and record at least 3 mock interviews — at minimum one technical/DSA round and one HR round — each followed by a structured self-review against this course's own "common mistakes" guidance, tracking specific improvement between attempts.
Steps
1.Run a mock technical interview (with a peer, a mentor, or by timing yourself solving a problem while narrating out loud) — record it if possible
2.Immediately after, self-review against specific criteria: did you jump to code without clarifying constraints first? Did you state time/space complexity? Did you use meaningful variable names?
3.Run a mock HR round separately, covering at minimum "tell me about yourself," "why this company," and a weakness question — record your actual answers
4.Self-review the HR round against this course's guidance: was your "tell me about yourself" a 2-minute pitch or a rambling life story? Did your weakness answer show real self-awareness, or was it a cliché?
5.Repeat both types of mock interview at least 2 more times, and log specifically what changed between attempt 1 and attempt 3 — not just "I felt more confident," but concrete changes (e.g., "stopped jumping to code before clarifying constraints")
What This Produces
•A documented interview-performance trend across multiple attempts, technical and HR both
•Specific, named improvements you can speak to if asked "how did you prepare"
Artifact Name
mock-interview-log
Tips for Great Practice Cycles
Always produce a measurable artifact, not just "I practiced." A score log, a before/after resume diff, a recorded mock interview with notes — these are what let you (and anyone reviewing your prep) actually see progress, the same way a commit history shows real work.
Review yourself against specific criteria, not vague self-assessment. "That went okay" is much weaker feedback than "I didn't ask about scale before designing, and I used single-letter variable names twice."
Track trends across repeated cycles, not a single attempt. One aptitude test score or one mock interview tells you almost nothing on its own — the pattern across 3+ attempts is what actually shows whether your prep is working.
Match practice conditions to real conditions. Timed aptitude tests should actually be timed. Mock interviews should actually be spoken out loud, not just thought through silently — the format mismatch between practice and the real thing is a common, avoidable gap.
Practice Checklist
•[ ] A resume that's been audited against ATS/keyword criteria, not just visually reviewed
•[ ] At least 3 timed aptitude practice cycles with section-level score tracking
•[ ] At least 3 mock interviews (technical and HR) with structured self-review after each
•[ ] A documented improvement trend across attempts, not just a single data point
•[ ] Comfortable explaining, with specifics, how your preparation actually changed based on what you learned from practice
