Resume format for freshers

A fresher resume has one job: convince a stranger, in about twenty seconds, that you can do work you have not been paid to do yet. Everything below follows from that. There is no experience section to carry the document, so projects, coursework and clarity have to carry it instead.

One page. Always, at this stage. Two pages says you could not decide what mattered, and a shortlist of four hundred applicants is decided by whoever made deciding easy.

The order, top to bottom

1. Name and contact details. Name, phone, email, city, and the two links that are worth having: LinkedIn and GitHub (or Behance, or a portfolio). Use an email address that is your name. Nothing else belongs here — no address block, no marital status, no “Curriculum Vitae” as a title.
2. A two-line summary, or nothing. If you can write two specific lines — what you build, what you are looking for — keep it. A generic “hardworking individual seeking a challenging opportunity” is worse than empty space, because it uses the most valuable part of the page to say nothing.
3. Education. Degree, institution, dates, and your marks. This is the one section that goes above experience while you are a fresher, and it drops below it about two years into your first job.
4. Projects. The most important section on a fresher resume, and the one most people write worst. Two or three, each with what it does, what you built, the stack, and a link if it exists.
5. Internships or part-time work. Same shape as a job entry: organisation, role, dates, two or three bullets about what changed because you were there.
6. Skills. Grouped, honest, specific. Languages, frameworks, tools. Leave out anything you would not want to be asked about for ten minutes.
7. Everything else, if it fits. Certifications, positions of responsibility, competitions, publications, languages spoken.

How to write a project entry that works

The weak version names a technology stack. The strong version names a result. Compare:

• Weak: “Built a web app using React, Node.js, MongoDB and Express.”
• Strong: “Built a hostel mess-billing app used by 300 students for two semesters; cut monthly reconciliation from a day of spreadsheet work to about ten minutes. React, Node, Postgres.”

The second one is the same project. It says how many people used it, how long it ran, and what it replaced — the three things that turn a class assignment into evidence. If a project has no users, say what it does and what was hard about it. Do not invent numbers; an estimate you can defend is fine, a fabricated one ends a good interview badly.

What to leave out

• Photo — unless you are applying somewhere it is expected. In India it often is; in the US and UK it usually costs you. The India-specific page goes through this properly.
• Date of birth, father’s name, gender, marital status, nationality, full postal address. None of these help, several create bias, and together they are a third of a page.
• “References available on request.” Everyone knows. They will ask.
• Declaration lines and signatures. A holdover from typed applications; on a modern resume it reads as a template nobody edited.
• Skill rating bars. A five-dot rating for Python means nothing to a reader and extracts as nothing at all to a parser.
• Objective statements about what you want. The reader is deciding whether you are useful. Space spent on your ambitions is space not spent on evidence.

Make it survive the software

Almost every application you submit is parsed before a person reads it. Standard section headings, month-and-year dates, no tables used for layout, real text rather than an image. The mechanics are in the ATS resume guide, and the thirty-second version is: extract your own PDF and read what comes out.