If you design hardware and want more or better work, the fastest lever isn't another certification or a longer resume — it's a portfolio of boards someone can actually look at. Clients and hiring managers can't judge your engineering from a bullet list. They can judge it from a board.
Short answer: build a hardware engineer portfolio around two or three real projects, and for each one show the problem, your role, the board, the outcome, and what you learned. Reveal your process — the schematic decisions, the bug you caught, clean DRC and ERC — not just a glossy render. Make it a link, not a 40 MB PDF. Depth beats breadth every time.
Why a hardware portfolio matters more than a resume
A resume says you did things. A portfolio shows them. In hardware that difference is enormous, because the work is visual and verifiable: a person evaluating you can look at a layout and immediately read your judgment — decoupling discipline, sane grounding, connector placement, whether the board looks like it was routed by someone who cares.
Nobody hands a stranger a board spin worth thousands of dollars on the strength of a job title. They hand it over because they saw evidence you can be trusted with it. Your portfolio is that evidence. It's the thing that converts "sounds qualified" into "I believe this person can deliver."
This matters whether you're job-hunting or going independent. If you're building a freelance practice, the portfolio is the pipeline — see how to become a freelance hardware engineer for where it fits in the bigger picture.
What to include for each project
A portfolio entry isn't a photo — it's a short story with a technical spine. For every project, cover five things:
- The problem. What did this board need to do, and under what constraints? Cost, size, power budget, environment. One or two sentences of context makes everything after it legible.
- Your role. Be honest and specific. "I did schematic capture and layout; a colleague wrote firmware" is far more credible than a vague "I built this." Reviewers trust people who draw clear lines around their contribution.
- The board. Show it. A clean render, a photo of the assembled hardware, a layout view. Let people see the thing you made.
- The outcome. Did it work? Did it ship? How many spins? "First spin came back functional" is a sentence worth a paragraph of adjectives.
- What you learned. This is the one most people skip, and it's the most human. A line about what you'd do differently signals growth and self-awareness — exactly what someone wants in a person they'll hand ambiguous work to.
Show process, not just pretty renders
A 3D render is a nice thumbnail and a weak argument. Anyone can autoroute a board and export a shiny picture. What separates a strong portfolio is evidence of how you think.
Show the decisions. Why did you choose that regulator topology? Why is that section guarded, that trace widened, that plane split? A sentence next to a schematic snippet turns a picture into proof of engineering.
Show a bug you caught. "During review I noticed the load switch enable was floating and added a pull-down before the first spin" is one of the most persuasive things you can put in a portfolio, because it demonstrates the exact behavior a client is paying for: catching problems before they cost a build cycle.
And show cleanliness. A board with a clean DRC and ERC report says you finish things properly. It's the hardware equivalent of tests passing. With GoForFab, every push regenerates your DRC and ERC reports through kicad-cli automatically, so "clean checks" is something you can actually link to rather than claim.
Make it accessible: a link, not a giant PDF
Here's a small thing that quietly costs people work: the portfolio nobody can open.
A 40 MB PDF that has to be emailed, downloaded, and scrolled is friction, and it's stale the moment you export it. Every time the board changes, the PDF lies a little more.
Prefer a link. A simple project page, or a shared dashboard, or even a tidy folder — something a reviewer can open in one click and skim in two minutes. Include real photos of assembled hardware where you have them; nothing builds credibility like a board that visibly exists and works on a bench.
The format should get out of the way. If someone has to work to see your work, most won't.
Weak entry vs strong entry
The gap between a forgettable portfolio and a hire-me portfolio is rarely the board itself — it's how it's presented.
| Weak portfolio entry | Strong portfolio entry |
|---|---|
| "Designed a sensor board." | "Designed a low-power soil-moisture sensor board; sub-10 µA sleep target for a battery product." |
| One render, no context | Render + assembled photo + a layout view |
| No mention of your role | "Schematic + layout mine; firmware by a teammate" |
| No outcome | "First spin functional; iterated once for connector placement" |
| Attached as a big PDF | A live link, always current |
| Silent on process | Notes a floating-enable bug caught in review |
Same board. Completely different impression.
Two or three strong projects beat ten weak ones
It's tempting to pad. Resist it. A reviewer judges your ceiling, not your count — they want to know how good your best work is, and a long list of half-finished boards actively buries it.
Pick your two or three strongest projects, document them properly, and lead with the best one. If you only have one board you're proud of, that's a fine start; make it excellent and shareable rather than diluting it with filler. Curation is itself a signal of judgment.
If you're using the portfolio to land clients, the same "depth over breadth" instinct applies to how you sell — how to stand out as a freelance hardware engineer goes deeper on that.
Open-source a project as a portfolio piece
If you can, open-source one board. It's the highest-trust move available to you, because it removes the need to take your word for anything. A reviewer can read the schematic, inspect the layout, look at your commit history, and see your manufacturing outputs directly.
An open project also demonstrates the workflow habits clients care about: version control, clean file organization, regenerated outputs that aren't stale. It's a public, standing proof that you deliver like a professional — which is exactly what turns a first project into repeat work.
You don't need to open everything. One well-kept public board, front and center, does the job.
A simple way to package it
The friction in all of this is production: keeping renders, BOMs, DRC and ERC reports, and photos current and presentable takes real effort, and it's the part people quietly let rot.
That's the gap GoForFab closes. Connect a KiCad project and every change regenerates a full, professional output set through kicad-cli — Gerbers, BOM, 3D renders, DRC and ERC reports — plus a shareable dashboard link. It makes a genuinely clean portfolio piece: always current, easy to open, and it shows process, not just a picture. It's free forever, so it's an easy way to make one strong project look like the work of an established shop.
Build a few real boards, document them like they matter, show how you think, and hand people a link. In hardware, the board they can see is worth more than anything you can claim.