Featured image by Stephen Margo on Unsplash
Your resume is getting rejected in six seconds flat. That's the average time a recruiter spends on it before moving on. Six seconds. Less time than it takes to unlock your phone.
The brutal truth? Most resumes from even the smartest engineers look identical — a wall of text, vague bullet points, and zero proof of impact. Here's how to actually fix that.
The One-Page Rule Is Non-Negotiable
You are not a Nobel laureate. One page. Always. Recruiters at dream companies like Google, Goldman, or McKinsey are scanning hundreds of resumes from top campuses. A two-page resume from a third-year student signals poor judgment, not rich experience.
Tight, sharp, scannable. That's the game.
The Exact Section Order That Works
Stop rearranging randomly. This sequence is optimized for how recruiters actually read:
- Header: Name, contact, LinkedIn, GitHub — clean, no photo, no objective statement
- Education: Institute, degree, CGPA, expected graduation year — put this first if you're from an IIT/NIT/BITS, your brand does the heavy lifting
- Experience: Internships, research roles, PPOs — reverse chronological, company name bolded
- Projects: Maximum 3, each with a one-line tech stack and a quantified result
- Skills: Languages, frameworks, tools — no skill bars, no rating yourself 4/5 in Python
- Achievements & PORs: Competitions, rankings, leadership roles — keep it punchy
The Bullet Point Formula Nobody Teaches You
This is where 90% of resumes die. Vague bullets like "Worked on a machine learning project" are resume poison.
Use this structure instead: Action Verb → What You Did → Measurable Result.
- ❌ "Developed a recommendation system for e-commerce"
- ✅ "Built a collaborative filtering recommendation engine that improved user click-through rate by 34% on a dataset of 2M records"
Numbers. Impact. Specificity. That's what gets you past the ATS and into the recruiter's shortlist pile.
ATS Is the First Gatekeeper — Don't Ignore It
Applicant Tracking Systems kill resumes before human eyes ever see them. Format and keywords matter as much as content.
- Use a clean single-column layout — no tables, no text boxes, no columns
- Font: Calibri, Arial, or Garamond at 10–11pt — nothing fancy
- Mirror keywords from the job description naturally in your bullet points
- Save as PDF unless specifically asked for .docx
- Name your file: FirstName_LastName_Resume.pdf — not "resume_final_v3_ACTUAL.pdf"
The Projects Section Is Your Secret Weapon
For most students with limited internship experience, projects are where shortlists are won or lost. Recruiters know you haven't run a billion-dollar operation — they want to see how you think and build.
- Pick projects that solve a real problem, not just tutorial clones
- One line: what it does. One line: how you built it. One line: what the outcome was.
- Link to a live demo or a clean GitHub repo — broken links are an instant red flag
Pull up your laptop at 2 AM in your KS Verse hoodie if you have to — but that GitHub needs to show commits, not just a README you wrote in ten minutes.
What to Ruthlessly Cut
Space is premium real estate. Delete these immediately:
- Objective statements ("I am a passionate and hardworking student seeking…") — nobody cares
- Hobbies like "reading" and "travelling" unless directly relevant
- High school achievements — unless it's JEE rank, which stays
- Skill ratings and bar charts — they're meaningless and look amateur
- References available on request — implied, wastes a line
The Final Check Before You Hit Send
Run your resume through Resumeworded or Jobscan for ATS scoring. Get one senior from your target domain to roast it honestly. Then get one non-technical friend to read it — if they can understand what you built, you're writing clearly enough.
Your resume is a product. Ship it like one. Iterate, get feedback, and never treat it as done until the offer letter hits your inbox.
