Portfolio projects that impress employers (and how to present them)
What hiring managers look for in a developer portfolio, which kinds of projects show it, and how to present them: README, tests, design notes and a clean history.
A portfolio exists to answer one question for a hiring manager: can this person do the work? A to-do app with a nice UI doesn't answer it. A project with requirements, tests, a design rationale and visible trade-offs does.
What reviewers actually look at
Most reviewers spend a few minutes per candidate. In that time they check:
- The README: what it is, how to build it, how to run the tests. If that's unclear, they stop.
- Tests: do they exist, and do they cover edge cases rather than just the happy path?
- Structure: small functions, clear names, separation of concerns.
- Decisions: why this data structure, what was rejected, what the limits are.
- History: a commit log that shows the work in steps, not one giant "initial commit".
Projects that show real skill
Pick projects where correctness is non-trivial and the trade-offs are interesting:
- Money and invariants: a ledger where transfers are atomic and reversals never rewrite history, like the Coinbridge account ledger.
- Parsers with real error handling: a strict JSON parser with exact error positions, like the Configo JSON parser.
- Systems that survive failure: a storage engine with a write-ahead log and crash recovery, like the Vaultline key-value store.
- Performance with fairness rules: an order book with price-time priority, like the Tickmark order book.
More ideas by level: beginner, intermediate and advanced.
How to present a project
- README first: one paragraph on what it does, build and test commands, a short design summary.
- Link your design note, including what you considered and rejected. See design docs for junior developers.
- Show the tests and how to run them. Mention any property or stress tests.
- Write a "what I'd do next" section. It shows judgement.
- Keep the history honest. Small commits with clear messages.
Devventura projects give you most of this by default: the tickets, your design note, milestone tests and a stretch ticket that proves you can extend your own code. Finishing all projects in a level earns a certificate you can add to LinkedIn.
Questions and answers
- How many projects should a junior developer portfolio have?
- Three to five finished projects is plenty. Quality and explanation matter far more than count: reviewers rarely look at more than two.
- Can I put course or learning-platform projects in my portfolio?
- Yes, if the code is yours and you can explain every decision. Say where the requirements came from, link to your design note, and point out what you'd do differently.
Practise it in a project
These projects put this guide to work, with tickets, tests and code review.
Coinbridge Credit Union
Account ledger for Coinbridge
Build the ledger behind Coinbridge's accounts: deposits, withdrawals, all-or-nothing transfers, reversals and statements with running balances.
- invariants
- atomic operations
- audit trails
- result codes
Configo
A JSON parser for Configo
Write the strict, dependency-free JSON parser at the heart of Configo: exact error positions, Unicode escapes, depth limits, compact output and path lookups.
- recursive descent
- recursive data types
- Unicode and UTF-8
- defensive parsing
Vaultline
A durable key-value store for Vaultline
Build Vaultline's embedded key-value store: an append-only log that survives crashes, checksums that catch corruption, and compaction that rewrites the log atomically.
- append-only logs
- crash recovery
- checksums
- atomic file replacement
Tickmark Exchange
An order book for Tickmark Exchange
Build the heart of an exchange: a limit order book with price-time priority, partial fills and O(1) cancels, then market orders, immediate-or-cancel and order amendments.
- ordered maps
- iterator stability
- invariants
- property-based testing
Read next
- How to write a design doc: a short guide for junior developers
What a design document is for, a half-page template (components, data structures, trade-offs, open questions) and a worked example, before you write any code.
- LeetCode alternatives: how to become job-ready, not just interview-ready
Coding puzzles train one skill. Here's what else the job needs, how to practise it, and how to balance interview prep with real project work.