You applied to sixty companies and heard back from four. It is easy to read that as "I am not good enough". Usually it is something much more boring: your resume was never read by a human at all, or it was read for about eight seconds by someone with two hundred more in the pile.
Both of those are fixable, and neither requires you to have more experience than you have. This is the format we give students in our own placement prep, and the reasoning behind each part of it.
What an ATS actually does (and does not do)
An Applicant Tracking System is a database with a parser attached. It reads your PDF, tries to work out which text is your name, your education and your skills, and files it. When a recruiter searches "React Node fresher Bengaluru", it returns the resumes whose parsed text matches.
It does not score your personality or reject you for "low ATS score" — that number you see on resume-checker sites is the website's own invention, not something the ATS produces. What it genuinely does is fail to parse layouts it was not built for, and then you are simply not in the results.
The one-page structure to copy
Top to bottom, in this order. The order is the point: a recruiter reads the top third and decides whether to read the rest.
- 1
Header — name, one line of contact
Name, phone with +91, a professional email address, and live links to GitHub and LinkedIn. Put the links as actual clickable URLs, in the body of the document, not in the page header. No photo, no date of birth, no full postal address — city and state is enough.
- 2
A two-line summary, written for this role
Not an objective ("seeking a challenging role..."), which says nothing and wastes your best real estate. Two lines: what you are, what you have built, what you are looking for. Rewrite it per role — it takes ninety seconds.
- 3
Skills — grouped, honest, and as a plain list
Group them: Languages, Frameworks, Tools, Databases. Use the same words as the job posting ("React.js" if they wrote React.js). Only list things you would be comfortable being asked about for ten minutes. A padded skills section is the fastest way to lose an interview you had already won.
- 4
Projects — two or three, with links
For a fresher this is the most important section on the page, which is why it sits above education. Each project: one line on what it does, one on the stack, and one to two bullets on a hard part you solved. A live URL and a GitHub link for every single one.
- 5
Experience — internships, freelance, real open source
Same bullet discipline as projects. If you have none yet, leave the section out entirely rather than padding it with a two-day workshop. An honest short resume reads far better than a stretched one.
- 6
Education — compact, at the bottom
Degree, college, graduation year, CGPA if it is above 7.5. Class 10 and 12 marks only if you are applying somewhere that explicitly asks. Three lines, not a third of the page.
- 7
Achievements — only if they are specific
A hackathon placing, an open-source PR that got merged, a rank in a contest with thousands of entrants. "Participated in" is not an achievement; leave the section off rather than filling it.
How to write a bullet that does something
Most fresher bullets describe a technology rather than a contribution. The fix is mechanical: what you did, how, and what changed as a result.
| Weak | Strong |
|---|---|
| Worked on a food delivery app using React | Built the order-tracking screen in React with WebSocket updates, cutting the time to show a status change from ~30s of polling to under a second |
| Used MongoDB for the database | Modelled orders and restaurants in MongoDB and added a compound index on (restaurantId, createdAt) that took the dashboard query from 1.2s to 90ms |
| Team project on machine learning | Trained and compared three classifiers on a 12,000-row dataset; chose logistic regression over a heavier model because it matched accuracy at a fraction of the inference time |
What if you genuinely have nothing to put in Projects?
Then that is the actual problem, and no amount of formatting fixes it. The good news is that it is a four-to-six week problem, not a four-year one.
- Build one thing that solves a problem you personally have. Deploy it somewhere with a public URL. That single project will out-perform three tutorial clones.
- Clone something real and then change it — take a familiar product, rebuild the core flow, and add one feature the original does not have. The added feature is what you talk about in the interview.
- Make five genuine open-source contributions. Documentation fixes count; they teach you to read an unfamiliar codebase, which is most of the job.
- Do a structured internship where the output is a real project with a mentor reviewing your code. Anything that ends in a deployed artefact and a code review is worth more than a certificate.
The final checks before you send it
- 1
Copy-paste test
Open your PDF, select all, copy, paste into a blank text document. If the order is scrambled or anything is missing, an ATS sees the same mess. Fix the layout, not the content.
- 2
The eight-second test
Hand it to a friend for eight seconds, take it back, and ask what role you are applying for and what you built. If they cannot answer both, your top third is doing the wrong job.
- 3
Keyword pass against the posting
Put the job description next to your resume. Every required skill you genuinely have should appear somewhere in your words, spelled the way they spelled it.
- 4
Link check
Click every link in the exported PDF. A dead GitHub link or a deployment that has expired is worse than no link — it reads as a project that no longer exists.
Frequently asked questions
Should a fresher resume be one page or two?
One page, without exception, until you have two or more years of full-time experience. A two-page fresher resume signals padding, and the second page is rarely read.
Should I add a photo to my resume in India?
No, for software roles. It takes space from your projects and some parsers mis-read the block around it. Photos are expected in a few sectors and on some government forms — follow the instruction if there is one, and otherwise leave it out.
PDF or Word — which should I send?
PDF, unless the application form explicitly asks for .doc or .docx. PDF preserves your layout everywhere; modern ATS parse it without trouble. Export it properly rather than printing to PDF from a screenshot.
Do I need a different resume for every application?
You need a different summary line and a reordered skills list — about two minutes of work per application. Keep one master document with everything and cut it down for each role rather than starting fresh.
Is a low CGPA going to get me rejected?
Some companies do filter on CGPA, and you cannot do anything about those. Most do not, and a strong project section changes the conversation entirely. If your CGPA is below 7.5, leave it off and let the projects speak.
Where should I put my GitHub and LinkedIn links?
In the header line at the top of the document body, as full clickable URLs. Do not put them in the page header or footer — some parsers ignore that region completely.
One thing to do today
Open your resume and rewrite a single project bullet using the what-how-changed pattern, with one real number in it. If you cannot find a number, that tells you which project needs another weekend of work. Then do the copy-paste test. Those two changes will do more for your shortlist rate than the next twenty applications.