Structure: what goes where
For a fresher, the résumé has one page and a fixed order. Contact details at the top, meaning name, phone, professional email and city, then education, then the work you have done: projects, internships and certifications in that order of proof. Skills come after evidence, not before, as a short list of tools and methods you can actually defend. Links to code repositories or portfolios replace claims. No photograph, date of birth, marital status, father’s name or religion is needed unless an employer’s application form requests it. Keep the file as a PDF with a clear file name, and check how it appears on a phone, because recruiters often read it that way first.
- Contact details, then education, then projects and internships.
- A short skills list you can defend in person.
- Links to code or a portfolio instead of claims.
- PDF file with a clear name.
Writing about projects without inflating
Projects are a fresher’s strongest section because they can be checked. Write each one in three parts: what problem the project addressed, what exactly you built or did, and what resulted, measured where you can measure honestly. Built a sales dashboard is weak; designed and implemented the data model, wrote the analysis, presented findings to the panel is defensible. Never claim a team project entirely, because a contributed-among-four description reads better than a solo claim that collapses in the interview. Skip technologies you merely watched a tutorial for. Before listing anything, ask whether you could discuss it for five minutes with questions; if not, cut it. A thin, true résumé beats an impressive, hollow one.
Formatting and language rules
Keep the formatting boring and the language clean. One font, consistent spacing, bold for headings, no tables for main content, and colour only for subtle emphasis. Write in active sentences, past tense for completed work, present tense for ongoing work. Proofread carefully, especially for the names of tools and subjects, which is where avoidable typos cluster, and have one person read it before you send it anywhere. Customise the top third, meaning the education line, the skills list and the first project, for each application, matching words from the announcement where they are honestly true. Save each tailored version under the company’s name, and keep the master separate. Consistency between your résumé and your application form matters more than brilliance.
Mistakes that quietly cost interviews
Some errors are fatal and easy to fix. A wrong phone number is the classic, because recruiters rarely chase a second contact if the first fails. Unexplained gaps get interpreted without you in the room, so state briefly what a gap actually was, such as exam preparation, freelancing or a health issue, without drama. Do not list every course certificate as if each were a qualification; select the few that matter for the role. Never convert an internship into work experience. And skip objective-paragraph clichés: one tuned line on what you are seeking beats a sentence about challenging roles in growth-oriented organisations. Before every send, confirm the file opens properly, on screen and on a phone.
Keep a master document current
Treat the résumé as a living document, reviewed monthly rather than rewritten in panic whenever a drive appears. Update it the week results are declared, after an internship ends, or when a project ships. Keep a master version with everything you have ever done, and cut down per application; add nothing you cannot evidence. File each sent version by employer and date, so that when an interview arrives months later you can recall exactly which version they read, because being caught quoting a résumé you no longer recognise is an awkward way to open a conversation. Rename the file properly before each send, and send it from an email address that sounds like you.