How to Write a Research Statement That Actually Wins Faculty Jobs
Search committees spend 90 seconds on your research statement. Here's the structure that gets you into the shortlist — past, present, and future framed as one coherent program.
1. What a Research Statement Actually Is
A research statement is not a recap of your dissertation. It is a 2-4 page
argument that you have a coherent research program — past work that earned
credibility, current work that shows momentum, and future work that justifies
a faculty line. Search committees read it to answer one question: "If we hire
this person, what will their lab look like in five years?" If your statement
reads like a list of projects, you have already lost.
The One Question You Are Answering
- What is the through-line that ties your past, present, and future work together?
- Why is that line worth a faculty position at this institution?
- What can only YOU do, that no other applicant in the pile can?
2. The 4-Section Structure That Works
Most successful research statements use the same scaffold. Section 1 (about
half a page) opens with a vision paragraph that names your research program
in one sentence. Section 2 (one page) covers past contributions, organized
thematically not chronologically. Section 3 (one page) presents 2-3 future
projects with enough specificity that a reviewer can imagine the first paper.
Section 4 (a short paragraph) closes with broader impact and fit.
3. Open With a Sentence You Could Print on a Coffee Mug
The first sentence is the only line every committee member will read. Make
it a one-sentence summary of your research program — concrete enough to be
memorable, broad enough to span 10 years of work. "I build statistical methods
for causal inference in observational health data" beats "My research is in
machine learning." If you cannot compress your vision into one line, your
program is not yet coherent enough to sell.
4. Frame Past Work as Evidence, Not a CV Repeat
Do not list every paper. Pick 2-3 thematic clusters, each with a clear
contribution and 1-2 supporting publications. For each cluster, write three
things: the question you asked, the methodological move that made it tractable,
and the result that mattered. Cite your own papers with a short bracketed
reference (e.g., [Smith et al., NeurIPS 2025]). Reviewers should leave this
section knowing you have already shipped non-trivial work.
5. Future Projects: Be Specific, Be Fundable
The future section is where most candidates lose the room. Vague aspirations
("I will explore foundation models for science") signal you have not thought
hard enough. Instead, propose 2-3 projects with: a concrete first experiment,
the data or system you would build, an obvious first paper, and at least one
named funding agency that supports this line (NSF CAREER, NIH R01, ERC
Starting Grant). Committees ask: "Could this person bring in money in year
two?" Answer that question without making them ask.
Each Future Project Should Name
- The specific question (one sentence)
- The first experiment or system you would build
- What success looks like — the kind of paper this becomes
- Which funding agency this line fits (NSF, NIH, DARPA, ERC, JSPS, NRF)
- Which collaborators or facilities you would leverage
6. Tailoring Without Sucking Up
Generic statements get filtered first. Tailoring does not mean inserting
"I would love to work at [University Name]" — it means showing you have read
the department's faculty pages. Mention 1-2 specific potential collaborators
and one institutional resource (a center, a dataset, a facility) that would
accelerate your work. Keep it to one paragraph near the end. If the tailoring
sounds like flattery, cut it.
7. Common Mistakes That Get You Cut in Round One
Length over four pages — read but skimmed. No vision sentence — the committee
cannot summarize you. Future section thinner than past — signals you peaked
in your PhD. Jargon a reviewer outside your subfield cannot parse — most
search committees have one expert and four non-experts. Promising more than
a single PI lab can deliver in five years — looks naive. Have a senior
mentor read it specifically for these failure modes before you submit.
PhD graduate who spent years tracking conference deadlines across computer science and engineering. Built ScholarDue after missing a submission window in the final year of candidacy and realizing no single tool tracked CFPs, extensions, and notification dates in one place.
Learn more→