B.Tech Fresher Resume for Campus Placements

Placement season gives you very little time to impress, and most B.Tech resumes look alike. This guide shows how to organise yours so your real work stands out, whatever your branch or CGPA.

Updated October 2026 · By QuickResume · Free · No sign-up

Start with the right order

Your college may give a fixed placement format. If it does, follow it. If you are free to choose, this order works for most engineering students:

1. Name and contact details, with LinkedIn and GitHub links
2. Education (B.Tech, class XII, class X)
3. Technical skills
4. Projects
5. Internships or training
6. Coding profiles and competitions
7. Certifications
8. Positions of responsibility and achievements

If you have a strong internship, move it above projects. If you have no internship, give projects the most room. The general principle is in our resume format for freshers guide: lead with whatever proves your ability best.

Writing CGPA and marks

Many companies set a minimum CGPA or percentage for campus drives, but the cut-off differs by company and year, so always read each company's notification. Do not assume a number applies everywhere.

• Write your CGPA on the scale your university uses, for example "7.8 / 10", and give the percentage equivalent only if your university provides a conversion formula.
• Use the same marks that appear on your official records. Placement teams verify them, and a mismatch can cost you an offer.
• If your CGPA is lower than you would like, do not hide it or alter it. Strengthen the rest of the page with projects, coding practice and internships.
• If you have active backlogs, answer honestly if asked. Some companies do not allow them, so check eligibility before applying.

Skills ordering

Arrange skills so the most relevant ones for the job come first. A recruiter at a software company does not need your AutoCAD skills at the top; a core mechanical company does.

Skip progress bars and self-ratings. List only what you have used in a project, assignment or lab. A skills list of 30 items invites 30 questions. More guidance is in skills for resume.

Projects: a worked example

Projects are the main proof for a fresher. Use three bullets: what the project does, how you built it, and what you can show for it (a live link, test results, a user count that is true).

Say which parts you built if it was a team project. Avoid the generic "calculator" or "to-do list" entries unless you added something unusual. Non-CSE students can use the same pattern: a mechanical student might describe a design, the software used for simulation, and what the test showed. See projects section for resume for more.

Coding profiles and competitions

Include links to profiles you actually use, such as GitHub, LeetCode, CodeChef or Codeforces. Add a short line only if it is true and checkable, for example "Solved 250+ problems on LeetCode, mostly arrays, strings and trees" with your current count. Do not round up.

A GitHub profile with a few well-described repositories and a README for each is better than twenty empty ones. Make sure at least the pinned repositories have clear titles and short descriptions. If you took part in a hackathon, mention the event, your role and what you built, not only the rank.

Internships and certifications

Even a short internship or virtual internship is worth including. Write the company, duration, what you worked on and one result or deliverable. If the work was mainly learning, say what you built during it rather than inflating your role. See resume for internship if you are still applying.

For certifications, list only those relevant to the role, with the provider and year. Five related certificates are more convincing than fifteen random ones. If a certificate matters for the job, you should be able to explain what it taught you.

Branch-wise emphasis

If you are switching from a core branch to IT roles, make this obvious in your skills section and projects rather than leaving recruiters to guess.

Final checks before the drive

1. One page, PDF, readable on a phone.
2. Every link opens without a login.
3. Marks and dates match your official records.
4. No spelling errors in project names or tools (for example, "JavaScript", not "Java script").
5. No photo or personal details unless your placement format requires them.
6. File name is clear, such as Name_Branch_Resume.pdf.

You can test the file with an ATS resume checker to make sure the text reads in the right order.

Frequently asked questions

Related guides