How do I build a portfolio website that actually gets me hired?

The single biggest upgrade is replacing tutorial projects with things you decided the shape of yourself, and writing up the decisions. Hiring managers spend maybe ninety seconds on a portfolio, and what they're screening for is 'can this person build something real and think about it', not 'can this person follow instructions'. What's wrong with the standard portfolio: - Three projects everyone has (a weather app, a to-do list, a clone of a famous site) prove you can follow a tutorial, which is not a differentiator when a thousand applicants did the same one. - Screenshots with no explanation. The reviewer can't tell what you did versus what the tutorial did. - No live links or broken links. If they have to clone a repo to see anything, they won't. What a convincing portfolio has: 1. Two or three projects, finished and deployed, with a live URL that loads fast. Depth over quantity — one substantial project beats five shallow ones, every time. 2. At least one project that solves a real problem for a real person, even a tiny one. A tool your college club actually uses. Something you built because you were annoyed by a thing. This is the strongest possible signal because it can't be copied from a tutorial. 3. A short write-up per project: what problem it solves, what you chose to build it with and *why*, one hard problem you hit and how you solved it, and what you'd do differently now. This paragraph does more work than the code itself — it's evidence of judgement. 4. Clean, readable code in the linked repo, with a README that has a screenshot, a live link, setup steps and a feature list. Many reviewers only look at the README. 5. Evidence you can finish. Handle empty states, loading states, errors and mobile screens. The 'last 10%' is exactly what separates a student project from a professional one, and reviewers notice immediately. The portfolio site itself: keep it simple and fast. A clean single page with your name, one line on what you do, the projects with links, and contact details beats an over-animated experience that takes six seconds to load. Ironically, an elaborate portfolio site with weak projects reads worse than a plain one with strong projects. One thing to cut: long lists of skill logos with percentage bars. Nobody believes 'JavaScript 85%', and it takes space from the projects that would actually convince someone. Show the work, explain the thinking, make it easy to click.