Why this happens
Recruiters for EV roles screen many applications quickly and look for proof that you can apply skills, not just a list of software names. A portfolio that leads with outcomes, shows real photos, plots and code, and states your exact role makes that proof easy to find.
What you need
Tools
- Laptop
- Presentation or document software that exports PDF
- Optional: a simple personal website or code hosting profile
Materials
- Project reports, photos, diagrams and data plots
- Demo videos
- Course certificates and internship letters
- Updated CV
Before you start
- Never claim work, results or certificates that are not yours; background checks and technical interviews expose it quickly.
- Do not publish confidential internship or company material without written permission.
Step by step
- 1
Pick your best three to five projects
Choose projects that match the roles you want, such as battery modelling, embedded firmware, motor control, CAD or testing. Quality beats quantity: three well-documented projects are stronger than ten thin ones. Include at least one project where you built or tested something physical and one that shows analysis or software.
- 2
Write a one-page overview
At the top, put your name, target role, contact details and two lines on what you do best. Below, list each project with a one-line outcome, for example 'Built a bench CAN logger that decoded four signals from a demo board'. Add key skills grouped by area. A recruiter should understand your profile from this page alone.
- 3
Make a card for each project
Give each project one page or one screen: the problem, your role, tools used, a photo or diagram, one key result with a number and a link to code, report or video. Be specific about your contribution in team projects; interviewers will ask, and vague claims are noticed.
Tip: Lead every card with the result, not the background theory.
- 4
Show evidence, not adjectives
Replace words like 'expert' or 'advanced' with evidence: a plot from your simulation, a wiring diagram you drew, a screenshot of your firmware running, a test table. Recruiters trust artefacts. Make sure every image is clear and labelled, and every number states its conditions.
- 5
Clean up linked code and files
If you link a code repository, add a README explaining the project and how to run it, remove dead files and check that no passwords, keys or confidential partner data are included. Pin the relevant repositories on your profile. A tidy repository is often checked by technical interviewers.
- 6
Show safety awareness
Where relevant, mention how you worked safely: current-limited supplies, fuses, supervised labs, isolation habits and staying away from high-voltage systems unless qualified. EV employers value candidates who understand that battery and high-voltage work has rules. Do not include photos of unsafe practice such as open packs on a desk.
- 7
Tailor and test it
For each application, reorder projects so the most relevant one comes first and adjust the overview line. Ask a senior, mentor or teacher to scan it for one minute and tell you what they remember. Export a PDF small enough to email, name it clearly with your name and role, and keep a web or repository version updated.
How to tell it worked
A reviewer who scans your portfolio for one minute can name your target role, your strongest project and one measurable result, and every claim links to evidence.
Stop and call a technician if
- A project you want to showcase involved unsafe or illegal modification, such as speed-limiter removal; leave it out of your portfolio.
- You are unsure whether internship work can be shown; ask your former supervisor before including it.
Questions
Should my portfolio be a PDF or a website?
Have a PDF for applications and emails, since it is easy to attach and print. A website or repository profile is a useful extra for links and videos.
Can I include coursework projects?
Yes, especially early in your career, as long as you show what you did and what you learned. Label them as coursework honestly.