Developer Portfolio Builder
Build Your First Job-Ready Developer Portfolio in 14 Days
You don’t need another 30-hour coding course. You need to turn what you already know into evidence an employer can understand.
That is a different job with different tools, and it is the one nobody teaches. Developer Portfolio Builder gives you the templates, the project specifications, the worked examples and a day-by-day system to get it done in a fortnight.
- Modules
- 7
- Days
- 14
- Project briefs
- 30
- Templates
- 6
One payment. Lifetime access, including updates. Instant access. Digital download, nothing ships.
Build My Portfolio — €39- 7 modules and a 14-day plan with a deliverable every day
- 30 project briefs with full specifications
- Website, GitHub, README, CV and case-study templates
- 100-point scorecard, AI prompt library, application tracker
Who this is for
This is for you if
- You are studying software development or computer science, or teaching yourself
- You can already build things — this is not a programming course
- You have at least one project or assignment to work with
- You are applying for an internship, placement or first junior role
- You are stuck on presentation rather than on programming
Who it is not for
This is not for you if
- You cannot code yet — learn to build something first, then come back
- You want a guaranteed job; nobody selling a product controls that
- You want someone to build your portfolio for you
- You already have a portfolio getting you interviews — you do not need this
Before → after
The change you are actually trying to make
The course
Seven modules, each ending in something that exists
01Decide what your portfolio needs
Work out what you are actually missing, instead of guessing
38 min
Decide what your portfolio needs
Work out what you are actually missing, instead of guessing
Most people start by building another project. Start instead by finding out which part of your portfolio is costing you replies — for most students it turns out to be documentation and positioning, not code.
- 1.18 min
What employers actually need to see
Understand the specific evidence a reviewer is looking for from a junior candidate.
- 1.210 min
The anatomy of a good developer portfolio
See how GitHub, website, projects, CV and LinkedIn are supposed to work together.
- 1.312 min
The portfolio audit
Score your current portfolio and identify your three largest gaps.
- 1.48 min
Pick your target role
Choose a role so every later decision has something to be measured against.
Deliverable: A gap analysis of your current portfolio and a chosen target role.
02Choose projects worth showcasing
Pick two or three projects that prove something, and scope them honestly
55 min
Choose projects worth showcasing
Pick two or three projects that prove something, and scope them honestly
The difference between a tutorial project and portfolio evidence is not difficulty — it is whether it solves a real problem, was finished, and can be explained. This module covers choosing, scoping and upgrading.
- 2.112 min
What makes a portfolio project impressive
Tell the difference between a tutorial rebuild and evidence of engineering ability.
- 2.210 min
The 30-project library
Navigate 30 briefs across beginner, intermediate and advanced levels.
- 2.38 min
Choose your projects
Score options on relevance, learning, interest, complexity and time.
- 2.415 min
University assignment to portfolio project
Upgrade an assignment with real features, tests, documentation and deployment.
- 2.510 min
Scope without getting stuck
Apply the MVP → Core → Advanced → Stretch model so you actually finish.
Deliverable: Two or three chosen projects with a written specification for each.
03Upgrade what you already have
Turn existing coursework into projects a reviewer takes seriously
40 min
Upgrade what you already have
Turn existing coursework into projects a reviewer takes seriously
You probably do not need to build from scratch. Deployment, documentation, tests and one unrequested feature turn an assignment into something indistinguishable from a personal project.
- 3.110 min
The upgrade framework
Apply five changes that move an assignment into portfolio territory.
- 3.212 min
Deploy anything, free
Get a project onto a public URL whatever the stack.
- 3.310 min
Add tests that mean something
Write a handful of meaningful tests and run them in CI.
- 3.48 min
Handling the cases the marking scheme ignored
Make the project survive bad input, empty states and a failing dependency.
Deliverable: One upgraded project, deployed and documented.
04Build your GitHub
Make the first thing a technical reviewer opens work in your favour
65 min
Build your GitHub
Make the first thing a technical reviewer opens work in your favour
Your GitHub is judged whether or not you intend it to be. This module covers the profile, the repository cleanup, README files and the workflow signals that read as professional.
- 4.18 min
Your GitHub is your technical evidence
Treat the profile as a portfolio rather than a backup drive.
- 4.212 min
Clean up your profile
Fix the bio, profile README, pinned repositories and naming.
- 4.312 min
Repository structure
Lay out a repository the way a reviewer expects to find it.
- 4.415 min
Write a README employers want to read
Document the problem, demo, stack, architecture, setup and lessons.
- 4.510 min
Commits, issues and project boards
Show a development process, not just a final state.
- 4.68 min
GitHub final audit
Run the full quality checklist across your profile.
Deliverable: A cleaned profile, pinned repositories and a README on each one.
05Build your website
Get a live portfolio site with a URL you can put on a CV
70 min
Build your website
Get a live portfolio site with a URL you can put on a CV
One page, five sections, deployed. This module gives you the template, the copy prompts for each section, and the deployment path — including what to do when a build fails.
- 5.110 min
What your website needs
Define the minimum set of sections and what goes in each.
- 5.215 min
The portfolio website template
Customise the starter template rather than building from an empty folder.
- 5.310 min
Writing your developer introduction
Write a header that says what you build in one clear sentence.
- 5.415 min
Project case studies
Turn each project into a short technical story with a real decision in it.
- 5.512 min
Deploy your website
Ship to Vercel, Netlify or Pages, including the common build failures.
- 5.68 min
Mobile, performance and accessibility check
Pass Lighthouse and work properly on a real phone.
Deliverable: A live, responsive portfolio website.
06Present yourself professionally
Make your CV, LinkedIn and project explanations tell one consistent story
80 min
Present yourself professionally
Make your CV, LinkedIn and project explanations tell one consistent story
The portfolio only gets opened if the CV survives the first filter. This module covers the developer CV, project bullet points, LinkedIn positioning, and using AI without ending up unable to explain your own work.
- 6.18 min
Your developer identity
Settle on a direction you can state in one sentence.
- 6.210 min
The skills section
Present technologies honestly, without star ratings or percentages.
- 6.315 min
Your developer CV
Build a one-page, ATS-friendly CV from the template.
- 6.412 min
Writing project bullet points
Compress each project into three lines that survive a 20-second scan.
- 6.512 min
LinkedIn that matches your portfolio
Align headline, About, Featured and links with the rest of your story.
- 6.623 min
Using AI without losing ownership
Use AI to brainstorm, review and document — while keeping every claim explainable in an interview.
Deliverable: A developer CV, an updated LinkedIn profile and an AI prompt library.
07Launch your portfolio
Run the final audit and start applying with something you are confident in
45 min
Launch your portfolio
Run the final audit and start applying with something you are confident in
The last mile: the recruiter walkthrough, the 100-point scorecard, the application assets, and a maintenance habit that stops the whole thing going stale in three months.
- 7.18 min
The 10-second test
Check that a stranger immediately understands who you are and what you build.
- 7.212 min
The recruiter walkthrough
Test the CV → LinkedIn → portfolio → project → GitHub journey end to end.
- 7.310 min
The 100-point portfolio scorecard
Score the finished portfolio and fix whatever falls below the line.
- 7.48 min
Application ready
Assemble final links, the CV PDF and your application tracker.
- 7.57 min
Maintaining your portfolio
Set up a monthly habit so it stays current while you apply.
Deliverable: An application-ready portfolio and a tracked list of applications.
14 days
Every day produces something finished
Decide
Days 1–4Find the gaps, pick a direction, choose projects and scope them before writing any code.
Build
Days 5–9Clean up GitHub, then get two projects to a finished, deployed, documented state.
Present
Days 10–12Publish the website, write the case studies, and align the CV and LinkedIn with them.
Launch
Days 13–14Score it, fix what falls short, and start applying with links you are confident in.
What you actually get
See what's inside before you buy
Portfolio scorecard
Baseline — day 1
60/100
- GitHub profile14/20
- Projects18/25
- Documentation8/20
- Website11/15
- CV & LinkedIn9/20
Biggest gap: Documentation. Three pinned repositories have no README.
100-point portfolio scorecard
Score GitHub, projects, documentation, website, CV and LinkedIn. Re-score after each round of changes to see what moved.
Project library
30 briefs
Each brief includes the problem, users, core features, stretch goals, data model, stack options and what a reviewer can infer from it.
30-project library
Each brief has the problem, users, core features, stretch goals, data model, stack options and an honest time estimate.
14-day roadmap
- 1
Portfolio audit
Baseline score and a written gap list
- 2
Choose your target role
A target role and portfolio direction
- 3
Select your projects
Two or three chosen projects
- 4
Write the specifications
Feature list, stack and scope per project
- 5
Set up GitHub
Clean profile, README, pinned repositories
- 6
Clean existing repositories
Archived noise, renamed repos, descriptions added
14-day roadmap
One task and one output per day. Days run from 30 minutes to three hours, and nothing is left as 'keep working on it'.
Priya Raman
priya-raman
Final-year CS student. I build APIs and data pipelines in Python and Go.
Pinned
society-events
Event sign-ups for university societies
Python★ 12
log-analyser
Stream and query logs larger than memory
Go★ 8
devkit
Everyday developer utilities as one binary
Go★ 24
deadline-tracker
Coursework deadlines in one place
TypeScript★ 5
GitHub profile system
The four-pass cleanup, a repository template with a CI workflow, and the checklist to run afterwards.
Priya Raman — back-end developer
Final-year computer science student. I build APIs and data pipelines in Python and Go. Available from July 2027.
Society Events Platform
Live ↗Event sign-ups for three societies. ~400 registrations over a term.
Django · Postgres · Redis · Fly.io
Log Analyser
Live ↗Queries logs larger than memory. Peak usage 1.2 GB → 40 MB.
Go · SQLite · HTMX
Portfolio website template
A responsive starter with project cards, About, Skills and Contact — plus the copy prompts for every section.
# Society Events
Event sign-ups for university societies. Built for three
societies at my university; ran a full term, ~400 sign-ups.
**Live:** https://events.example.dev · **Stack:** Django, Postgres, Redis
## The problem
Committees ran sign-ups through Instagram stories and a
spreadsheet. Cancellations were missed and events overfilled.
## Technical decisions
**Capacity enforced in the database, not the service layer.**
Load testing showed two simultaneous sign-ups could both pass
an application-level check for the last place. Moved to a
unique constraint inside a transaction — slower, correct.
## What was hard
Waiting-list promotion. When someone cancels, the next person
must be promoted exactly once, even if two cancellations land
in the same second.README template
The documentation structure reviewers actually read, with guidance for each section and worked examples.
Priya Raman
Back-end developer · Manchester · priyaraman.dev · github.com/priya-raman
Projects
Society Events Platform — Django, Postgres, Redis
- · Built event sign-up used by 3 societies for ~400 registrations over one term
- · Prevented capacity oversell with a DB constraint after load testing found a race
- · Added transactional email and CSV export used by committees each week
Log Analyser — Go, SQLite
- · Streamed 2 GB log files line by line, cutting peak memory from 1.2 GB to 40 MB
- · Built a query layer with time-range and level filters over 4M parsed records
Technologies
Languages Python, Go, SQL, TypeScript · Data PostgreSQL, Redis, SQLite · Tools Docker, GitHub Actions, Linux
No star ratings. No percentage bars. One page.
Developer CV template
One page, ATS-friendly, no percentage bars. With the bullet-point patterns that survive a 20-second scan.
Society Events Platform
Case study · 7 sections
- Problem
- Committees ran sign-ups across Instagram and a spreadsheet. Cancellations were lost.
- Users
- Three societies, roughly 400 registrations across one term.
- Approach
- Scoped to sign-ups and capacity only. No payments, no accounts for members.
- Architecture
- Django + Postgres. Redis for the waiting-list queue. Email via a transactional provider.
- Challenges
- Two simultaneous sign-ups could both take the last place. Fixed with a DB constraint.
- Result
- Ran a full term without a double-booking. Committees export attendees weekly.
- Lessons
- I would put email behind a queue — sending inline made the endpoint slow.
Case-study template
Problem, users, approach, architecture, challenges, result, lessons — and how to compress it into CV bullets.
Plus
- 50-prompt AI library, with the ownership rules attached to each one
- LinkedIn framework — headline, About, Featured and projects
- Application tracker with follow-up scheduling
- Three annotated example portfolios at different levels
- Final launch checklist to run before your first application
Everything included
The full contents
The system
7-module course
Around six hours of short lessons, each ending in a decision or a deliverable rather than a summary.
14-day implementation roadmap
A daily plan with a defined output per day, so progress is visible instead of theoretical.
100-point portfolio scorecard
Score GitHub, projects, website, technical evidence, CV, LinkedIn and documentation, then re-score after changes.
Projects
30-project library
Beginner, intermediate and advanced briefs with problem, users, features, data model, stack and stretch goals.
Project selection framework
Score candidate projects on relevance, learning, interest, complexity and time.
Assignment upgrade system
Turn existing coursework into portfolio evidence in two evenings rather than three weeks.
Templates
Portfolio website template
Responsive starter site with project cards, About, Skills and Contact sections.
GitHub repository template
Structure, .gitignore, licence and a CI workflow you can copy straight in.
README template
The full documentation framework, with guidance for every section.
Developer CV template
One page, ATS-friendly, with project bullet-point patterns that pass a scan.
Project case-study template
Problem → users → approach → architecture → challenges → result → lessons.
LinkedIn framework
Headline, About, Featured and project positioning, with worked examples.
Support materials
AI prompt library
50 prompts for project ideas, debugging, code review, documentation, architecture and interview preparation — with the ownership rules that keep your work yours.
Application tracker
Companies, roles, dates, contacts, stages and follow-ups in one place.
Three example portfolios
Beginner, intermediate and advanced worked examples, annotated with what each one gets right.
Final launch checklist
The one-page pass to run before you send your first application.
Free vs paid
What the free toolkit covers, and what it doesn't
Price
One payment, lifetime access
The launch price is what it costs while the product is new and there are few testimonials. It rises to the standard price after the launch window and stays there — there is no relaunch and no reset.
If it is not worth it to you, the free toolkit is genuinely useful on its own and we would rather you used it.
One payment. Lifetime access, including updates. Instant access. Digital download, nothing ships.
Build My Portfolio — €39- 7 modules and a 14-day plan with a deliverable every day
- 30 project briefs with full specifications
- Website, GitHub, README, CV and case-study templates
- 100-point scorecard, AI prompt library, application tracker
FAQ
Questions before you buy
Is the free toolkit actually free?
Yes. Seven files — a portfolio checklist, a GitHub checklist, a README template, a case-study template, a website structure guide, five project briefs and a final audit. No payment details, no trial that converts, no credit card. You give an email address, we send the files and occasional resources, and you can unsubscribe from any email in one click. The full contents are listed on the toolkit page before you sign up, so you can see exactly what you are getting.
What is the difference between the free toolkit and the paid product?
The free toolkit tells you what a good portfolio contains and gives you the templates for the core pieces. It solves roughly the first quarter of the problem, and for some people that is genuinely enough. Developer Portfolio Builder is the implementation system: seven modules, a 14-day plan with a defined output each day, 30 project briefs with full specifications, the website and CV templates, an AI prompt library, an application tracker and a 100-point scorecard. The free version answers 'what should I do'; the paid one walks you through doing it.
What does the paid toolkit include?
A seven-module course of short lessons (about six hours total), a 14-day implementation roadmap with a daily deliverable, a 30-project library split across beginner, intermediate and advanced with full specifications, a portfolio website template, a GitHub repository template, a README template, a developer CV template, a project case-study template, a LinkedIn framework, a 50-prompt AI library, an application tracker, three annotated example portfolios, a 100-point portfolio scorecard and a final launch checklist.
How long does the 14-day system take?
Roughly 6–7 hours of content and 10–15 hours of implementation, spread over two weeks. Days are between 30 minutes and three hours, with the heaviest days being the project work in the middle. It is not a race — people who take four weeks finish just as well as people who take two. What matters is that each day produces something concrete rather than something watched.
Do I need to be able to code already?
Yes. This is not a programming course and it will not teach you a language. It assumes you can already build something and are stuck on turning that into evidence an employer can read. If you have completed a first year of a computing degree, a bootcamp, or an equivalent amount of self-teaching, and you have at least one project or assignment to work with, you have enough.
Does this work for my language and stack?
The system is stack-agnostic — the audit, the project selection, the documentation structure, the CV and the case-study framework apply whatever you write. The examples lean web-heavy because that is where most junior roles are, but the project library covers back-end, mobile, game development and data work, and the templates assume nothing about your language. The one place stack matters is the website template, which is provided in a common web stack; you are free to build your site any way you like.
Why is it €29 and not free?
The free toolkit is where we prove the material is worth your time, and it stays free. The paid product is a substantial amount of work — 30 written project specifications, seven modules, a dozen templates, a scorecard — and pricing it means it can keep being maintained and improved. €29 is the launch price while the product is new and there are few testimonials; it rises to €39 as a standard price. If it is not worth €29 to you, the free toolkit is genuinely useful on its own and we would rather you used it.
Will this guarantee me a job?
No, and be wary of anything that says otherwise. Hiring depends on the market, the role, your interviews and a lot of things nobody selling a product controls. What this controls is the part you control: whether your portfolio clearly demonstrates what you can do, whether your projects are documented and deployed, and whether you can explain your work. That is what gets you to the interview. What happens in the interview is yours.
How many projects should I have?
Two or three that you can explain in depth. Reviewers do not read eight projects; they look at the first two and form a view. A common pattern that works well: one substantial project that shows depth, one that shows breadth or a different skill, and optionally one small polished thing like a CLI tool or a published package. Four projects at 60% completion is the most common shape on a junior portfolio and the least effective.
Can I use AI when building my portfolio?
Yes, and pretending otherwise would be unrealistic — professional developers use it daily. The rule that matters is ownership: you must be able to explain every line you present, because you will be asked to. Use it for brainstorming scope, reviewing your own code, drafting documentation you then rewrite, and rehearsing explanations. Do not use it to generate a project you have not read, and do not claim familiarity with a technology you only watched a model use. An interviewer finds that out in about ninety seconds.