Skip to main content
v2026.11,986 entries · CC-BY 4.0

How to Write a Research Statement for a Faculty Application

How to write a research statement for a tenure-track faculty job application: structure (past, present, future), length by field, what belongs in the future-direction section, and how it differs from a cover letter, personal statement, teaching statement, diversity statement, and biosketch.

Written and maintained by CASRAI Editorial Board

Published · Last updated

On this page

A faculty research statement is a short document that summarizes your past research, your current work and, above all, the research program you would build as an independent investigator. University career offices typically recommend about 2–5 pages (the figure varies by office and field, as the data table below shows), organized as past, present and future, with the future section carrying the most weight. If the job advertisement sets a page limit, that limit overrides every general guideline.

The statement sits alongside the cover letter, CV, teaching statement and (where requested) a diversity statement in a tenure-track packet, but it does a different job than any of them: it is the document a search committee reads to decide whether this person has a fundable, independent research program, not just a strong publication record built in someone else’s lab.

This guide covers what a research statement needs to contain, how long it should be according to published university guidance, how committees read it, three alternative structures, how it differs from adjacent documents — personal statement, teaching statement, cover letter and NIH/NSF biosketch — and the mistakes that most often weaken it.

Want to see one filled in, not just the rules? This guide covers structure, length, and common mistakes. For a labeled, worked example showing what an actual past/present/future research statement looks like on the page, see CASRAI’s research plan template.

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 the record just a list of projects done for other people? Is there a fundable, independent research program here — one that does not depend on a former advisor’s lab, reagents or grant? And does that program fit what this specific department or institution offers: instrumentation, student population, existing strengths, space?

The third question is why a generic statement performs poorly even when the science in it is strong. A statement that reads as “here is what I did” and nothing more does not show where the work goes next or why the target department is the right place for it. University career offices consistently advise tailoring: Penn Career Services, for example, says the student-involvement plans in a statement must fit the institution, that you should name resources the institution actually has, and that you should not mention graduate students if the department offers only undergraduate programs. The University of Washington’s careers office likewise advises making the plan realistic for the type of institution, from a liberal arts college to a major research university, including how undergraduates would take part.

Structure: past, present, future

The most commonly taught arc organizes the statement around three parts, even where the section headings vary or disappear:

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

A useful test for the future section is that it should read like the seed of an actual grant proposal — a clear problem statement, specific aims and significance — not a vague statement of interest. Committees at research-intensive institutions often include people who also sit on grant review panels, and they read with that lens.

Alternative structures

Past/present/future is the framing Penn Career Services uses, but it is not the only published model. Two others are worth knowing, because the right one depends on the field and on how much of the statement must cover fit.

  • Proportional split (MIT Communication Lab). The MIT Communication Lab’s faculty-application CommKit suggests roughly 25% introduction, 25% alignment with the department, and 50% on your research areas.
  • Six-paragraph model (CU Boulder Career Services). Colorado’s guidance for academic statements lays the statement out as a one-page, six-paragraph sequence in which the fourth paragraph covers publications and the fifth covers your next project; the publications paragraph (the fourth) can expand to two or three paragraphs when you have additional research projects.
  • Research thrusts (MIT CAPD). For STEM fields, MIT’s Career Advising and Professional Development office describes organizing the plan as 2–3 research thrusts that you would pursue over your first 3–6 years.

These models agree on the essentials: a short orientation, an explicit link to the hiring department, and most of the space given to forward-looking research.

How long should a research statement be?

Published guidance does not agree on one number, and several offices say outright that the posting controls. The data table below compares what five university career or communication offices state about length and about the number of future projects to describe, using the figures each page gives.

Three things stand out when reading the sources side by side:

  • The ranges disagree. CU Boulder describes a one-page, double-sided statement. The University of Washington gives 1–3 pages and notes that a longer statement is sometimes appropriate. MIT’s CAPD says 3–5 pages not including citations. Penn says 2–3 pages and notes that the count depends on how many images, illustrations or graphs you include. The MIT Communication Lab’s aerospace-engineering CommKit states 2–4 pages.
  • The field matters, but the sources do not give a clean field-by-field table. Penn says separate research statements are usually requested in engineering, social, physical and life sciences, and that in many humanities fields the research content is folded into the cover letter. MIT CAPD says that in the humanities and social sciences the statement explains how you will complete the key tenure project, such as three articles or a book.
  • The posting beats any convention. CU Boulder explicitly tells applicants to follow the application’s own length instructions. If no limit is given, ask a faculty member or recent search-committee member in the target field.

When in doubt, shorter is safer. A statement that runs long signals difficulty prioritizing, which is a poor signal from someone who will have to write tightly scoped grant aims.

How committees read a research statement

The MIT Communication Lab’s CommKit models three reading depths: roughly 20 seconds, 2 minutes and 10 minutes. Its advice follows from that: put the vision in one or two sentences at the top, on a scale of what you want to accomplish over a career (the CommKit frames this as roughly a 20-year horizon), and make sure the core research areas appear on the first page, so that a reader who stops early still learns what the program is. Detailed implementation, such as methods and experimental steps, belongs in the job talk rather than the statement.

The CommKit also lists what faculty reviewers say they evaluate: creativity, technical communication, knowledge of the field, collegiality, fit with the department, overlap with existing research, potential for growth and ability to attract funding. Reading your own draft against that list, one criterion at a time, is a practical editing method. Overlap deserves particular care: the same page that shows a gap your work fills should also show how it complements, rather than duplicates, what the department already does.

What belongs in the future-direction section

This section does the most work, so it is 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 is unknown and why it is worth answering.
  • The general approach — method, model system, dataset or technique — without turning it into a full methods section.
  • The resources it needs: space, equipment already at the target institution versus equipment you would have to acquire, student or postdoc labor, and where relevant the funding mechanisms you would target — an NIH R01 or K99/R00 pathway, an NSF CAREER award, a foundation grant or similar.
  • How the project connects to, but is independent of, your doctoral or postdoctoral advisor’s program. Penn, UW and the MIT CommKit all stress that the plan must be distinct from your advisor’s work, since a statement that reads as a continuation of the advisor’s grant is a red flag for independence.
  • How it connects to the target department — shared instrumentation, a potential collaborator on faculty, a course you could build around it, or an institutional strength the proposal leans on.

How many projects should the future section describe?

The sources give a range rather than a rule. Penn suggests four or five specific aims, divided into short-term and long-term and tied to a five-year plan. MIT CAPD suggests two to three research thrusts for the first 3–6 years in STEM. The University of Washington suggests two or three feasible ideas, depending on field, and recommends separating short-term goals (about 2–5 years) from long-term goals (5 years and beyond). The MIT CommKit for aerospace engineering suggests two or three core research areas. The common thread is a small, sequenced set — enough to show a program and few enough that each is developed — with the next two to five years concrete and the longer horizon sketched.

Humanities and social sciences versus STEM

The statement’s form shifts with the field. Penn notes that engineering, social sciences, physical sciences and life sciences usually ask for a separate research statement, whereas in many humanities fields the research description is folded into the cover letter, so check what the posting actually requests before drafting a standalone document. MIT CAPD adds that for humanities and social-science applicants the plan should explain how you will complete the key project needed for tenure, for example three articles or a book, rather than laying out a laboratory pipeline. STEM statements, by contrast, tend to use sub-headings for distinct project lines and sometimes a program-level figure; Penn notes that the page count can depend on how many images, illustrations or graphs are included.

Tailoring by institution type

A statement written for a research-intensive university and one written for a teaching-focused college should not be identical. The MIT CommKit distinguishes R1 institutions from teaching-focused ones, and the guidance cited above points the same direction: name resources the institution really has (Penn), match the scale of the plan to the type of institution and describe realistic undergraduate involvement (UW), and state your intent to seek grants where the institution expects it (Penn). A statement that promises a large graduate-student-driven program to a department with no graduate students signals that it was not written for that department.

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 transmittal letter that summarizes fit for the specific position and points the reader to the fuller documents. MIT CAPD gives about 1–1.5 pages for a faculty cover letter; it should not duplicate the research statement’s depth.
  • Personal statement: where used (more common in medicine, fellowship applications such as the Fulbright statement of grant purpose, and some non-US systems), it addresses your personal trajectory and motivation for a specific opportunity — fit and narrative, not a research program.
  • Teaching statement: a separate document covering pedagogy, teaching philosophy and courses you could teach; MIT CAPD gives about 1–2 pages. Research and teaching statements should not be merged even when a posting asks for only a single “statement”.
  • Diversity statement: addresses your contributions to diversity, equity and inclusion in research, mentoring or teaching (MIT CAPD gives about one page). See CASRAI’s diversity statement guide for what reviewers look for. It is not the place for future-research planning, and the research statement is not the place for those contributions when a separate statement is requested. Some institutions use other names, such as inclusion, perspective or service statements; Penn’s guide to other faculty application documents describes these variants.
  • Mentoring statement: MIT CAPD also lists a mentoring statement of about one page where an institution requests one.
  • 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.

What if the advertisement asks for a combined statement?

Some postings ask for research, teaching and other content in one document with a cap. Penn’s guidance shows examples with limits such as a maximum of two pages and no more than three pages. In that case, follow the cap exactly, allocate space according to the posting’s priorities, and cut implementation detail first; the full research plan can move to the job talk.

Is a research statement the same as a research plan?

Institutions label this document differently, so read the posting for what it asks the document to contain rather than relying on the title. Our research plan template shows a worked version. A research statement also differs from a grant proposal: it covers a broader multi-year program for a hiring committee, whereas a proposal targets one funder’s format and a narrower scope, though a strong future section is often the seed of the first proposal.

Research statement example: an annotated skeleton

A research statement example is most useful when you can see what each paragraph is for. The skeleton below follows the past, present and future arc described above, with the job of each paragraph in brackets; replace the bracketed prompts with your own specifics. It is a structural template, not a finished statement, and it assumes a single-spaced one-to-two-page document, the length Binghamton University’s career office gives as usual (Binghamton Career Tools).

Paragraph What it does Prompt to fill in
1. Vision States the research program and why it matters in one or two sentences [The question my group will answer, and the broader problem it serves]
2. Past work Shows the thread running through doctoral and postdoctoral work [Two or three findings, each tied to the same question, with the papers that report them]
3. Current work Describes work in progress and under review, in language an adjacent subfield follows [What is underway now and what it will show]
4. Future project one The nearest-term line: question, approach, resources, expected first papers [Aim, method or model system, equipment and people needed]
5. Future project two A second line, sequenced after or alongside the first, independent of your advisor [How it extends the program and how it differs from my advisor’s work]
6. Fit and funding Names departmental resources, possible collaborators and the funding mechanisms you would target [Shared facilities, colleagues, courses, and the agencies or foundations that fund this work]

For finished samples, the University of Washington’s careers office links example statements by discipline, among them biology, physics, engineering, mathematics, computer science, sociology and philosophy, hosted by universities such as Stanford, UC Santa Barbara, UC Irvine, NYU and Duke (UW Careers, Research Statements). Read two or three from your own field before drafting, because the conventions differ by discipline. CASRAI’s research plan template also walks through a labeled version.

Research statement for a postdoc application

A postdoc research statement answers a narrower question than a faculty one: what you will do in this lab, and why you are ready to do it. The University of Washington’s guidance notes that postdoc statements can cover more research projects than a recent graduate’s, because postdocs have more work to show, and advises tailoring each statement to the specific opportunity and checking the norms with faculty in your field (UW Careers). In practice, keep the past and present sections but replace the independent-program sections with one or two projects that fit the host group’s methods and questions.

Fellowship programs that fund postdocs ask for related documents with their own rules. See, for example, CASRAI’s guides to the NSF PRFB postdoctoral fellowship in biology and the EMBO postdoctoral fellowship before adapting a faculty statement for either.

Common mistakes

  • Front-loading the past instead of the future. Committees already have the CV and publication list; a 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. The sources above recommend roughly two to five sequenced projects or aims, depending on the source; a list of five or six loosely related ideas reads as unfocused.
  • Ignoring institutional fit. Sending an identical statement to every department without adapting the fit framing, the resources referenced or the collaborators named.
  • Burying the vision. Under the CommKit’s reading model, a reader who only skims should still learn the program from the first page.
  • Too much implementation detail. Experimental steps and minor technical choices belong in the job talk, not the statement.
  • Overusing subfield jargon. Search committees and, later, study sections include generalists; a proposal only a narrow specialist can follow will not clear either bar.
  • Skipping outside feedback. Penn recommends feedback from an advisor and other faculty; the MIT CommKit recommends starting early and seeking readers from different fields and seniority levels; UW suggests having at least one person proofread.

Frequently asked questions

How long should a research statement be?

Published university guidance ranges from one page (CU Boulder) to 3–5 pages excluding citations (MIT CAPD), with Penn at 2–3 and UW at 1–3. Follow any limit in the job posting over a general convention; when none is given, ask faculty in your field.

Is a research statement the same as a research proposal?

Not quite. A research statement describes a multi-year program for a hiring or tenure committee. A research proposal, such as a grant’s specific aims and research strategy, targets one funding mechanism and a narrower scope.

Do humanities applicants need a separate research statement?

Not always. Penn notes that in many humanities fields the content is folded into the cover letter; check the posting. Where a statement is requested, MIT CAPD says to explain how you will complete the key tenure project, such as three articles or a book.

Should a research statement include figures?

In STEM fields a schematic summarizing the overall program is common, and the MIT CommKit suggests figures that relate the vision to the research areas. Penn notes that figures affect page count. They are rare in humanities and social-science statements.

What should a research statement leave out?

Minor implementation details, which the MIT CommKit assigns to the job talk, plus anything duplicated from the CV, and diversity or teaching content when separate statements are requested.

Can I reuse the same statement for every application?

The core program can be reused, but the fit section, named resources and student-involvement plans should be rewritten for each institution, as Penn and UW advise.

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

At many institutions a version of the statement, updated to reflect what was accomplished versus what was proposed, forms part of the tenure dossier, so keep the hiring-stage statement as a document you can revisit.

Who should review a draft before submission?

A close mentor for scientific accuracy and someone outside the immediate subfield, ideally a faculty member who has served on a search committee, for whether the framing lands with a generalist reader.

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.

Sources

Sources (accessed 2026-11-13):

Further reading: research plan template — How to structure a faculty job-application research plan: past/current/future research sections, typical length, common weaknesses, and how it differs from an NIH Specific Aims page or grant proposal.

Further reading: Promotion and Tenure Narrative Statement — What a promotion and tenure narrative statement is, how it differs from a CV and from separate research, teaching, and diversity statements, and how structure and emphasis shift between research-intensive and teaching-focused institutions.

Data: Research statement guidance for faculty job applications: length and number of future projects, by university career-office source

Original side-by-side compilation of what five university career or communication offices state about faculty research statements: recommended length and the number of future projects or aims to describe. Compiled by reading each office's public guidance page; blank cells mean the source states no figure. Page limits in an actual job advertisement override all of these.

Period covered: 2026. Coverage: United States.

Research statement guidance for faculty job applications: length and number of future projects, by university career-office source
Source (office)Research statement length, minimum (pages)Research statement length, maximum (pages)Future projects or aims suggested, minimumFuture projects or aims suggested, maximumLength note
University of Pennsylvania Career Services2345Depends on number of images, illustrations or graphs; 4-5 specific aims split into short-term and long-term, with a 5-year plan
MIT Career Advising & Professional Development3523Not including citations; STEM: 2-3 research thrusts over first 3-6 years
University of Colorado Boulder Career Services111 page double-sided; follow the application's own length instructions
University of Washington Career & Internship Center1323Longer sometimes appropriate; 2-3 feasible research ideas depending on field
MIT Communication Lab (aerospace engineering CommKit)24232-4 pages stated for aerospace engineering; 2-3 core research areas

Sources

Compiled by CASRAI from the sources above. Free to reuse under CC BY 4.0 with attribution.

Follow CASRAI

Research-administration guidance, standards updates and independent tool reviews.

Ask CASRAI · free to try

Ask about How to Write a Research Statement for a Faculty Application

2 free questions a day, no account.

An AI assistant for research: funder rules, compliance, methods and publishing. It links the sources behind its answers and labels answers that come from a web search.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays open to read, with no account and no card.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →