Resume for Internship for Engineering Students (2026 Format)

Quick answer: Use a one-page, single-column resume with a clean header, education, skills, two or three relevant projects and any real experience. Put proof links beside your projects, use standard section headings, export as PDF, and tailor the top third to the role. No photo, no objective paragraph, no tables.

1Page

2–3Projects

6–10sFirst scan

7Day rebuild

Need proof for your resume?The free 11-day AI challenge ends with portfolio projects you can link, explain and defend in an interview.

Build free

What recruiters scan in the first six seconds

Recruiters are not reading your resume from top to bottom. They are scanning for four signals:

Role fit: Does the headline and top third match the internship?
Proof: Are there projects, links or results, or only claims?
Clarity: Can they understand what you did in one pass?
Contact: Is your email, phone and portfolio easy to find?

Everything else is secondary. A resume that wins is not the most beautiful one. It is the easiest one to say yes to.

The one-page engineering internship resume format

Use this order for a standard internship application. If you have no experience, move Projects above Experience.

Section	What to include	Space
Header	Name, phone, email, city, LinkedIn, GitHub/portfolio	3–4 lines
Headline	Target role + one proof skill, e.g. “Second-year CSE student · Python · Web projects”	1 line
Education	Degree, college, university, dates, CGPA (if strong), relevant coursework	2–3 lines
Skills	Languages, tools, frameworks, domains. Only what you can discuss.	3–4 lines
Projects	2–3 projects with role, stack, action, result and link	8–14 lines
Experience	Internships, freelance, part-time, volunteering, open source	4–8 lines
Achievements	Hackathons, rankings, certifications, scholarships — only if relevant	2–4 lines

Keep margins between 0.5 and 0.8 inches, font size 10–11.5 pt, and line spacing around 1.15. White space is not wasted space; it makes the page scannable.

Header details

Use a professional email: `firstname.lastname@...`, not a childhood nickname.
Add city and state, not your full street address.
Link to GitHub or a portfolio if it is presentable. Do not link a dead profile.
Use a clickable phone number and email in the PDF.

Education details

Degree, branch, college and graduation year.
CGPA if it is reasonably strong for your target; never round up dishonestly.
Relevant coursework only if it supports the role. Do not list every subject.
Class XII percentage is optional; include it only if it helps and space allows.

Engineering internship resume sample (text version)

This is a format sample, not a real student. Copy the structure, not the claims.

AARAV SHARMA Bengaluru, Karnataka · +91 98XXXXXX00 · aarav.sharma@email.com linkedin.com/in/aaravsharma · github.com/aaravsharma SECOND-YEAR CSE STUDENT · PYTHON · WEB DEVELOPMENT EDUCATION B.Tech, Computer Science and Engineering — [College Name], [University] 2024–2028 · CGPA: 8.4/10 Coursework: Data Structures, DBMS, Operating Systems, Web Development SKILLS Languages: Python, C, JavaScript, SQL Tools: Git, GitHub, VS Code, Figma, Postman Web: HTML, CSS, React (basic), Node.js (basic) PROJECTS StudyTrack — Attendance and study planner | React, Node.js, SQLite - Built a planner that lets students track attendance and generate a weekly study schedule. - Added local data storage and a dashboard that shows subject-wise attendance percentage. - Live demo: [link] · Code: [link] Campus Events — College event listing page | HTML, CSS, JavaScript - Designed a responsive event page used by 200+ students during a two-day college fest. - Added search, category filters and a mobile layout; reduced event lookup time from minutes to seconds. - Code: [link] EXPERIENCE Open-source contributor — [Project Name] | Remote · 2026 - Fixed three documentation issues and added one test for the login flow. - Worked with maintainer feedback and submitted pull requests on GitHub. Volunteer — College coding club | 2025–2026 - Coordinated two beginner workshops and mentored 15 juniors on Python basics. ACHIEVEMENTS - Finalist, [College] Hackathon 2026 — built a campus lost-and-found prototype in 24 hours. - Completed [Course Name] with a project certificate, [Year].

Notice what is missing: photo, full address, “hardworking team player”, a list of ten soft skills, and five projects nobody can explain. The page is dense but scannable, and every project has a link.

How to write project bullets that survive an interview

Weak bullets describe what the project is. Strong bullets show what you did, how you did it and what changed.

Weak	Strong
Made a study app using React.	Built a study planner in React and SQLite that lets students track attendance and generate a weekly schedule.
Worked on machine learning project.	Trained a logistic regression model on 5,000 rows to classify support tickets; improved validation accuracy from 72% to 81% by cleaning labels and adding text features.
Good at teamwork and communication.	Coordinated a four-person team, split tasks, and shipped a working prototype within 24 hours at a college hackathon.

Use this formula for each bullet:

Action: built, designed, automated, analysed, reduced, improved.
How: the tool, method or constraint that makes the work credible.
Result: a number, a time saved, a user count, a working link, or a clear outcome.

If you do not have a number, use a concrete outcome: “shipped a live demo”, “used by 30 classmates”, “passed 40 test cases”. Never invent metrics.

ATS rules for Indian engineering students

Applicant Tracking Systems parse text. If your resume is a design project, the parser may lose your name, skills or education.

Use a single-column layout. Avoid two columns, text boxes and tables.
Use standard section headings: Education, Skills, Projects, Experience, Achievements.
Use a common font such as Arial, Calibri or Inter at 10–11.5 pt.
Export as PDF unless the application asks for DOCX. Keep the text selectable.
Put keywords from the job description in the resume where they are true.
Use the full term and the abbreviation once: “Natural Language Processing (NLP)”.
Name the file `Firstname_Lastname_Role.pdf`.
Test by copying the PDF text into a plain text editor. If it becomes gibberish, fix the layout.

No keyword stuffingHidden white text, repeated keywords and skill lists you cannot defend will get you rejected in the interview or flagged by the ATS. Match the role honestly.

No internship experience? Build a resume anyway

You are not starting from zero. You have coursework, projects, labs, clubs, volunteering, hackathons and maybe freelance work. The job is to reframe them as evidence.

Coursework project: add a README, a demo and a result. It becomes a project section.
Hackathon: describe the problem, your role, the stack and what shipped in the time limit.
Club or event: quantify the outcome — attendees, posts, matches, participants, hours saved.
Freelance: treat it as experience. Name the client type, the deliverable and the result, without confidential details.
Open source: list merged pull requests, issues fixed and tests added. Link the profile.
Certification: include it only if you built something with it. A certificate alone is not proof.

If you have nothing yet, spend one week building a small project before sending another application. The resume improves when the evidence improves.

10 resume mistakes that cost internships

No target role. A generic resume is read as a generic candidate.
Photo and personal details. Not required, and they can hurt ATS parsing.
Objective paragraph. “Seeking a challenging opportunity” says nothing.
Skill list without proof. Listing React with no React project invites a hard interview.
Tutorial clones only. Add one original feature or a real user.
No links. A project that cannot be opened is a claim, not proof.
Walls of text. Recruiters scan; bullets and white space help.
Typos and inconsistent dates. They signal low attention to detail.
Fancy template. Columns, icons and charts often break parsing.
Same resume for every role. Tailoring the top third takes ten minutes and changes response rates.

Your 7-day internship resume rebuild

Do not rewrite everything from scratch. Rebuild one section per day and finish with a tested PDF.

Showing 7 of 7 days

Day 1

Audit the current resume

Mark every line that is a claim without proof. Delete the objective, photo and soft-skill list.

Output: a marked-up old resume Content

Day 2

Choose the target role

Pick one role and copy five keywords from a real job description. These become your headline and skill priorities.

Output: one role + five keywords Content

Day 3

Rewrite two project bullets

Use action, how and result. Add a number only if it is real. Cut anything you cannot explain for two minutes.

Output: four strong bullets Proof

Day 4

Add proof links

Publish the GitHub repo, add a README, and include a live demo link. Fix broken links before sending.

Output: two working links Proof

Day 5

Tailor the top third

Change the headline, reorder projects and add the JD keywords where they are true. Keep it one page.

Output: a role-specific draft Content

Day 6

Run an ATS and readability test

Copy the PDF text into a plain editor, check the reading order, and ask a friend to scan it for six seconds.

Output: a parser-safe PDF Test

Day 7

Final review and export

Check dates, spelling, phone, email and file name. Export one final PDF and use it for the next 10 applications.

Output: a send-ready resume Test

How to tailor your resume in 10 minutes

Copy the job description into a document.
Highlight the five most repeated skills or responsibilities.
Check that each one appears somewhere in your resume with evidence.
Move the most relevant project to the top.
Change the headline to match the role title.
Remove one less relevant item if the page overflows.
Save a separate PDF with the company name in the file.

This is not lying. It is choosing which true things to show first.

Resume checklist before you hit send

One page, single column, standard headings.
Name, phone, email, city, LinkedIn and portfolio are correct and clickable.
Headline matches the role.
Education includes degree, branch, college and dates.
Two or three projects with action, how and result.
Every project has a working link.
Skills are honest and relevant.
No photo, objective, full address or soft-skill filler.
No typos, inconsistent dates or weird fonts.
PDF text is selectable and parses cleanly.
File name is `Firstname_Lastname_Role.pdf`.
A friend can explain what you do after six seconds.

Frequently asked questions

How long should an engineering internship resume be?

One page is the standard for internships and for students with less than two years of experience. A second page is justified only if you have substantial research, publications or multiple relevant internships. Recruiters scan quickly, so density and relevance matter more than length.

Should I include a photo on my internship resume?

For most Indian engineering internships, no. A photo is not required, can create bias, and may confuse ATS parsing. Use a clean text-only header with your name, phone, email, city, LinkedIn and GitHub or portfolio.

What if I have no internship experience?

Lead with projects, coursework, hackathons, open-source contributions, volunteering or freelance work. A well-documented project with a live link and a clear result is stronger than an unrelated internship. Do not invent experience; reframe real work.

Should I include my CGPA on my resume?

Include it if it is reasonably strong for your target roles, and never inflate it. Many formal programmes screen on CGPA, so omitting it can create questions. If your CGPA is low, focus on projects and skills, but be prepared to answer if asked.

What is an ATS-friendly resume format?

Use a single-column layout, standard headings such as Education, Skills, Projects and Experience, selectable text, no tables or text boxes, and a simple font. Export as a PDF unless the application asks for a Word file. The goal is to be readable by both software and a busy recruiter.

How many projects should a student resume have?

Two or three relevant projects are enough for a one-page resume. Choose projects that match the role, can be explained in an interview, and have a link or demo. One deep project is better than five tutorial clones.

Should I write a resume objective?

Usually not. A generic objective wastes the most valuable space at the top. Use that space for a targeted headline, a strong project or a skills summary that tells the recruiter what role you want and what you can do.

How do I tailor my resume to a job description?

Extract the five most important skills and responsibilities from the JD, then make sure your resume shows evidence for each one through projects, coursework or experience. Use the same language where it is honest, and reorder sections so the most relevant proof appears first.

Can I use the same resume for every internship?

You can keep one master resume, but send a tailored version for each role. Change the headline, reorder projects and adjust keywords. A generic resume is easy to spot and usually loses to a candidate who addressed the specific role.

What file name should I use for my resume?

Use a clear name such as Firstname_Lastname_Resume.pdf or Firstname_Lastname_Software_Intern.pdf. Avoid final_final_v3.pdf, spaces, emojis and unusual characters. A clean file name signals attention to detail.

Keep reading

TaskVeda Team
We help Indian students become job-ready with AI skills, live bootcamps, internships and portfolio-first learning.

Last updated: 21 October 2026