How Recruiters Actually Read Your Resume
Before you write a single line, understand who reads your resume. In most companies it passes through two filters:
- An Applicant Tracking System (ATS) – software like Workday, Greenhouse, Lever or Naukri RMS that reads your file, pulls out your details and ranks you against the job description.
- A human recruiter – who usually skims the resume in well under a minute, looking for the role, key skills, projects or experience, and any red flags.
So your resume has two jobs: it must be machine-readable (so it is not lost in the ATS) and scannable in seconds (so a busy recruiter immediately sees why you fit).
The 10-second test: hand your resume to a friend for 10 seconds, then take it back. If they cannot tell you your target role, your top 3 skills and your best project, the top half of your resume needs work.
The Right Format: Length, Layout, Font & File
| Item | Recommended | Why |
|---|---|---|
| Length | 1 page (fresher), 1–2 pages (experienced) | Forces you to keep only what matters |
| Layout | Single column, reverse-chronological | Parses correctly in every ATS |
| Font | Calibri, Arial, Roboto or Inter, 10–11 pt body, 14–16 pt name | Clean and readable on screen |
| Margins | 0.5–0.75 inch | Fits content without looking crowded |
| Headings | Standard: Summary, Skills, Projects, Experience, Education | ATS looks for these exact words |
| File type | PDF (unless the portal asks for DOCX) | Keeps your formatting intact |
| File name | FirstName-LastName-Java-Developer-Resume.pdf | Looks professional and is easy to find |
Avoid tables, text boxes, icons for contact details, skill bars ("Java 80%"), photos and two-column templates. They look nice but often break ATS parsing – your skills may simply not be read.
Which Sections, in Which Order
The order tells the recruiter what you are strongest at. Put your best evidence first.
| # | Fresher | Experienced (1+ year) |
|---|---|---|
| 1 | Header (contact + links) | Header (contact + links) |
| 2 | Summary (2–3 lines) | Professional Summary (3–4 lines) |
| 3 | Technical Skills | Technical Skills |
| 4 | Projects | Work Experience |
| 5 | Internship / Training (if any) | Key Projects (optional) |
| 6 | Education | Education |
| 7 | Certifications & Achievements | Certifications & Achievements |
Freshers lead with projects because that is the proof of skill. Experienced developers lead with work experience because real production work outweighs personal projects.
Header: Contact Details That Matter
Your header should fit in two or three lines and contain only what a recruiter needs to contact you and verify your work.
Include
- Full name (largest text on the page)
- Target role, e.g. "Java Developer"
- Phone number with country code
- Professional email (name-based)
- City, State
- LinkedIn, GitHub and portfolio links (as clickable text)
Leave out
- Photo, date of birth, gender, marital status
- Father's name, full home address
- Emails like
coolboy123@... - "Resume" or "Curriculum Vitae" as the title
- Declaration and signature at the bottom
RAHUL SHARMA Java Developer +91 98XXX XXXXX | rahul.sharma.dev@gmail.com | Mohali, Punjab linkedin.com/in/rahulsharma-dev | github.com/rahulsharma-dev | rahulsharma.dev
Summary: Your 3-Line Pitch
The summary is the first thing a recruiter reads. Skip generic objectives like "seeking a challenging position in a reputed organisation" – they say nothing. Use this formula instead:
Role + core stack + strongest proof + what you want to do next.
Java developer (B.Tech CSE, 2026) skilled in Core Java, Spring Boot, REST APIs and MySQL. Built 3 full-stack projects including a job portal with JWT authentication, and solved 250+ DSA problems on LeetCode. Looking to start as a backend / Java full stack developer.
Java backend developer with 3 years of experience building Spring Boot microservices for e-commerce and fintech products. Reduced order-API response time by 40% through query optimisation and Redis caching. Strong in REST API design, MySQL, Kafka and AWS deployments.
Every claim in your summary should be backed by something later in the resume – a project, a job, or a profile link.
Technical Skills: Grouped, Honest, Relevant
Group your skills so a recruiter can scan them in two seconds, and list only what you can answer interview questions on. If you write it, expect to be asked about it.
| Group | Example for a Java developer |
|---|---|
| Languages | Java (8/17/21), SQL, JavaScript |
| Backend & Frameworks | Spring Boot, Spring MVC, Spring Data JPA, Hibernate, Spring Security (JWT) |
| Frontend | HTML5, CSS3, Bootstrap, React (basics) |
| Databases | MySQL, PostgreSQL, MongoDB (basics) |
| Tools & DevOps | Git, GitHub, Maven, Postman, Docker (basics), IntelliJ IDEA |
| Concepts | OOP, Data Structures & Algorithms, REST APIs, Multithreading, Design Patterns |
Never pad the list with tools you touched once. One cross-question you cannot answer ("you wrote Kubernetes – how do you scale a deployment?") can cost you the whole interview.
Projects: The Most Important Section for Freshers
For a fresher, projects are your work experience. Interviewers spend most of the technical round on them. A strong project entry has four parts:
- Title + tech stack + links (GitHub and live demo, if any)
- What it does – one line in plain language
- What you built – 2–4 bullets with specific features and technical decisions
- Result – numbers wherever possible (users, records, speed, test coverage)
The bullet formula
Action verb + what you built + technology used + measurable result.
Weak
- Made a job portal project.
- Worked on login and signup.
- Used Spring Boot and MySQL.
Strong
- Built a job portal with Spring Boot, Spring Data JPA and MySQL supporting job posting, search and applications.
- Implemented JWT-based authentication with role-based access for admin, recruiter and candidate.
- Added pagination and indexed search, cutting search time on 10,000 test records from ~2 s to under 300 ms.
Which projects impress recruiters?
- Full-stack CRUD apps with real features – authentication, roles, validation, pagination, file upload.
- REST APIs with proper status codes, exception handling, Swagger/OpenAPI docs and unit tests.
- Something deployed – a live link shows you can take a project to the finish line.
- Projects that solve a real problem for your college, a local business or yourself.
Avoid listing only tutorial clones (to-do app, calculator, weather app) unless you added clearly original features.
Experience & Internships: Show Impact, Not Duties
Write what you achieved, not what your job description said. Start every bullet with a strong action verb and add a number wherever you honestly can.
| Instead of… | Write… |
|---|---|
| Responsible for backend development. | Developed 12 REST endpoints in Spring Boot for the order module, used by 3 internal teams. |
| Fixed bugs. | Resolved 40+ production defects and added JUnit tests that raised module coverage from 45% to 78%. |
| Worked on database. | Optimised slow MySQL queries with indexing and query rewrites, reducing report generation time by 60%. |
Useful action verbs: Built, Developed, Designed, Implemented, Optimised, Automated, Migrated, Integrated, Reduced, Improved, Led, Mentored, Deployed.
For training programmes or internships, list the company, duration and 2–3 bullets about what you built – not the list of topics you were taught.
Education, Certifications & Achievements
Education
List your degree, college, university, years and CGPA/percentage. Freshers can add 12th and 10th in a single line each. Experienced developers can keep only the highest degree.
B.Tech, Computer Science & Engineering — ABC Institute of Technology, Mohali 2022 – 2026 CGPA: 8.1 / 10 Class XII (CBSE) — 88% | Class X (CBSE) — 91%
Certifications that add value
- Certifications backed by a project or exam you can talk about (e.g. Oracle Java certification, AWS Cloud Practitioner, a course where you built a project).
- Coding achievements: LeetCode/CodeChef ratings, hackathon results, competitive programming ranks.
- Open-source contributions or technical blogs.
Skip participation certificates, short webinars and unrelated courses – they dilute the strong items.
Make Your Resume ATS-Friendly
- Read the job description and mirror its exact keywords where they are true for you (e.g. "Spring Boot", "REST API", "Microservices", "MySQL").
- Use standard section headings – Skills, Projects, Experience, Education.
- Keep a single-column layout with no tables, text boxes, headers/footers or images holding important text.
- Write dates consistently, e.g.
Jun 2025 – Aug 2025. - Spell out acronyms once: "Object-Oriented Programming (OOP)".
- Save as a text-based PDF (you should be able to select and copy the text).
Quick parse test: open your PDF, press Ctrl+A, copy and paste into Notepad. If the text comes out jumbled or sections are missing, an ATS will struggle too.
Tailor Your Resume for Every Application
Sending the same resume everywhere is the most common reason for low response rates. Keep one master resume with everything, then create a tailored copy for each role in 10–15 minutes:
- Highlight the skills and tools mentioned in the job description.
- Reorder your skills and projects so the most relevant ones come first.
- Adjust your summary to name the role you are applying for.
- Remove items that are irrelevant to this specific job.
For a service-based company (TCS, Infosys, Wipro, Accenture) emphasise fundamentals, DSA and a clean academic record. For a product company or startup, emphasise depth in projects, deployed work and problem-solving.
Common Resume Mistakes to Avoid
Mistakes
- Spelling and grammar errors
- Generic objective statement
- Listing every technology you have heard of
- Paragraphs instead of bullets
- Broken or private GitHub links
- Inconsistent dates, fonts and spacing
- Fake experience or inflated numbers
Fixes
- Run a spell check and read it aloud once
- Specific summary with role and proof
- Only skills you can defend in an interview
- Short bullets starting with action verbs
- Click every link from the PDF before sending
- One font, one date format, aligned spacing
- Honest numbers you can explain
Background verification is standard in IT companies. Fake experience letters or inflated details can lead to an offer being withdrawn even after you join.
Download Free Java Resume Samples (PDF)
Use these two samples as a reference for structure, wording and spacing. Replace every detail with your own – never copy projects or numbers you have not done.
Java Fresher Resume
One-page, ATS-friendly resume for a B.Tech/MCA fresher with skills, 2 internships, 3 projects, certifications and achievements.
Download PDFJava Experienced Resume
One-page resume for a Java backend developer with 3 years of experience – impact-driven work bullets, internship, key projects, certifications and achievements.
Download PDFFinal Checklist Before You Hit "Apply"
- Fits on one page (fresher) and passes the 10-second test.
- Target role is visible at the top.
- Summary names your stack and your strongest proof.
- Skills are grouped and every item is interview-ready.
- 2–4 projects with tech stack, links and measurable bullets.
- Keywords from the job description are included honestly.
- All links (LinkedIn, GitHub, live demo) open correctly.
- No spelling mistakes; consistent fonts, dates and spacing.
- Saved as
FirstName-LastName-Java-Developer-Resume.pdf.
Frequently Asked Questions
Should a fresher resume be one page or two pages?
One page. Recruiters skim quickly, and a fresher rarely has enough relevant material to fill two pages without padding. Move to two pages only after a few years of real work experience.
Should I add my photo, date of birth or father's name to my resume?
No. For software jobs these details do not help your selection and take space away from skills and projects. Name, phone, email, city, LinkedIn and GitHub are enough.
Is a Canva or two-column resume template okay?
It is risky. Many applicant tracking systems read two-column layouts, tables, icons and text boxes in the wrong order or skip them. A clean single-column layout with standard headings is the safest choice.
How many projects should I add as a fresher?
Two to four strong projects are better than eight small ones. Pick projects you can explain in depth – the problem, your design, the technologies and what you would improve.
Should I mention CGPA if it is low?
If the company or job post asks for it, mention it honestly. Otherwise you can leave it out and let your projects and skills carry the resume. Never round up or change marks.