Why the IIT resume is different
Campus placement at IIT and NIT is not a normal job search. 300 to 500 students apply for 8 to 15 Day 1 slots. Recruiters get 400 resumes per role, read each for under 10 seconds, and shortlist 20 for interviews. The resume is the only filter. A good one does not get you the job; it gets you into the room where you can get the job.
IIT placement resumes follow a strict template set by the Student Placement Office at each IIT (SPO at IIT Bombay, CDC at IIT Kharagpur, Placement Cell at IIT Delhi). One page. Specific section order. No photo. No colours beyond subtle accents. The template is rigid because consistency lets recruiters scan 400 files quickly. Breaking the template makes your resume feel amateur, not creative.
This guide gives the SPO-compliant structure, the five pillars recruiters actually score on, and branch-specific bullet examples for CSE and Mechanical. It applies equally to NIT placements (Trichy, Warangal, Surathkal), where the format is near-identical.
Section order (SPO-compliant)
Order matters. Recruiters scan top-down; the first five inches of the page decide the shortlist. Here is the order used by most IIT SPOs and mirrored by NIT placement cells.
1. Header
Name, roll number, branch, CGPA, phone, IIT email, GitHub, LinkedIn. Single line or two. No photo.
2. Education
IIT first with branch, current CGPA (2 decimals), expected graduation. Class 12 percentage and board. Class 10 only if percentage is 90+.
3. Scholastic Achievements
JEE Advanced AIR, JEE Main percentile, KVPY, Olympiads, department rank. 2 to 4 lines. Most IIT resumes keep this above Experience.
4. Internships / Work Experience
Reverse chronological. Role, company, dates, 3 to 4 bullets each. Quantify every bullet.
5. Projects
Course projects, self-initiated, research. Title, stack, role, 2 to 3 bullets, link to GitHub or demo.
6. Skills
Languages, frameworks, tools, databases. Grouped, comma-separated. No proficiency bars.
7. Positions of Responsibility
Secretary of X Club, Coordinator for Y Event, TA for CS 101. Include scale numbers (500 students, 20 volunteers).
8. Extra-curricular
Sports at inter-IIT, cultural wins, community work. 2 to 3 lines total. This is the differentiator section.
5 pillars of an IIT resume
JEE rank + CGPA first
On Day 1 companies, recruiters filter by these two numbers before reading bullets. Put them where they cannot be missed: AIR in Scholastic Achievements, CGPA in Education header.
Quantify every bullet
Not "worked on backend API" but "built backend API handling 50K req/s on a 2-node setup, cut p99 latency 40 percent". IIT recruiters expect numbers from IITs. Bullets without numbers get skipped.
Project depth over breadth
4 deep projects beat 9 shallow ones. Depth means: problem statement, your contribution, tech choice rationale, outcome with a number. Shallow means: "used React and Node to build a clone of X".
One page only, even for dual degree
The SPO one-page rule is near-universal across IITs. Font 10 to 11 pt, margins 0.5 inch, line-height 1.15. Every word earns its space.
Branch-specific tailoring
CSE resume emphasises system design, scale, algorithms. Mechanical emphasises CAD, simulation, fabrication. Electrical splits between core (VLSI, Power) and software. Never send a generic resume to a branch-core company.
CSE branch example bullets
Use these as a template for how depth and numbers combine. Each bullet names the tech, the scale, and the outcome.
- Designed and implemented a distributed task queue in Go handling 100K messages/second across a 5-node cluster, reducing backend processing latency by 62 percent compared to the Redis-based predecessor.
- Led a team of 3 in building the search auto-complete for CampusConnect (12K MAU), using a Trie + Bloom filter index that served queries in under 8 ms p95 on a single t3.small instance.
- Contributed a patch to PyTorch (merged, PR #87412) fixing a CUDA memory leak in the data loader that affected batch training jobs above 64 workers.
- Won 2nd place out of 184 teams at Inter-IIT Tech Meet 2025 for a real-time drone obstacle avoidance system built on ROS 2 with a 12 ms end-to-end reaction loop.
Mechanical branch example bullets
Core branches need domain-specific numbers: efficiency percentages, mass flow, dimensional tolerance. Software-y bullets (Python tool, dashboard) are fine as secondary proof.
- Designed a 3-stage compressor blade geometry in ANSYS Fluent, improving isentropic efficiency from 81.2 to 84.7 percent over the baseline NACA profile for a 3 kg/s mass flow.
- Fabricated a 1:4 scale model of the designed compressor using 5-axis CNC (Al 6061), validated simulation results to within 3 percent error on a lab wind-tunnel setup.
- Co-authored a paper (accepted, AIAA 2026) on slotted-blade tip leakage reduction, contributing the CFD setup and mesh independence study.
- Internship at General Motors Tech Bangalore: built a Python tool that reduced BOM reconciliation time from 4 hours to 12 minutes across 2,400 SKUs.
7 mistakes that drop you in the stack
Listing "Microsoft Word" and "Gmail" under Skills.
Cut. Every IIT student has these. Use the space for languages, frameworks, CAD tools, simulation packages you actually know deeply.
Course project called "E-commerce Website using MERN Stack".
Either rename to the actual product you built and quantify usage, or drop the project. Generic clones flag as filler.
CGPA hidden in the middle of the page.
Put CGPA in the Education line next to the branch. Add department rank if in top 10.
POR that reads "Member of XYZ Club".
Mere membership is not a POR. Replace with a role you actually held with scale: "Coordinator, TechFest 2025 (event attended by 8,000 students)".
Research project with no professor name or outcome.
Always cite the professor and lab. Add publication status, poster, report link, or metric.
Resume longer than 1 page.
Cut. Every SPO in every IIT has a 1-page limit. Companies receive 400 resumes per role; 2-pagers get skipped at the first filter.
Same resume for every company on Day 1.
Two versions minimum: software (Goldman, Microsoft, Samsung R&D) and core (Schlumberger, Reliance, ISRO). Tailor the projects order.
Day 1 vs Day 2 vs open season
Day 1 companies (Microsoft, Goldman Sachs, Uber, Rubrik, McKinsey, BCG) filter on CGPA first (often 8.0 or 8.5 cutoff) and expect at least one strong internship or a competitive programming rank. Resume must lead with numbers. Scholastic achievements visible.
Day 2 onwards (Indian IT services, analytics firms, core engineering) usually drop the CGPA cutoff to 7.0 and widen the net. Here the POR and extra-curricular sections carry more weight; recruiters want cultural fit signals alongside technical depth.
Open season and off-campus use the same resume but tailor the summary line (if you include one) to the specific role. Reorder projects so the most relevant one is first. Swap in a different 1-line role statement at the top.
External references
Frequently asked questions
Can my IIT placement resume be 2 pages?+
Should I include CGPA if it is below 7.5?+
Do I need a photo on the IIT resume?+
How many projects should I list?+
Should I list online courses like Coursera?+
My JEE rank is above 10,000, should I still include it?+
What if I had no internship in second year summer?+
Should NIT students follow this same format?+
Does ResumeBuildz have an IIT template?+
Build your IIT / NIT placement resume
ResumeBuildz ships a single-column, SPO-compliant template. Edit online, export to PDF with exact one-page margins.