If you studied mechanical, civil, electrical or electronics engineering and want a core job, your resume has one job. It must show that you have already done a little of the work. A design engineer role, a site engineer role or an embedded trainee role is filled by someone who looks ready to learn fast on a real plant, site or lab bench.
Most fresher resumes hide that evidence. The project gets one line, the training becomes "Completed 30 days training", and the skills list names eight software packages. This guide fixes each part.
The short answer
- Put branch evidence near the top. After education, show your final-year project, industrial or in-plant training and internships before anything else.
- Write each item as work. Say what you did, with which tool or method, and what came out of it.
- List only the tools you can use when asked. A short, honest tool list beats a long one.
- Add your GATE score if it helps the roles you are applying to. Leave it off where it adds nothing.
- Keep two versions if you are applying to both core companies and IT service companies. Change the order and emphasis. Never change the facts.
Put branch evidence above everything else
A good order for a core-branch fresher on one A4 page:
- Name, phone, email, city, and a LinkedIn or portfolio link if you have one
- A two-line summary naming your branch and the kind of role you want
- Education, with scores and their scale
- Final-year project
- Industrial training, in-plant training and internships
- Tools and technical skills
- Site visits, lab work, certifications you actually completed
- Positions of responsibility and activities, kept short
For how to write the education lines, see how to show 10th, 12th and CGPA. If your college's placement cell gives you a fixed format, use it inside the campus process.
Write training and projects as work, not attendance
A month of in-plant training often means watching more than doing. That is fine. Write what you observed, what you did yourself and anything you produced, even a small report.
Illustrative example (fictional person). Rohan is a final-year mechanical student who did four weeks of in-plant training at a forging unit.
Before:
- In-plant training at ABC Forgings Pvt Ltd, 30 days.
After:
- In-plant trainee, ABC Forgings Pvt Ltd, Pune (June 2026, 4 weeks). Followed the closed-die forging line from billet cutting to heat treatment. Recorded die-change times over 10 shifts and prepared a one-page summary for the shift supervisor. Learnt to read the plant's process sheets and inspection reports.
The "after" version claims no improvement Rohan did not make. But an interviewer now has three things to ask about, and Rohan can answer each.
The same pattern works for the final-year project. Name the problem, your part in the team, the method or tool, and the result, including a result that fell short.
Illustrative example (fictional person). Divya, a civil student, before and after:
- Before: Project on design of G+3 residential building.
- After: Final-year project: structural design of a G+3 residential building (team of 4). Modelled the frame and ran load combinations in STAAD.Pro. I owned the slab and beam design and checked the results by hand for two members. Drew the column layout in AutoCAD.
In a team project, say which part was yours. Interviewers ask, and a vague answer costs more than a small honest one.
For ECE and EEE students, the same rule applies to a mini-project on a microcontroller board or a power electronics lab setup. Say what the circuit or code did, what you built or tested, and how you checked it worked.
Site and industrial visits. A one-day visit is not training. Keep visits in a short line of their own, such as "Industrial visits: 220 kV substation; ready-mix concrete plant". Add a detail only if you took something real from it.
Same story. A little more breathing room.
Switch the layout. Watch how spacing and hierarchy change the way this sample reads.
Alex Morgan
Product designerProfile
Product designer focused on making complex workflows easier to understand.
Experience
Product Designer · Example Studio
- Mapped the onboarding journey with the support team.
- Designed and tested a clearer account setup flow.
- Documented reusable components for the engineering team.
Skills
Interaction design · Prototyping · Design systems
Everything is asking for attention.
Closely packed headings and text leave fewer visual signposts. Try the other treatment.
Tools: list only what you can use in an interview
Core job posts often name specific software. Mechanical posts may ask for AutoCAD, SolidWorks, CATIA or ANSYS. Civil posts may ask for AutoCAD, STAAD.Pro or estimation in Excel. ECE and EEE posts may ask for MATLAB, a circuit simulator or an embedded toolchain. These are only examples. The job post tells you what that employer wants.
The rule is simple. If a tool is on your resume, you should be able to open it in an interview and do a basic task. Assume someone will ask.
A clear way to show depth without inflating it:
| Tool | How to write it |
|---|---|
| Used in your project or training | "SolidWorks: modelled and assembled the gearbox housing for my final-year project" |
| Learnt in a course or lab, used a few times | "ANSYS Workbench: static structural analysis in a college lab course" |
| Watched someone use it | Leave it off |
If a course gave you a certificate, list it only if you completed it, with the issuer and year.
GATE score: when it belongs
The GATE 2026 organising institute says a GATE score stays valid for three years from the result date. It also says several public sector undertakings (PSUs) use GATE scores for recruitment (GATE 2026, IIT Guwahati). Each PSU sets its own rules in its own notice, so read the notice, not a summary of it.
On a resume, a GATE line helps when:
- The role or organisation mentions GATE, or
- The score is a clear point of strength for a technical role.
Write it the way the scorecard shows it: paper, year, score and rank. For example (fictional): "GATE 2026, Mechanical Engineering (ME): score 612, All India Rank 2,340". Put it in the education block or just below it.
You can leave it off for IT service roles or where it adds nothing. If you spent a year preparing for GATE after graduating, how to show exam-preparation time covers the timeline.
Core roles and IT service roles: two versions, same facts
Many core-branch students apply to core companies and IT service companies in the same season. That is normal. The mistake is sending one resume to both.
| Part of the resume | Core version | IT service version |
|---|---|---|
| Summary | "Mechanical engineering fresher seeking a design or production role" | "Engineering graduate seeking a software or support trainee role" |
| First section after education | Final-year project and in-plant training | Programming coursework, coding projects, any certifications you finished |
| Tools | Branch tools you can use | Programming languages and tools you can use |
| Branch project | Full detail | Short, stressing problem-solving and teamwork |
Both versions must say the same thing about your degree, scores, dates and training. Only the order and the amount of detail change. For keeping versions straight across many applications, off-campus applications suggests a simple naming system. For the wider B.Tech fresher picture, see the B.Tech fresher resume guide.
If you use Guul, tailoring a resume to a job description shows which tools and terms a particular post mentions. You can then check each one against what you have truly done before adding it.
Your experience. A fresh canvas.
Try a different look. These are actual Guul template previews, with illustrative sample content.
A clean slate. Literally.
One column, distinct sections, and room for your experience to lead. A simple place to start.
Make this layout yours ↗The builder opens with your selected template.Replace all sample details with your own experience.Explore the resume lookbook →
A checklist before you apply
- Your final-year project says which part was yours.
- Each training or internship line says what you did or produced, not only the dates.
- Every tool listed is one you could use in front of the interviewer.
- Site visits are short and separate from training.
- A GATE score, if shown, matches the scorecard exactly.
- Dates, scores and company names are the same in the core and IT versions.
- The page is one A4 sheet, with standard headings such as "Projects" and "Training".
Once your draft is ready, Guul's resume checker explains each finding in plain words, so you can see whether dates, headings and project lines came out as you intended.
Then do one last thing. Read each line aloud and ask yourself, "Could I talk about this for two minutes?" Anything that fails that test needs more detail or needs to come out.
