A personal website for PhD students

A hiring committee in a mid-sized department gets through a shortlist between two other meetings, a stack of forty applications and about ninety minutes. Nobody on that committee reads your job market paper first. They read your CV, skim the cover letter, and — for the candidates who are close calls, which is most of the shortlist by definition — they open whatever link you gave them to see if the work is legible before committing forty minutes to the paper itself. That is the honest version of what a personal website does on the academic market: it is not the argument, it is the thing that decides whether the argument gets a full read.

The strongest objection to spending any time on this is correct as far as it goes: committees hire on the paper, the letters and the talk, not on web design. A beautifully built site attached to a mediocre job market paper changes nothing. But that objection answers a question nobody is actually asking. The page isn't competing with the paper for importance; it's competing with the ninety seconds a committee member has before they decide whether to open the paper at all. A candidate whose site makes that decision easy gets read. A candidate whose site makes it a chore — three menus deep, no summary, a CV as the only content — loses attention to whoever made it easy, even if the underlying work is just as good.

The paragraph that has to work on a stranger from another subfield

Every hiring committee includes people outside your immediate subfield — a labor economist on a search for a macro position, a syntactician reading a sociolinguist's file, a cell biologist sitting on a search that will eventually hire a structural biologist. These people vote. Their read of your work has to happen in the two or three sentences you give them, because they are not going to reconstruct your contribution from the abstract of a forty-page paper written for specialists.

The fix is one paragraph, written before anything else on the page, that states your question, why it matters outside your subfield, and what you found — in language a colleague from a different area of the same discipline would understand on the first read. Not a dumbed-down version of the abstract; a genuinely different piece of writing, because an abstract is written to satisfy reviewers who already know the literature and this paragraph is written to satisfy someone who doesn't.

There is a real test for whether it works: read it to labmates or officemates in an adjacent subfield and ask them to repeat back what you study and why it's interesting, without looking at the paragraph again. If they can't, the paragraph is still written for specialists and needs another pass. This is a harsher test than it sounds — most drafts fail it twice before they pass, because the habit of writing for reviewers is hard to unlearn in one sitting.

reach and where a PhD site fits in the broader landscape of builders

Before going further into the academic specifics, it's worth being honest about what building this page actually requires, because most PhD students building their first site are choosing a tool, not just writing content. For a one-page academic site — research statement, job market paper link, CV, teaching, contact — reach is the fastest route from nothing to something real: it turns a CV into a finished one-page site, generated in about twenty seconds, and you can be live on a free yourname.joinreach.app subdomain in under two minutes. For a document you already have — your CV — turning it into a page rather than starting from an empty template is the whole advantage, and it matters more during a job search than at almost any other point in an academic career, because the search happens on a deadline you don't control.

It is not the right tool for everyone on the market, though, and the limitation that matters most here is specific: reach makes exactly one page, with no sub-pages and no site navigation. If your field expects a syllabus archive, a full publications page with abstracts, and a teaching portfolio as separate pages rather than sections of one scroll — common in some humanities departments — a single-page tool will feel cramped. For the research-statement-plus- JMP-plus-CV shape most STEM and social science candidates actually need, one page is not a compromise; it's the right shape already, and the constraint that would hurt elsewhere doesn't apply here.

Route	Price	Billing	Pages
reach	$0 subdomain / $4.99 custom domain	monthly, or $49/year	One page
Carrd Pro Standard	$19	per year, annual only	One page, custom domain
WordPress.org + budget host	~$3/mo intro, renews higher	varies by host	Unlimited
Webstudio free tier	$0	—	Unlimited, *.wstd.io subdomain

Prices checked August 2026. If your field wants a real multi-page site with a syllabus archive and a growing publications list, Webstudio's free tier or a self-hosted WordPress site cost little and don't cap you at one page — the trade is that you build every page yourself instead of starting from a generated draft.

The job market paper, placed where it can be found in one click

Whatever tool builds the page, the content decision underneath it doesn't change: below the non-specialist paragraph, the single most important object on the page is a working link to your job market paper, and it should not require scrolling, a menu, or a guess about which of your five working papers counts as "the" one. Label it plainly — "Job Market Paper" as the visible text, not the filename — and make sure the link resolves to a PDF, not a page that requires another click to find the download button.

Name the file itself the way a search committee will actually use it: lastname_jmp.pdf, not draft_v14_final_FINAL.pdf. Committees download dozens of these into one folder over a hiring season, and a file that arrives pre-labeled with your name is a small courtesy that a tired committee member notices, in the same way a badly named file is a small friction they notice too. Everything else you've written — other working papers, a dissertation summary, work in progress — belongs below this, not beside it, because a page with six equally weighted links gives a stranger no signal about which one to open first.

The signals a committee scans for without saying so

Three names on the page do more work than most candidates realize: your advisor, your department, and your cohort. A committee member skimming a site is partly trying to place you — whose lab, which program, working alongside whom — because that placement tells them things a CV states more formally but less immediately. An advisor whose name is recognized in the subfield functions as a kind of pre-read; it doesn't replace your work, but it changes the speed at which a stranger decides to take the work seriously. This is uncomfortable to say plainly and rarely said at all, which is exactly why it's worth stating here: put your advisor's name where it's easy to find, not buried in an acknowledgments line at the bottom of the CV PDF.

Teaching evidence follows a different rule, and the honest version matters more than the padded one. Two seminars taught as a TA is not a teaching record, and presenting it as one invites a skeptical read. State it plainly instead — course titles, level, what you were responsible for, maybe one line of a student evaluation if you have a strong one — and let it be exactly as substantial as it is. A committee reading a short, honest teaching section trusts the rest of the page more than one reading an inflated paragraph trying to make two courses sound like five.

Naming the window you're actually in

Committees see "PhD candidate" often enough that the phrase has stopped telling them anything. It could mean two years from defending or two months. State your actual status and, if you have one, a date: "On the market; dissertation submitted, defense scheduled for March 2027" or "ABD, expected completion August 2027." If you're between submission and viva — the paper is in, the date isn't yet fixed, and the honest status is genuinely ambiguous — say that too, plainly: "Dissertation submitted, defense date pending." A committee that knows exactly where you stand can plan around you. One that has to guess treats the guess as a small risk, and small risks add up against a candidate who is otherwise a toss-up.

The account that disappears

A site built on a departmental server or tied to your university email has a shelf life that has nothing to do with how good the page is. Many institutions close student accounts within a year of graduation, sometimes faster, and a page that lived at yourname.university.edu vanishes with it — often silently, so the first sign is a broken link on a syllabus website somewhere or a search result that now 404s. Move to a domain you personally own before you're job hunting again, not after the account closes and the link you'd been sending to every application is suddenly dead. This matters more for academics than almost any other profession, because the market itself is cyclical: you will likely need this exact page again in three to seven years, on the tenure-track market or after a postdoc, and the version worth keeping is the one that survives your employer changing.

These pieces are specific to the job market window, but they sit on top of the wider pattern covered in personal websites by profession — what a reader scans for varies by field, and academia's version of "prove you're real" is a publication list and an advisor's name rather than a portfolio. For the deeper case on how that scan-first principle plays out for other credential-first fields, see personal websites for designers for the portfolio-first contrast, and the fuller academic treatment in personal websites for academics, which covers faculty sites beyond the job market moment this piece is about.