A recruiter at Razorpay once told us she spends about seven seconds on a resume before deciding whether to read it properly. Seven seconds. That's one column of text, maybe two. If your name, college, and first bullet don't signal something useful in that window, the rest of the page doesn't matter.
For anyone building a software engineer resume in India as a fresher or early-career candidate, the problem isn't effort. Most candidates spend hours formatting. The problem is they optimize for what looks impressive to them, not what a recruiter is actually scanning for. This post breaks down exactly what that scan looks for, with specific before-and-after examples.
The 7-Second Scan Is Real, and It's Not Random
Recruiters aren't reading randomly. They're running a pattern-match. At a service company like TCS or Infosys, the first scan checks: college tier, CGPA (if stated), and whether the skills section has the exact technology stack the team uses. At a product company like Razorpay or Swiggy, the scan shifts: they're looking for a project or internship that shows you shipped something real.
At Google India, it's different again. The recruiter is looking for signal that you can think at scale. That means algorithmic complexity, system size, or research output. A "to-do list app built with React" doesn't give them that signal, even if the code is clean.
Know which scan you're optimizing for before you write a single bullet.
Your College Name and CGPA Are Doing More Work Than You Think
At service companies, CGPA cutoffs are hard. TCS iON tests filter at 60% or 7.0 CGPA depending on the year and campus. Infosys Instep has similar floors. If you're above the cutoff, state your CGPA clearly. If you're below it, don't hide it — it'll come up anyway — but make your projects section strong enough that the recruiter keeps reading past it.
For product companies, college tier matters less than you'd expect at the resume stage. Razorpay and CRED have hired from Tier-2 and Tier-3 colleges when the candidate's GitHub or internship work was strong. The resume just has to get you to a phone screen. After that, your work speaks.
One thing that kills otherwise good resumes: putting CGPA in a tiny font at the bottom of the education section. If it's above 8.0, it belongs right next to your college name on the same line.
Bad Bullets Are the Biggest Problem on Fresher Resumes
This is where most candidates lose the recruiter's attention. Here are real examples of the kind of bullets we see constantly, and what they should say instead.
Bad: "Worked on backend development using Java and Spring Boot."
Good: "Built a REST API in Spring Boot handling 500+ daily requests for a college event registration system; reduced manual admin work by 3 hours per event cycle."
Bad: "Contributed to an e-commerce project as part of a team."
Good: "Integrated Razorpay payment gateway into a Django e-commerce app; handled webhook verification and edge cases for failed transactions."
The bad versions describe activity. The good versions describe output. Recruiters at product companies are specifically trained to ignore activity-based bullets because every candidate has them. Output-based bullets are rarer and they stick.
If you genuinely don't have numbers, estimate conservatively and say so. "Reduced page load time by roughly 40% by lazy-loading images" is honest and specific. "Optimized performance" is noise.
The Skills Section Is Not a Keyword Dump
A skills section that lists 30 technologies is a signal that you're comfortable with none of them. Recruiters know this. A Wipro recruiter told us she mentally divides candidates' skill sections by two: if someone lists 20 skills, she assumes they're actually comfortable with 10.
List only technologies you could answer a technical question about right now, without Googling. For a fresher, that's usually 6–10 items. Group them logically: Languages, Frameworks, Tools, Databases. Don't list "MS Word" or "Google Docs" unless the job description specifically asks for productivity tools.
One exception: if a job description mentions a specific technology three times, and you have even passing familiarity with it, include it and be ready to talk about it. Applicant tracking systems at large companies like HCL and Cognizant do keyword-match before a human ever sees the file.
One Page Is a Rule, Not a Suggestion
For 0–3 years of experience, a two-page resume is a red flag. It signals either poor judgment about what matters, or padding. Both are bad signals before you've even spoken to anyone.
Everything on your resume should be there because it earns its space. A project from your first year of college that you've since done better work than? Cut it. A certification you got in 2022 that you can't speak to anymore? Cut it. Your "hobbies" section listing "reading, music, cricket"? Cut it unless you're applying to a company where culture fit is assessed at the resume stage (almost none are).
The one-page constraint is also useful as a forcing function. If you can't fit your best work onto one page, the problem is usually that you haven't decided what your best work is yet.
The Projects Section Is Your Actual Interview Starter
For a software engineer resume in India targeting fresher roles, the projects section is often what gets you the call. Not your CGPA. Not your skills list. The project that made a recruiter curious enough to ask about it.
A strong project entry has four things: what you built, what technology you used, what scale or outcome it reached, and one interesting technical decision you made. That last one is what separates candidates who get interesting technical rounds from candidates who get generic ones.
Weak: "Built a chat application using Node.js and Socket.io."
Strong: "Built a real-time chat app in Node.js and Socket.io supporting 50 concurrent users; chose Socket.io over long-polling after benchmarking both under simulated load on a ₹0 budget using free-tier AWS."
The second version gives an interviewer three questions to ask. That's exactly what you want.
Format Errors That Auto-Reject You Before a Human Reads Anything
At companies using ATS (most large ones do, including TCS, Wipro, and Amazon India), certain formatting choices make your resume invisible to the system even if a human would have liked it.
Avoid: tables, text boxes, columns built with invisible borders, headers and footers with contact information, and images of any kind. ATS parsers fail on all of these. Submit a clean single-column PDF with standard section headers. Name the file "FirstName-LastName-Resume.pdf" — not "Resume-Final-v3-UPDATED.pdf."
Font size below 10pt causes parsing errors on some systems. Margins below 0.5 inches do the same. These aren't aesthetic choices. They're technical requirements.
What a Google India Recruiter Scan Looks Like vs. a TCS One
At TCS, the recruiter is checking a checklist: eligible college, eligible CGPA, required skills present, no obvious red flags. The resume's job is to clear the filter cleanly. Creativity in formatting or unusual project choices can actually hurt you here because the recruiter isn't looking for unusual.
At Google India, the recruiter is looking for evidence of analytical depth. That means: competitive programming achievements (even a Codeforces rating is worth mentioning if it's above 1400), research publications or conference papers, or projects that involved non-trivial algorithmic work. A Google recruiter will spend more than seven seconds on a resume that shows one of these. They'll spend exactly seven on one that doesn't.
Razorpay and other fintech companies are looking for a specific thing: have you touched real money or real users? An internship where you built a feature that went to production matters more than three personal projects that never left your laptop.
Before You Send Anything, Run This Check
Read your resume out loud. Every bullet. If you stumble on a bullet while reading it, a recruiter will stumble on it while skimming. Rewrite it.
Then ask someone who hasn't seen your resume to tell you, in one sentence, what you're good at after reading it for 10 seconds. If their answer doesn't match what you want to be hired for, the resume isn't doing its job.
The goal isn't a resume that covers everything. It's a resume that makes one clear case for why you're worth 30 minutes of someone's time.
After you fix the resume, the next problem is surviving the interview itself. Knowing what to put on paper and knowing how to talk about it under pressure are different skills. The PrepFinity blog has posts on both — start there for what comes after the callback.
Ready to practice talking through your resume and projects under real interview pressure? Start with 3 free interviews — no credit card needed.