Resume format for B.Tech freshers in India
One page, projects above everything else, and a skills block a recruiter can match to the job description in seconds.
Written for final-year and recently graduated engineering students applying on campus and off campus.
The section order that works for engineering freshers
A B.Tech fresher resume is read for evidence you can build something. Put the evidence first and the credentials second, because the degree is the one thing every other applicant also has.
- Contact line: name, phone, email, city, GitHub or portfolio link. No photo, no full address.
- Two-line target summary naming the role and your strongest stack. Skip it if it would only repeat the header.
- Technical skills, grouped as languages, frameworks, tools, and databases.
- Projects: two to three, each with what it does, your stack, your specific contribution, and an outcome.
- Internships and training, then education, then certifications, then positions of responsibility.
How to handle CGPA, backlogs, and graduation year
These are the fields campus and off-campus recruiters filter hardest on, so decide them deliberately rather than leaving them ambiguous.
- List CGPA if it is 7.0 or above. Convert to percentage only when the application asks for percentage.
- Cleared backlogs do not belong on a resume. Active backlogs are worth disclosing only when a form asks.
- Always show graduation month and year. A missing year reads as a gap you are hiding.
- Class 12 and 10 percentages belong on the resume only for campus drives that screen on them.
Writing project bullets that survive a technical screen
The failure mode is a project described as a feature list. Recruiters cannot tell effort from a feature list, and interviewers will open the repository.
- Name the problem before the tech: "Reduced attendance marking from 10 minutes to under 1" beats "Built an attendance app".
- Say what you personally built when it was a team project. "Owned the auth flow and Postgres schema" is credible; "worked on the app" is not.
- Add scale where it exists: rows processed, users tested with, accuracy achieved, latency reduced.
- Link the repository or a live deployment. An unlinked project invites doubt.
Core engineering versus IT roles
Mechanical, civil, electrical, and ECE freshers applying to IT roles need a different emphasis than those staying in core, and one resume rarely serves both well.
- Core roles: lead with design tools (AutoCAD, SolidWorks, CATIA, MATLAB, ETAP), plant or site training, and the standards you worked to.
- IT roles from a core branch: lead with the stack, courses, and shipped projects, and let the branch be a line in education rather than the story.
- Keep two versions rather than one hybrid. A resume that hedges reads as unfocused to both panels.
Certifications worth listing, and ones that add noise
Certifications help when they signal depth a project cannot. They hurt when they pad a page with participation.
- Worth listing: NPTEL with score, AWS or Azure fundamentals, GATE score if competitive, a recognised specialisation completed end to end.
- Not worth listing: one-hour webinars, unverifiable internships, generic workshop attendance certificates.
- Group them in one line each. A certification section longer than your projects section inverts the signal.
Save your resume improvements before you lose momentum
Search brought you here because the resume needs fixing. Create a free account, save the draft, and continue with the score checker or builder.
Frequently asked questions
Should a B.Tech fresher resume be one page?
Yes. With no full-time experience there is rarely enough proof to fill two pages, and a second page pushes your projects below the fold on the recruiter side.
Where should CGPA go on a B.Tech fresher resume?
In the education section, on the same line as the degree and graduation year. It does not belong in the header or the summary.
How many projects should an engineering fresher list?
Two or three described properly. Six shallow project titles are weaker than two with your contribution, stack, and outcome spelled out.
Is a career objective needed for a B.Tech resume?
Only if it names a target role and a real skill. A generic objective about seeking a challenging position uses your most valuable line to say nothing.
Start your resume free
Save progress and continue later