A recruiter spends an average of seven seconds scanning a resume before deciding whether to continue reading. For freshers without years of work experience, that first impression is everything. This guide shows you exactly what to include, what to cut, and how to structure your one-page resume for maximum impact.

The golden rule: one page

Freshers should keep their resume to one page. Hiring managers at large companies receive hundreds of applications; a concise, well-organized single page signals clarity of thought and respect for the reader's time.

Essential sections and their order

1. Contact information

Place your name prominently at the top. Include your phone number, a professional email address (first.last@gmail.com, not gamer123@), and links to your LinkedIn profile and GitHub if relevant. Avoid a full home address — city and state are sufficient.

2. Summary or objective (optional but powerful)

Three lines that answer: who you are, what you can do, and what you are looking for. Tailor this to each role. Example: "Final-year Computer Science student with strong DSA fundamentals and two internship projects in full-stack development. Seeking a software engineering role where I can contribute to scalable products from day one."

3. Education

List your degree, institution, graduation year, and GPA or percentage if above 7.5 CGPA or 75%. Add relevant coursework if space allows.

4. Skills

Group skills logically: Programming Languages, Frameworks, Tools and Platforms, and Soft Skills. List only skills you can discuss confidently in an interview — do not pad this section.

5. Projects

This is the most important section for freshers. For each project:

  • State what the project does in one sentence
  • Describe your specific contribution (not just the team's)
  • Quantify the result where possible: "Reduced API response time by 40%" beats "Improved performance"
  • Link to a live demo or GitHub repository

Three strong projects beat six vague ones.

6. Internships and work experience

If you have internships, list them above projects. Use action verbs: built, designed, automated, reduced, improved. Focus on outcomes, not responsibilities.

7. Certifications and achievements

Include only relevant certifications (AWS, Google, Coursera courses in your domain) and notable achievements (hackathon wins, competitive programming rankings, academic medals).

Formatting rules that matter

  • Use a clean, ATS-friendly font: Calibri, Arial, or Georgia at 10–11pt
  • Consistent margins: 0.5 to 0.75 inches
  • Use bullet points, not paragraphs
  • No photos, graphics, or tables — they confuse ATS software
  • Export as PDF unless the job posting specifies Word

Common mistakes freshers make

  • Listing "MS Office" as a skill in 2026
  • Using a generic objective statement
  • Cramming five projects with no detail instead of two projects with clear impact
  • Spelling the company name wrong in a tailored summary

Tailoring your resume for each application

Before submitting, match your skills and project descriptions to the keywords in the job description. ATS filters look for exact or near-exact matches. Spending five minutes tailoring each application significantly improves your callback rate.

Once your resume is ready, practise talking about every line with PlacementDo — interviewers will probe the exact projects and skills you listed.

Resume quality checks before you apply

Read your resume once as a recruiter who has only thirty seconds. The first screen should reveal your target role, strongest evidence, and relevant skills without requiring a search. Replace broad adjectives with proof: a feature shipped, a response time reduced, a test suite added, a competition rank, or a user problem solved. If a result cannot be measured, describe the observable change or decision instead of inventing a number.

Keep project bullets consistent. Start with the problem or responsibility, name the technology only where it clarifies the work, and finish with the outcome. A good project section also tells the interviewer what you personally built, how you validated it, and what limitation remains. Remove tools you cannot discuss for several minutes. Tailor the order of bullets to the job description while keeping the underlying facts truthful.

Before submitting, export the PDF, check it on a phone, and test every link. Ask a friend to explain your profile after reading it once; confusion shows where the wording is too dense. Keep a plain-text version for application forms and maintain a change log so you can update dates and results without losing an older version. A focused, honest one-page resume gives your interview answers a reliable foundation.