How to Write a Research Statement

A research statement is the document in a faculty job application where a candidate lays out what they have done as a researcher, what they are doing now, and — most importantly to a search committee — what they intend to do with independent lab or research group funding over the next five to ten years. It sits alongside the cover letter, CV, teaching statement, and (increasingly) a diversity statement in a tenure-track application packet, but it does a different job than any of them: it is the document a hiring, tenure, and (later) grant-review committee reads to decide whether this person has a fundable, independent research program, not just a strong publication record working in someone else’s lab.

This guide covers what a research statement needs to contain, how long it should be, how to structure it so a search committee actually reads it closely, and how it differs from the adjacent documents — personal statement, teaching statement, cover letter, and NIH/NSF biosketch — that candidates often conflate with it.

What a research statement is for

A search committee reading a research statement is trying to answer three questions: Does this person have a coherent research identity, or is their record just a list of projects done for other people? Is there a fundable, independent research program here — one that doesn’t depend on a former advisor’s lab, reagents, or grant? And does that program fit what this specific department or institution needs — instrumentation, student population, existing strengths, space?

That third question is why a generic research statement performs poorly even when the science in it is strong. The most common feedback career-services offices and search-committee members give on weak drafts is that the document reads as “here is what I did” and nothing more, rather than showing where the work goes next and why the target department is the right place for it to go there. A research statement written for one search and reused unedited for the next is usually recognizable as such — committees at different institutions are looking for a program that fits their specific resources, colleagues, and student body, not a form letter.

Structure: past, present, future

Nearly every field’s convention for a research statement organizes it around the same three-part arc, even where the section headings themselves vary or disappear:

Past work (brief). One paragraph, sometimes folded into the opening, that establishes the candidate’s training and the intellectual thread connecting their dissertation and postdoctoral work — not a chronological CV recap, but the throughline that makes the rest of the statement make sense.
Present/ongoing work. What the candidate is actively working on now, including work in progress and papers under review, described with enough specificity that a generalist reader in an adjacent subfield understands both the question and why it matters.
Future direction (the largest section, by far). A concrete, several-year research program: 2-4 specific projects or aims, described in enough detail that a committee can picture the first grant proposal and the first few papers, along with what resources (space, equipment, students, collaborators) each would require. This is the section committees weight most heavily, because it’s the one that answers whether the program is fundable and independent.

A useful frame many research-development offices and career centers use: the future-direction section should read like the seed of an actual grant proposal — a funder-ready problem statement, specific aims, and significance — not a vague statement of interest. Committees that also sit on grant review panels (which, at research-intensive institutions, is most of them) are reading with exactly that lens.

Length and formatting norms

Length conventions vary meaningfully by field, and following the wrong field’s norm is a common, avoidable mistake:

Humanities: typically 1-2 pages, often prose-heavy with few or no headings.
Social sciences: typically 2-3 pages.
STEM / lab sciences: typically 3-4 pages, frequently using subheadings for distinct project lines, and sometimes including a figure or diagram of the proposed research program.

Because these ranges vary by field, sub-field, and even by individual search committee’s stated preference, the single most reliable check is the job posting and department norms — some ask for a hard page limit explicitly; where none is given, asking a current faculty member in the target field or department, or a postdoc mentor who has recently served on a search committee, is more reliable than defaulting to a generic word count. When in doubt, err shorter: an unnecessarily long statement signals an inability to prioritize, which is itself a negative signal to a committee evaluating whether someone can write a tightly scoped grant aim.

On formatting: write for a generalist reader. Search committees are rarely composed entirely of narrow subfield specialists, and grant review panels even less so. Avoid subfield jargon without a gloss, keep paragraphs short (rarely more than half a page), and open each major section with a sentence a non-specialist committee member could restate accurately.

What belongs in the future-direction section specifically

This is the section that does the most work, so it’s worth being concrete about what a strong version contains for each proposed project or research line:

The specific question or gap, stated so a non-specialist understands both what’s unknown and why it’s worth answering.
The general approach — methods, model system, dataset, or technique — without turning it into a full methods section.
What resources it needs: space, equipment already at the target institution vs. equipment the candidate would need to acquire, student/postdoc labor, and (where relevant) which specific funding mechanisms the candidate would target — an NIH R01 or K99/R00 pathway, an NSF CAREER award, a foundation grant, or similar.
How it connects to, but is independent of, the candidate’s postdoctoral or dissertation advisor’s program — committees are actively checking for this, since a research statement that reads as a continuation of the advisor’s grant rather than a distinct program is a red flag for independence.
How it connects to the target department specifically — shared instrumentation, a potential collaborator already on faculty, a course the candidate could build around it, or a strength of the institution the proposal leans on.

How a research statement differs from adjacent documents

Candidates frequently blur these documents together, which weakens all of them. Each has a distinct job in the packet:

Cover letter: a short (1-2 page) transmittal letter that summarizes fit for the specific position and points the reader to the fuller documents attached — it should not duplicate the research statement’s depth.
Personal statement: where used (more common in medicine, some fellowships, and some non-US systems), this addresses the candidate’s personal trajectory and motivations for a specific opportunity — fit and narrative, not a research program.
Teaching statement: a separate document (usually 1-2 pages) covering pedagogy, teaching philosophy, and specific courses the candidate could teach — research and teaching statements should not be merged even when a job posting only explicitly asks for a single “statement.”
Diversity statement: addresses the candidate’s contributions to diversity, equity, and inclusion in research, mentoring, or teaching — see CASRAI’s diversity statement guide for what reviewers look for there specifically. It is not the place for future-research planning, and the research statement is not the place to address DEI contributions if a separate diversity statement is requested.
NIH/NSF biosketch: a structured, format-constrained CV supplement used in grant applications (see CASRAI’s NIH biosketch worked example) — it documents past accomplishments in a fixed format, and is not a substitute for the freer-form future-direction narrative a research statement provides, even though the two documents often draw on the same underlying research plan.

Common mistakes

Front-loading the past instead of the future. Committees already have the CV and publication list; a research statement that spends most of its length recapping completed work under-delivers on the one question only this document answers well.
No independence signal. Failing to distinguish the proposed program from the advisor’s ongoing grant, especially for candidates applying straight out of a single long postdoc.
Too many projects, too little depth. Listing five or six loosely related project ideas reads as unfocused; two to four well-developed lines with clear sequencing (what gets funded and started first) reads as a program.
Ignoring institutional fit. Sending an identical statement to every department without adapting the fit framing, resources referenced, or potential collaborators named.
Overusing subfield jargon. Search committees and, later, study sections include generalists; a proposal only a narrow specialist can follow will not clear either bar.
Treating it as a solo writing exercise. The strongest statements go through several rounds of feedback from mentors, ideally including someone who has recently served on a search committee or study section in the target field.

Frequently asked questions

How long should a research statement be?

It depends heavily on field: roughly 1-2 pages in the humanities, 2-3 in the social sciences, and 3-4 in STEM/lab sciences, though individual departments and job postings sometimes specify an exact limit — follow that limit over any general convention when one is given.

Is a research statement the same as a research proposal?

Not quite. A research statement covers a broader multi-year program across several projects, written for a hiring or tenure committee; a research proposal (e.g., a grant application’s specific aims and research strategy) targets one funding mechanism’s format and a narrower scope. A well-written research statement’s future-direction section is often the seed a candidate later expands into their first grant proposal after being hired.

Should a research statement include figures?

In STEM fields, a schematic figure summarizing the overall research program (e.g., how proposed project lines relate to each other) is common and often useful; it’s rare in humanities and social-science statements, where the document is closer to a narrative essay.

Do research statements matter for tenure review, not just hiring?

Yes, at many institutions — a version of the research statement (updated to reflect what was actually accomplished versus what was proposed at hiring) is often a required component of the tenure dossier, so it’s worth keeping the hiring-stage statement as a document to revisit and update, not a one-time artifact.

Who should review a draft before submission?

Ideally a mix of a close mentor familiar with the specific research (for scientific accuracy) and someone outside the immediate subfield or a faculty member who has recently served on a search committee (for whether the framing lands with a generalist reader) — both perspectives catch different weaknesses.

For the broader mechanics of an academic job application packet and the research-administration side of what happens after an offer, see CASRAI’s guide to what a research administrator does and the Certified Research Administrator (CRA) credential for the administrative-career track alongside the faculty-track path this guide focuses on.