Fresher resume checklist: what to check before you apply
The checks a resume reviewer runs on a fresher resume, in the order they run them: the first few seconds, projects, skills, accuracy and tailoring for one opening.
Share on WhatsApp
Conceptual image · created with AI
Most fresher resumes are not rejected because they are badly designed. They are passed over because a busy reader cannot see, quickly, what the person is applying to be and what they have actually done. Those are fixable problems, and they are easier to fix with a list than with a new template.
This is the checklist used in GullyFuture resume clinics, where a reviewer reads a student's own resume with them and the student rewrites it in the room. You can run it on your own resume in an evening. It works best if you also ask one other person to read it with the same list.
What you should come away with
- Say what role you are applying for in the first two lines
- Explain every project: the problem, what was built, and which part was yours
- List only skills you could talk about for three minutes
- Count part-time work, family business and club roles as experience
- Make every date and mark match your documents exactly
- Keep a master resume and tailor a copy for each opening
Start with the first few seconds, because that is the time a reader gives a resume before deciding whether to read it properly. Check that your name, phone number and email address are at the top and correct, and that the email address is a plain one built from your name. Check that the first two lines say what role you are applying for, in plain words: 'Final-year mechanical engineering student looking for a graduate engineer trainee role in manufacturing' tells a reader more than any career objective about growth and challenging environments. Check that the most relevant thing you have done is near the top, not on the second page.
Check the layout next. For most freshers one page is enough. Use a single column, standard headings such as Education, Projects, Experience and Skills, and real text rather than text inside images, tables or text boxes. Plain layouts are easier for people to read, and easier for the applicant tracking systems many employers use to store and search applications. Save it as a PDF unless the employer asks for something else, and give the file a sensible name, such as your name and the word resume.
Then read every project entry. A title and a list of technologies is not an explanation. For each project, check that it says what problem it solved, what was built, which tools were used, what happened in the end, and, if it was a team project, which part was yours. An interviewer will ask what you personally did, so say it on the page. If there is a link to the code, a demo or a report, include it. Two projects you can talk about in detail are worth more than six you can only name.
Now go through the skills list line by line and ask one question of each entry: could I talk about this for three minutes if an interviewer asked? If not, remove it. A skill is something you have used in work you can show, not the name of a course you once attended. Every item on the list is a question the interviewer is entitled to ask, and a long list of things you cannot discuss is worse than a short list you can.
Look for experience you may have left out. Many freshers believe only internships count. A part-time job, helping to run a family shop, tutoring younger students, organising a college event, volunteering or a small paid project all show that you can be relied on to turn up and finish things, which is exactly what an employer of freshers is trying to judge. Write each one plainly: what the work was, and what you were responsible for.
Check certifications in the same way as skills. A certificate shows that you studied something; it does not show that you can use it. Keep the ones that are relevant to the role and connect each to something you did with what you learned. If a certificate has no connection to the job or to anything you have built, it can usually go.
Next, check accuracy, because employers check it too. Background verification compares what you have written with what your college and any previous employer confirm. Dates should match your certificates and marksheets. Marks and grades should be stated exactly as they appear on the marksheet, in the same scale. Job titles should be the ones you actually held. Project descriptions should be your own words, not copied from a senior or a website. A small exaggeration that seems harmless can cost an offer at the last stage, and it will certainly cost you in the interview.
Check consistency across places. If you have a LinkedIn profile or a GitHub account, it should tell the same story as the resume: the same dates, the same projects, the same target role. Recruiters often look, and a mismatch raises questions you do not want to answer.
Finally, tailor it for the opening you are applying to. Keep one master resume with everything in it, and make a copy for each application. Read the posting and mark what it asks for. Move the most relevant project or experience to the top. Use the posting's own words where they are honestly true of you, and never add a tool or skill you have not used just because the posting mentions it. Remove what does not help for this role. It takes twenty minutes per application, and it is the difference between a resume that could be for anything and one that is clearly for this job.
When you have finished, read it once as the recruiter would: quickly, looking for a reason to believe you fit. If the reason is not obvious in the first few seconds, go back to the first check. And if you can, ask somebody who reads resumes at work to look at it with you. A second reader finds in five minutes what you will not see after five readings of your own.