Use this template
Add your own experience and make this layout yours.
dev-engineering
Engineering Intern
Resume Example
4.5 / 5
Why This Template Works
This resume format is optimized for Applicant Tracking Systems (ATS) by including relevant keywords such as 'backend development', 'system integration', and 'microservices'. The inclusion of a professional summary highlights key skills and experiences that are crucial for an Engineering Intern position, making it stand out to recruiters. Additionally, the use of consistent formatting and clear sections makes it easy for both ATS algorithms and human readers to parse and understand.
Instant Resume Score
Check Your Engineering Intern Resume Score
Upload your resume for an instant ATS score and practical, role-specific improvements.
- No Signup Required
- Private by Default
- Usually under 30 sec
Your resume
One step to your resume score
Add your resume to run a free score and get prioritized fixes.
How to Write This Resume
Expert guidelines and best practices for each section of your resume.
01
Contact
Contact
First Name Last Name City, State, Zip Code Phone Number | Email Address LinkedIn Profile URL | Portfolio URL (Optional)
General Guidelines
Your contact information is the first section recruiters see. Keep it concise and professional. Ensure your email address is appropriate (e.g., [email protected]). Include your LinkedIn profile for a comprehensive view of your professional journey. A portfolio or personal website is recommended for creative, technical, or design roles.
Avoid This
Do not include your full physical address (street number/name) for privacy reasons. Avoid including personal details like marital status, age, photo, or social security number unless specifically required in your country. Don't use unprofessional email addresses.
Real Examples
Don't
Emily Wang 1234 Random St, Apt 56 San Francisco, CA 94101 [email protected] github.com/emilywdev
Do
Emily Wang San Francisco, CA (555) 987-6543 | [email protected] linkedin.com/in/emily-wang | github.com/emilywdev
Quick Tips
- Use a professional email address (firstname.lastname format)
- Ensure your voicemail is set up and professional
- Double-check your phone number and email for typos
- Make your LinkedIn URL custom (linkedin.com/in/yourname)
- Include GitHub link for developer roles
02
Summary
Summary
Professional Title Result-oriented [Role Name] with [Number] years of experience in [Key Skills/Industries]. Proven track record of [Major Achievement]. Skilled in [Key Technologies/Skills]. Committed to delivering [Specific Value] for [Target Industry/Company type].
General Guidelines
A professional summary is your elevator pitch. It should be 3-5 sentences long, summarizing your experience, key skills, and major achievements. Tailor it to the job description by using relevant keywords. Focus on what makes you unique and the value you bring to potential employers.
Avoid This
Avoid generic objectives like 'Looking for a challenging role to grow my skills.' Recruiters want to know what value you bring to them, not what you want from them. Don't use first-person pronouns (I, me, my). Keep it concise and impactful.
Real Examples
Compare a weak objective with a strong professional summary.
Don't
Objective: I am a hard-working student looking for an internship where I can learn and grow.
Do
Engineering intern with hands-on experience building Python APIs, Docker-based development environments, and SQL-backed tools. Improved CI feedback time from 45 to 20 minutes and added tests that increased coverage by 30%. Comfortable collaborating with senior engineers, documenting technical decisions, and learning unfamiliar systems quickly.
Quick Tips
- Keep the summary to 3-4 lines and target the internship description.
- Mention the stack you can actually explain in an interview.
- Lead with projects, internship work, or coursework that proves practical ability.
- Avoid broad claims such as 'passionate problem solver' unless the sentence also shows evidence.
03
Skills
Skills
Technical Skills - Languages: [List] - Frameworks: [List] - Tools: [List] Soft Skills - [Skill 1], [Skill 2], [Skill 3]
General Guidelines
Group your skills logically (e.g., Languages, Frameworks, Tools). Focus on hard skills relevant to the job. List skills in order of proficiency or relevance. Soft skills are better demonstrated through bullet points in your experience section rather than a bare list.
Avoid This
Do not list skills you are not comfortable using in an interview. Avoid using progress bars or percentages to rate your skills (e.g., "Java: 80%"). Do not include outdated technologies unless specifically required.
Real Examples
Practical example showing do's and don'ts for skills
Don't
Java: 65%, Python: Beginner, C++: Intermediate
Do
Python - Proficient in core concepts and libraries. JavaScript - Experienced with React and Node.js frameworks.
Don't
Microsoft Office Suite, Photoshop, Dreamweaver
Do
Git, Docker, AWS
Quick Tips
- Start your skills section by categorizing them into Technical Skills (such as Languages, Frameworks, Tools) and Soft Skills.
- Prioritize technical skills that align with the job requirements of an Engineering Intern.
- Ensure that soft skills are integrated within experience descriptions rather than listed separately in a skills section.
- Avoid listing outdated or irrelevant technologies unless they were used recently or for specific projects.
04
Experience
Experience
Job Title | Company Name | Location Month Year – Month Year - Action Verb + Context + Result (Quantified) - Led [Project] resulting in [Outcome]... - Collaborated with [Team] to implement [Feature]...
General Guidelines
This is the core of your resume. Use reverse-chronological order (most recent first). Start each bullet with a strong action verb. Focus on achievements and impact, not just duties. Use numbers to quantify your impact (dollars, percentages, time saved, users affected). Show progression and increasing responsibility.
Avoid This
Avoid passive language like 'Responsible for...' or 'Tasked with...'. Don't list every single daily task; focus on significant contributions and measurable outcomes. Avoid jargon that recruiters outside your field won't understand.
Real Examples
Practical example showing do's and don'ts for experiences
Don't
Worked on a microservices project involving Docker containers.
Do
Containerized two backend services with Docker, cutting deployment preparation time by 50%.
Don't
Fixed bugs in the system's codebase.
Do
Resolved 20+ defects in a legacy workflow application, saving more than 40 hours of manual QA effort.
Quick Tips
- Start each bullet with the engineering action you performed.
- Use realistic measures such as tests added, bugs fixed, latency reduced, or review time saved.
- Show collaboration with mentors, designers, QA, or product teammates when relevant.
- Keep intern achievements credible and tied to the tools you used.
05
Education
Education
Degree Name | University Name | Location Month Year – Month Year - Relevant Coursework: [Course 1], [Course 2] - Honors/Awards: [Award Name] - GPA: X.X (if above 3.5)
General Guidelines
List your highest degree first. If you have significant work experience, keep the education section brief. Include your GPA only if it is above 3.5 or if you are a recent graduate. Highlight relevant coursework, academic projects, honors, or leadership roles.
Avoid This
Do not include high school details if you have a college degree. Avoid listing every single course you took; select only the most relevant ones. Don't include graduation dates from decades ago if age discrimination is a concern in your field.
Real Examples
Practical example showing do's and don'ts for educations
Don't
Bachelor of Science | XYZ University | San Francisco, CA September 2018 – May 2023 - Courses: Intro to Programming, Data Structures & Algorithms, Calculus I, Calculus II, Calculus III, Physics for Scientists and Engineers
Do
Bachelor of Science in Computer Engineering | San Francisco State University | San Francisco, CA September 2018 – May 2023 - Relevant Coursework: Embedded Systems Design, IoT Technologies, Cloud Computing - Honors/Awards: Dean's List (Fall 2021) - GPA: 3.8
Quick Tips
- Start with your most recent degree and move backwards in time.
- Focus on relevant coursework that aligns with your current or future career path.
- Include only the most notable honors, awards, or leadership roles if applicable.
- Use bullet points to make the information easy to scan for recruiters.
06
Projects
Projects
Project Name | Technologies Used - Briefly describe what you built and its purpose - Highlight a specific technical challenge you solved - Link to GitHub or live demo if available
General Guidelines
Projects are excellent for demonstrating practical skills, especially if you lack work experience or are changing careers. Include a link to the GitHub repo or live demo if possible. Focus on projects that show problem-solving skills and relevant technologies for the target role.
Avoid This
Don't include trivial tutorials unless you significantly expanded on them. Avoid projects that are outdated, incomplete, or irrelevant to the role you're applying for. Don't just list technologies—explain what you built and why it matters.
Real Examples
Practical example showing do's and don'ts for projects
Don't
Developed a simple calculator app that adds two numbers using JavaScript. This project taught me the basics of HTML, CSS, and JavaScript.
Do
Built an IoT garden monitoring system using Python, MQTT, and Raspberry Pi sensors to track soil moisture and temperature. Added alerts for out-of-range readings and documented setup steps so another student team could reproduce the project.
Quick Tips
- Highlight projects that showcase your ability to solve real-world problems using relevant technologies.
- Emphasize any significant contributions or unique aspects of the project in your description, such as innovative features or user impact.
- Include a link to GitHub repositories or live demos whenever possible to allow reviewers to see your work firsthand.
- Avoid discussing trivial or outdated projects that do not add value to your application or demonstrate relevant skills.
Frequently Asked Questions
Common questions about this role and how to best present it on your resume.
Emphasize coursework, technical projects, internships, coding languages, tools, and measurable contributions such as tests added, bugs fixed, latency reduced, or deployment time saved.
Use school projects, lab work, open-source contributions, hackathons, certifications, and part-time technical work to show how you solve problems and work with real tools.
Yes. Include projects that show relevant technologies, a clear problem, your specific contribution, and a GitHub or demo link when the work is polished enough to share.
Certifications can help when they support the role, but they should not replace projects or experience. List only credible, relevant certifications you can discuss in an interview.
Build a Resume That Gets You Hired 60% Faster
In minutes, create a tailored, ATS-friendly resume proven to land 6X more interviews.
Beat the 75% ATS Rejection Rate
3 out of 4 resumes never reach a human eye. Our keyword optimization increases your pass rate by up to 80%, ensuring recruiters actually see your potential.