How to Write an ATS Resume as a Fresher

The problem with fresher resumes

The standard resume format assumes you have a work history to put in the middle of it. When you do not, two failure modes follow.

The first is a resume that is mostly white space — name, degree, three skills, and a large empty area. The second is padding: hobbies stretched into paragraphs, "excellent communication skills" repeated three ways, a school prize from six years ago given its own section.

Neither is necessary. Most graduates have considerably more relevant material than they think — it is just filed in their head under "coursework" rather than "experience". The work is recognising it and presenting it in the shape a recruiter expects.

It also helps to know that employers hiring for graduate and entry-level roles are not comparing you to experienced professionals. They are comparing you to other freshers, and looking for evidence you can do things, learn quickly, and turn up reliably.

Section order for a first resume

Use the conventional headings, in this order:

1. Contact details. Name, phone, email, city, and a LinkedIn or GitHub link if it is current. In the document body, never in a header.
2. Professional summary. Two or three sentences: your discipline, your strongest relevant capability, and what you are looking for. Skip the adjectives.
3. Education. Degree, institution, graduation year, and grade if it helps you. Relevant modules as a single line, not a full transcript.
4. Projects. The section that does the heavy lifting. Two to four, each treated like a small job.
5. Experience. Internships, placements, part-time and casual work. Include it even when it is unrelated to your field.
6. Skills. Concrete, checkable, and honest about level.
7. Certifications and extras. Only where they add something — a relevant course, a language, a societies role with real responsibility.

Once you have a year or two of full-time work, experience moves above education and projects shrink or disappear. Until then, this order tells the more useful story.

Making projects count

A project section is the fresher’s substitute for work history, and it works well when written like work history rather than like a course submission.

Give each project a title, a timeframe, and two or three bullets covering what you built, what you used, and what came of it. Name the tools — they are the searchable terms a recruiter will look for.

Weak version

"Final year project — built a website for a local business as part of my degree. Learned a lot about web development."

This tells a reader nothing about what you can actually do. No tools, no scope, no outcome, and "learned a lot" is filler.

Strong version

"Booking site for a local salon — Sep 2025 to Mar 2026. Built a responsive booking system in React and Node.js with Stripe payments. Deployed to production and handed over to the owner, who has processed around 60 bookings a month since launch."

Same project. This version names five searchable technologies, establishes scope, and ends with evidence that the thing actually works in the world.

What counts as a project

More than you think: coursework with a real deliverable, a dissertation, a hackathon entry, a freelance job for a family friend, a society website you maintain, a dataset you analysed for your own curiosity. If you built or produced something and can describe the outcome, it qualifies.

Unrelated work experience is still experience

Graduates routinely leave out retail, hospitality, warehouse, tutoring, and care work on the grounds that it "isn’t relevant". Include it.

It establishes that you have held a job, met a rota, dealt with people, and been trusted with responsibility — which is exactly the uncertainty an employer has about a first-time hire. A resume with no employment at all raises a question that a summer in a supermarket answers.

Write it the same way as anything else: role, employer, dates, and one or two bullets emphasising the transferable part.

• Weak: "Worked at a café. Served customers."
• Better: "Served 200+ customers per shift in a busy city-centre café; trained two new starters and covered key-holder duties on weekends."
• Weak: "Tutored students in maths."
• Better: "Tutored six GCSE students in mathematics over two academic years; five improved by at least one grade."

Skills without overclaiming

The temptation is to list every tool you have ever opened. The problem arrives at interview, when you are asked about the third item on a list you wrote optimistically.

List what you could discuss for two minutes without preparation. Where level genuinely varies, say so plainly — "Python (proficient), R (basic)" is more credible than an undifferentiated list, and no interviewer penalises accurate self-assessment.

Avoid star ratings and progress bars. They are unreadable to parsers, and nobody agrees on what four out of five stars in Excel means.

Keeping it to one page

One page is right for almost every fresher, and the constraint is useful — it forces you to decide what actually matters.

• Cut secondary school details once you have a degree, unless a grade is specifically requested.
• Cut the objective statement. "Seeking a challenging role in a dynamic organisation" occupies three lines and says nothing.
• Cut hobbies unless they demonstrate something the role needs — competitive chess for an analyst role, maybe; "reading and socialising", no.
• Cut references entirely. "References available on request" is assumed and wastes a line.
• Keep every project and job that shows capability, even briefly.

If you are still overflowing, tighten the writing before you delete content. Most first resumes lose fifteen percent of their length to redundant phrasing without losing any substance.

Tailoring, when you are applying to fifty roles

Graduate applications happen in volume, which makes tailoring feel impossible. It is also precisely why tailoring works — most of your competition is sending the same document everywhere.

You do not need a new resume each time. Keep one master version and change three things per application: the summary, the order of your skills, and which project appears first. Ten minutes.

Where a graduate scheme lists specific competencies — teamwork, analysis, commercial awareness — make sure at least one bullet somewhere demonstrates each of them with an actual example. Those competencies are frequently what the shortlisting is scored against.