Resume for Freshers

One page. Not a guideline — a filter.

For a fresher in India, one page is not a style preference; it is how the reader decides whether you understand your own position. A two-page fresher resume signals that you cannot tell what matters, and that is a worse signal than a thin single page. Nobody has ever been rejected for having only one page of relevant material.

The constraint does real work. It forces you to drop the school section down to two lines, cut the objective, delete the hobbies, and make room for the one project you can actually talk about for ten minutes. When you are struggling to fit, that struggle is the resume improving.

Margins are not the place to solve the problem. Shrinking to 8pt with quarter-inch margins to squeeze in a second project is instantly visible and reads as desperation. Cut content instead.

What fills the page when you have no experience

Projects, in order of preference: something you built end to end, something you built as part of a team, something you built following a tutorial. All three are worth listing; be honest about which is which. For each, write what it does, what you specifically built, what stack or method you used, and one number — users, records processed, accuracy, time saved, marks awarded, team size.

Internships, including unpaid ones and short ones. Six weeks at a small company where you did real work beats three months of a certificate-mill 'virtual internship' that produced nothing. Write what you did and what shipped, not what the company does.

Academic work that produced an artefact: a final-year project, a dissertation, a lab study, a case competition entry, a survey you ran. Coursework alone is not evidence, but coursework that produced something with a result is.

Positions of responsibility with scale attached. 'Coordinator, college tech fest' means nothing; 'Coordinator, college tech fest — ran a 4-person team, 620 registrations, ₹1.4 lakh sponsorship raised' means something. This is the section where non-engineering freshers usually have far more material than they think.

Certifications, kept short and only where relevant. Two respected ones beat eleven Coursera completions. A recruiter reading a fresher resume with fourteen certificates concludes you collect certificates instead of building things.

The objective line, and why to delete it

'To secure a challenging position in a reputed organisation where I can utilise my skills and grow with the company' appears on a substantial share of Indian fresher resumes, and it has never once helped anyone. It says nothing specific about you, it is interchangeable with every other applicant's, and it burns the most valuable two lines on the page.

Replace it with nothing, or with a two-line summary that carries facts. 'Final-year B.Tech (IT), VIT Vellore. Built and deployed two Django applications, one with 300+ active users. Looking for a backend engineering role.' That is the same real estate spent on things only you could have written.

If you are switching field — a mechanical graduate applying to data roles, a B.Com graduate applying to marketing — the summary earns its place, because it is the one line that explains the mismatch before the reader invents their own explanation.

Numbers when you have never been paid

Freshers assume quantification requires a job. It requires a scope. Every one of these is a real number available to a student: users of your app, rows in your dataset, accuracy of your model, people in the event you ran, sponsorship you raised, hours you tutored, teammates you led, weeks a project took, rank in a competition, papers you presented.

Two versions of the same fact. 'Worked on a machine learning project for crop yield prediction' tells the reader nothing about size or your role. 'Built a crop-yield model on 12,000 rows of ICAR data (Python, scikit-learn); 84% accuracy, presented at the departmental review, 3-person team where I owned feature engineering' is checkable and specific.

Do not invent numbers, and be ready for the follow-up. Indian technical interviews open with 'tell me about this project' more often than anything else, and a resume claim you cannot unpack for three minutes does more damage than the empty space it filled.

What Indian recruiters actually skip

Hobbies, unless they are competitive or produced something. 'Reading, listening to music, travelling' is filler and reads as such. 'District-level chess, 2023' is a fact.

Declaration lines and 'References available on request'. Both are leftovers from an older biodata convention that private-sector recruiters ignore. They belong on a government application, where they are genuinely required, and nowhere else.

Date of birth, marital status, father's name, religion and full postal address. City and state is all a private-sector resume needs. These fields are mandatory on sarkari forms, which is exactly why so many students copy them across by mistake.

Photographs, for private-sector applications. School and government applications are the exception, and the exception does not generalise.

Long skills lists with proficiency bars. A five-star rating you gave yourself carries no information, and a list of every language you have seen invites the interviewer to ask about the weakest one on it. List what you can be questioned on.

Campus and off-campus need different files

Campus placement is a volume process. Your resume passes through a placement cell format, an eligibility filter on CGPA and backlogs, and an aptitude round before a human reads it properly. Follow the placement cell's format exactly even where you think yours is better, keep your CGPA and any backlog history accurate to the decimal, and put your strongest project first because the reader is scanning identical resumes in a stack.

Off-campus is the opposite: nobody is obliged to read you at all, and an ATS often screens first. That means the job description's own words matter, single-column formatting matters, PDF matters, and standard section headings matter. It also means a referral is worth more than any formatting decision — one message to a senior from your college who works there beats fifty portal applications.

Keep one master file with everything, then cut a targeted version per application. Tailoring for a fresher is mostly reordering: move the project that matches the job description to the top, and swap the skills line to lead with what the JD asked for. It takes four minutes and moves the response rate more than any redesign.

The mistakes that cost interviews

An email address like coolguy_007@example.com. Use firstname.lastname. It costs nothing and it is noticed.

A GitHub or portfolio link that 404s, is empty, or has three repositories with a single 'initial commit' each. An empty link is worse than no link, because the recruiter clicked it.

Listing a skill you cannot survive one question on. Every technology on your resume is an invitation. If Java is on there because of one semester course, expect a Java question, and expect the interview to change direction when you cannot answer it.

Percentage and CGPA written inconsistently across sections, or a CGPA converted with a formula your university does not use. Write both, and state the conversion.

Sending a resume named 'resume_final_v3_updated.pdf'. Name the file Firstname_Lastname_Role.pdf. Recruiters save hundreds of these to one folder.

Letting AI write the whole thing. The current generation of fresher resumes has a recognisable rhythm — every bullet the same length, every verb from the same list of twenty, no specific detail anyone could verify. Recruiters have learned to spot it, and the penalty is the whole document losing credibility, not just the bad line.