Resume Guide

How to build a resume that passes ATS filters, earns recruiter attention, and accurately represents your capabilities — in under one page.

Foundation

What a Fresher Resume Should Accomplish

Your resume has one job: get you to the interview. It is not a biography, a portfolio, or a comprehensive record of everything you have ever done. It is a carefully curated document that answers one question for the recruiter: "Should we invest 30-60 minutes interviewing this person?"

For freshers and early-career engineers, this means demonstrating three things:

Technical competence — You have the foundational skills to do the job.
Initiative — You have built things beyond coursework that show genuine interest.
Communication clarity — You can describe complex work in concise, specific terms.

Everything on your resume should serve one of these three purposes. If it doesn't, it doesn't belong there.

Structure

Recommended Resume Structure

For freshers and graduates with less than 2 years of experience, use this structure. Keep it to one page — no exceptions.

HeaderName, email, phone, LinkedIn, GitHub. No photo, no address, no date of birth. Use a professional email (firstname.lastname@gmail.com, not gamer_tag_2003@gmail.com).

EducationUniversity, degree, graduation year, CGPA (if above 7.0). Relevant coursework only if it directly maps to the role. No high school details unless you have no college degree.

Experience (if any)Internships, freelance work, open source contributions. Use action verbs and quantify impact: "Reduced API response time by 40% by implementing Redis caching" is stronger than "Worked on backend optimization."

Projects (2-3 maximum)Your most impressive technical projects. Each entry should include: what it does, what you built, which technologies you used, and one measurable outcome or technical achievement.

SkillsProgramming languages, frameworks, tools, databases. List only technologies you can confidently discuss in an interview. Remove anything you last used more than a year ago.

ATS

Passing Applicant Tracking Systems

When you apply through a company's career portal (which is where every Synckra Apply button leads), your resume is typically processed by an ATS before a human sees it. Here is how to ensure your resume survives:

⚡

ATS-Friendly Practices:

Use a simple, single-column layout — Multi-column designs, text boxes, headers/footers, and tables break most ATS parsers.
Submit as PDF — Unless specifically asked for .docx. PDF preserves formatting across systems.
Use standard section headings — "Experience," "Education," "Skills," "Projects." Creative headings like "My Journey" confuse parsers.
Mirror job description keywords — If the listing says "React.js," write "React.js" on your resume, not "ReactJS" or "React." ATS matching is often literal.
No images, charts, or graphics — ATS cannot read visual elements. Your skills chart is invisible to the machine.
No special characters in filenames — Name your file "FirstName_LastName_Resume.pdf".

Mistakes

Common Resume Mistakes

🚫Objective Statement"Seeking a challenging role..." wastes space. Everyone wants a challenging role. Remove it entirely.

🚫Listing Every CourseDon't list all 40 courses from your degree. Include only 3-4 directly relevant to the role.

🚫Skill Ratings"Python: ★★★★☆" is meaningless. Either you can use the technology professionally or you cannot. Remove self-ratings.

🚫Vague Descriptions"Worked on a team project" tells the recruiter nothing. Use: "Built a real-time chat app using Socket.io serving 200+ concurrent users."

🚫Two+ PagesFreshers do not need multi-page resumes. If you cannot fit it on one page, you are including irrelevant information.

🚫Lying or ExaggeratingEvery claim on your resume is fair game in an interview. If you cannot defend it under questioning, do not include it.

For guidance on how to discuss your projects effectively once you get the interview, see the Interview Preparation guide. For understanding which skills to prioritize on your resume, check the Skills Guide.

FAQ

Common Questions

Should I use a resume template or design my own?

Use a clean, proven template. Overleaf (LaTeX) templates like Jake's Resume or Deedy are widely recommended for tech roles. The goal is clarity, not aesthetics. Recruiters spend 6-10 seconds on initial screening — make those seconds count with clear formatting, not creative design.

What if I have no internship experience?

Focus on projects. Build 2-3 substantial projects that solve real problems, use modern technologies, and have measurable outcomes. Contributions to open source repositories also count as practical experience. Many successful engineers landed their first role on projects alone.

Should I include my CGPA?

If it's above 7.0/10 (or 3.0/4.0), yes. If it's lower, omit it. Some companies have CGPA cutoffs in their screening process, but many — especially startups and product companies — don't weigh it heavily if your projects and skills are strong.

How often should I update my resume?

Update it every time you complete a meaningful project, learn a new technology that you can use professionally, or gain new experience. Before each application cycle, review and tailor it to the types of roles you are targeting.