How to make a portfolio website that gets you hired

Step by step

1. Define who the portfolio is forWrite down the role, seniority and type of company you want next. Every decision about projects, wording and design should serve that reader, not everyone.
2. Pick three to six of your strongest projectsChoose work that matches the job you want, shows a range of skills and has an outcome you can describe. Cut anything you would not want to talk about in an interview.
3. Write a short case study for each projectCover the problem, your role, the constraints, what you did, and the result. Lead with one strong image or demo and keep each case study readable in two minutes.
4. Plan the page structureA clear home page with a one-line positioning statement, a work section, an about section and an obvious way to contact you is enough for most people.
5. Choose a template or design system and keep it simplePick a layout that puts the work first, use one or two typefaces, a restrained colour palette and generous spacing. Check it on a phone before anything else.
6. Write your about section and contact detailsExplain what you do, who you do it for and what you are looking for now, in plain language. Add an email address, LinkedIn or GitHub, and a downloadable resume.
7. Publish, test and share itExport the site, host it on a static host, connect a custom domain, test speed and links, then put the URL on your resume, email signature and profiles.

Start with the reader, not the design

Recruiters and hiring managers often spend less than a minute on a portfolio before deciding whether to look deeper. In that time they want to answer three questions: what do you do, are you good at it, and are you relevant to the role they are hiring for. A portfolio that answers those questions quickly will beat a beautiful one that hides the answers behind animation or a vague tagline.

Before you open any builder, write a single sentence that describes you to your target reader, for example 'Product designer focused on B2B onboarding and design systems' or 'Backend engineer who builds reliable payment and data pipelines'. That sentence becomes your headline and the filter for every project you include.

Choosing projects: quality over quantity

Three excellent, well-explained projects are more persuasive than twelve thumbnails. Hiring teams read portfolios to understand how you think, and they can only do that when there is enough detail to follow your decisions.

If you are early in your career and lack client work, self-initiated projects are fine as long as you treat them seriously: define a real problem, set constraints, and show what you learned. Redesigning a well-known app with no constraints or research tends to read as an exercise; solving a specific problem for a local business, open-source project or community group reads as real work.

• Relevance: does this project resemble the work you want to be hired for?
• Ownership: can you clearly explain which parts you personally did?
• Outcome: is there a result, metric, shipped product or lesson you can point to?
• Range: together, do the projects show different skills rather than the same one repeated?
• Permission: are you allowed to show it? Use anonymised or redacted versions of work under NDA.

How to write a case study people actually read

A good case study is a short story with evidence. Open with a one-paragraph summary: the client or context, the problem, your role and the outcome. Many readers stop there, so make it complete on its own.

Then expand in the order a curious reader would ask questions: what made the problem hard, what options you considered, why you chose the approach you did, and what happened after launch. Use headings so people can skim, keep paragraphs short, and put an image, diagram, code snippet or metric next to each claim. Quantify results where you honestly can, such as conversion up 12 percent, build time halved, or support tickets reduced, and say how you measured them.

For developers, a live demo link and a link to the repository are worth more than screenshots. Make sure the README explains how to run the project and what you would improve with more time.

Structure and design that put the work first

Most strong portfolios share the same simple structure: a home page with your headline and selected work, one page per case study, an about section, and contact details that are visible without hunting. Navigation should have no more than four or five items.

Design choices should support reading. Use a comfortable body text size of at least 16 pixels, high contrast between text and background, and consistent spacing. Limit yourself to one or two typefaces. Images should be compressed and sized correctly so pages load quickly on mobile data, because a slow portfolio is often closed before it renders. If you are a designer, the portfolio itself is a work sample, so attention to detail matters, but clarity still wins over novelty.

Templates are a sensible starting point for most people. Portfolio OS, for example, includes portfolio templates for developers, designers, writers and consultants with light and dark themes, so you can focus on content and adjust colours, fonts and spacing later.

Your about section and contact details

The about section is where a hiring manager decides whether they would enjoy working with you. Write it in the first person, in plain language, and cover what you do, the kinds of problems you like, relevant experience or industries, and what you are looking for now. A friendly, professional photo helps people remember you but is optional.

Make contacting you effortless. Show an email address as text, not only a contact form, and link to LinkedIn, GitHub, Dribbble or other profiles that support your work. Offer your resume as a PDF download and keep it consistent with the portfolio: the same job titles, dates and project names.

Domains, hosting and publishing

A custom domain such as yourname.com looks professional and stays with you if you change tools. Domains typically cost around 10 to 20 US dollars a year. A portfolio is usually a static site, so it can be hosted for free or very cheaply on static hosts such as GitHub Pages, Netlify, Vercel or Cloudflare Pages.

If your builder can export a plain HTML site or a ZIP of static files, you are never locked in: you can upload the files to any host, keep a backup, and move later. Portfolio OS exports standalone HTML, a ZIP website, or Next.js and Vite source code, and it runs in the browser with no sign-up.

Before sharing the link, test every page on a phone and a laptop, click every link, check that images load, and run a speed test such as Google PageSpeed Insights. Add a page title and meta description so the site looks good when shared and appears properly in search results.

Keep it current

Set a reminder to review your portfolio every few months. Swap in stronger projects as you finish them, remove ones that no longer represent your level, and update your headline when your goals change. A portfolio with a recent project and a current job title signals that you are active and serious.

Frequently asked questions