Who it actually helps
Anyone whose work is visual or interactive, because a PDF cannot show it: designers, front-end developers, photographers, illustrators, video editors, architects. For these fields the site is not a resume in a different format, it is the portfolio, and the resume is the appendix.
Writers, researchers and consultants, where a body of published work benefits from being collected, linked and readable in a browser rather than listed.
And people building a public presence — speakers, founders, anyone who wants to be findable by name. A personal domain that ranks for your own name is worth having, and it is the one benefit that accrues over years rather than per application.
For everyone else — accountants, nurses, project managers, sales, operations — the honest answer is that almost nobody will visit it. Recruiters work from the resume and LinkedIn, and a third destination adds a click that most will not make.
What goes on it
Less than you think, and organised for someone who arrived from a link in an application and has thirty seconds.
- A single sentence at the top saying what you do. Not a mission statement.
- The work itself, if the work is the point — three to six pieces, each with what it was, what you did and what happened. Case studies beat thumbnails.
- A condensed career history. Not the full resume; the shape of it, with the PDF downloadable.
- Contact: an email address, and links to whichever profiles are current. Not a contact form nobody trusts.
- Nothing else. No skill bars, no testimonials carousel, no blog you will abandon in six weeks, no animated hero section.
How to build it without losing a weekend
Match the tool to the point of the exercise. If the site is a portfolio, use something that lets you publish and move on — a hosted site builder, a template on a static host, or one of the personal-site services. Nobody hiring a photographer cares what the site is built with.
If you are a developer and the site is itself a work sample, then building it is the point, and a static site generator deployed to any of the free hosts is the conventional route. Keep it small. A personal site that demonstrates restraint reads better to another engineer than one that demonstrates every framework you have tried.
Buy a domain that is your name. It costs about the price of a coffee per year, it is the part that lasts, and yourname.com in a resume header looks considered in a way that a subdomain on a free host does not. Everything else about the site can be rebuilt later; the domain is the thing worth owning now.
The site does not replace the PDF
This is the mistake worth naming plainly. Applications go through systems that expect a file, recruiters forward documents to hiring managers, and hiring managers print things or read them offline. A URL in place of an attachment fails at the first automated step and irritates at every human one.
So the site is a supplement. The PDF is what you send, with the URL in the contact line beside your email — one link, in the header, where a curious reader will find it. If the site is the portfolio for a visual role, name it as one: "Portfolio: jordanalvarez.com" tells the reader what they will get.
Keep them consistent. A site listing a job the resume omits, or dates that do not match, creates exactly the sort of discrepancy that becomes a question. And if the site goes stale, take it down or update it — an abandoned personal site with a two-year-old "currently at" line is worse than no site, because it demonstrates the opposite of what you were trying to show.
