Careers · 10 min read · Updated August 2026
Writing a fresher resume that survives an applicant tracking system
What actually happens to your resume after you press submit in India, and how to write one page that a parser, a recruiter and an engineer can all read in under a minute.
By Ovyro Editorial
A fresher resume in India is read three times by three different readers with three different budgets of attention. A parser reads it in milliseconds and turns it into rows in a database. A recruiter reads it for about seven seconds and decides whether to open the links. An engineer reads it for a minute before an interview and looks only for something to ask you about. A resume that pleases one of those readers and confuses the other two is the reason strong candidates get silence.
This guide covers the mechanics: what parsers break on, what recruiters scan for in the first screen, and what an engineer wants to find. None of it requires design skill or paid templates.
What the parser sees
Applicant tracking systems convert your file into plain text and then attempt to label the pieces. Anything that interferes with the ordering of that text costs you fields. Two-column layouts are the most frequent offender, because a naive extraction reads across the columns and interleaves your skills with your education. Text placed inside images, headers and footers, or in shapes and text boxes, is often dropped entirely.
Submit a PDF exported from a text editor, never a scan or an exported image, and never a design file flattened into a picture. Use one column, standard system fonts, and normal bullet characters. Test it yourself: open the PDF, select all, paste into a plain notes app. If the result reads in the order you intended, a parser will handle it.
Name the file predictably, with your name and the role. Recruiters download dozens of files into one folder and a file called resume_final2.pdf is an invitation to lose you.
- One column, standard fonts, black text, no graphics.
- No photographs, skill bars, star ratings or logos.
- PDF exported from text, not an image or scan.
- Copy-paste test before every submission.
The seven-second screen
A recruiter scanning a stack looks for four things in this order: the role you are applying for, your current status, evidence you have built something, and whether the links work. Everything else is read later or not at all.
Put a single summary line at the top that names the target, for example 'Final-year CSE student targeting backend internships, Python and Postgres, available January to June'. Vague self-description costs you the most valuable line on the page. Phrases like 'passionate hardworking individual seeking a challenging role' communicate nothing and are visibly boilerplate.
Order sections by what you actually have. A student with three shipped projects and no work experience should present projects immediately after the summary, then experience, then skills, then education. Reversing this to lead with education is the default in most Indian college templates and it wastes the top third of the page on information the reviewer already assumes.
Writing project lines that carry information
The weakest project line names a stack. The strongest names a problem, a decision and a result. Compare 'E-commerce website using React, Node, MongoDB' with 'Built a storefront for a family retail business, 400 SKUs, moved product search to Postgres full text after Mongo queries crossed 1.2 seconds'. The second is the same project honestly described, and it hands an interviewer three follow-up questions.
Numbers do not need to be impressive to be useful. Users, records, response times, uptime, marks, anything measured is better than an adjective. If a project has no numbers, describe the constraint you worked under instead: an offline-first app for poor connectivity, a scraper that had to respect rate limits, a model trained on a laptop GPU.
Two to four projects is the correct count. Reviewers read the first two. A list of ten tutorial clones reads as a list of tutorials, and it dilutes the one project you actually care about.
Skills, education and the things to delete
The skills section is a keyword index, not a self-assessment. List languages, frameworks, databases and tools you would be comfortable being questioned on, grouped by category, with no proficiency percentages. Every item you list is a legitimate interview topic, so remove anything you added for completeness.
Education needs the degree, institution, year and, if it is competitive, your score. Nothing else. School results below undergraduate level can go once you have any project or internship to show.
Delete: declarations, marital status, father's name, date of birth, full postal address, and photographs. They are conventions of an older Indian resume format, they carry no information for a technical role, and in the case of personal identifiers they create a genuine privacy exposure when a resume circulates.
- Keep: name, city, email, phone, GitHub, portfolio, LinkedIn.
- Remove: photo, DOB, marital status, address, declaration.
- Skills you list are skills you will be asked about.
Tailoring without rewriting
Tailoring does not mean writing a new resume per application. It means keeping one master document and changing three things: the summary line, the ordering of projects, and the emphasis inside the top project's bullets. That takes four minutes and materially changes how relevant the page reads.
Mirror the vocabulary of the posting where it is honest to do so. If a role says 'REST APIs' and you wrote 'backend endpoints', use their phrase. This is not keyword stuffing, it is removing a translation step for a reader who is comparing forty candidates against one description.
Keep a plain-text copy of the master version. Many Indian portals and government forms ask you to paste sections into fields rather than upload a file, and reformatting under a deadline is how errors get in.
Common failure patterns we see
Broken links are the most costly and the easiest to fix. A GitHub profile with an empty README, a deployed URL that has expired on a free tier, a portfolio behind a login. Check every link on a phone, on mobile data, before you apply.
Second is the two-page fresher resume padded with coursework, workshop attendance and certificate lists. Certificates for completing a video course are not credentials; they signal time spent rather than capability. One page, always, until you have three years of work history.
Third is inconsistency between the resume and the profile a recruiter finds when they search your name. Dates that disagree, a different job title, a portfolio showing work the resume does not mention. Fix the mismatch before it becomes a question you have to explain in an interview.
Frequently asked questions
Should a fresher resume in India be one page or two?
One page. A second page is justified only by multiple years of professional experience or a publication record, and even then most reviewers read only the first page.
Do I need a cover letter for Indian tech roles?
Only when the form has a field for it. When it does, four sentences: the role, your most relevant build, why this company specifically, and your availability window.
Are online course certificates worth listing?
Rarely. List the project you built during the course instead. A recruiter can verify a working artefact; a completion certificate only proves attendance.
How do I show experience if I have never had a job?
Freelance work, open-source contributions, club and fest engineering work, and paid or unpaid research assistance all count as experience. Describe them with the same structure as employment: what you owned, what you shipped, what changed.