Research Proposal or Life Story in Your SOP?

Research Proposal or Life Story? How Professors Actually Read Your SOP

The University of Alabama's history department tells doctoral applicants: "PhD applicants should describe the project they wish to undertake for their dissertation. You should write an ample paragraph here!"

Susan Athey, the Economics of Technology Professor at Stanford Graduate School of Business, tells applicants the opposite: "Its not necessary to have a specific thesis proposal, and odds are if you try to pretend you have one when you really don't you'll come off as sounding naive which is a bad thing."

Both are describing a real reading process. The gap between them is where most applicants get lost, so it is worth mapping carefully.

Camp one: the statement is a research document

A substantial group of faculty and departments treat the statement as a technical artifact that happens to be written in the first person.

Mor Harchol-Balter, the Bruce J. Nelson Professor of Computer Science at Carnegie Mellon, says it directly in her long-running applicant guide:

It's misleading that the personal statement is called a "personal" statement, since what admission committees are really looking for is a research statement. What admission committees want is a statement about what research you have done, what research you hope to do, and why you like research.

The University of Florida's biology department renames the document outright: "You are asked to provide a Statement of Purpose, which we expect to be a Research Statement."

UC San Diego's power and energy systems program gives applicants a proposal instruction — "Identify a research gap in the literature" — which is a research-proposal move, not an autobiographical one.

And a faculty applicant guide hosted by Notre Dame's biological sciences department sets a ratio: "Keep your personal statement more about your research (90%)."

Camp two: cut the origin story

Closely allied, and often mistaken for the same camp, is a group whose real target is not narrative but unspecific narrative — the childhood scene, the declaration of passion, the flattery.

Roger Maioli, associate professor and associate chair in the University of Florida's Department of English, names the trap precisely:

"The professors reading these applications may love literature (it's often what brought them to the field), but they expect you to write as a scholar who studies literature rather than as a reader who enjoys it."

Carnegie Mellon's electrical and computer engineering department is blunter: "Avoid common clichés in your SoP. In particular, try to avoid childhood anecdotes or goals. The admissions committee is interested in your current goals, skills, and strengths."

The University of Toronto's computer science department uses capital letters: "Do NOT include tales about your childhood and how you've always loved computers. This type of information is irrelevant and suggests that you are unfocused or have little to say."

UC San Diego's economics department applies the same edit to enthusiasm: "While showing interest in research in economics is important, don't spend too much time describing your passion for economics. This will be unlikely to persuade admissions committees. Get to specifics as soon as possible."

And the University of Washington's Department of English hosts an excerpt from an article by Steven Olswang that states the rule in one line: "The Statement of Purpose should not relate a life story or flatter either the applicant or intended readers."

Camp three: the statement is a person thinking

Then there are departments that ask for the opposite emphasis, and are just as explicit about it.

The University of Pittsburgh's biological sciences department asks applicants to drop the performance:

"The practice of science includes both successes and setbacks, and there is no perfect set of experiences. So, try to use your own voice and be frank, rather than anticipate what you think we might want to hear."

UCLA's sociology department lists three admission criteria, and one of them is explicitly biographical: "The Admissions Committee considers a strong applicant to have well-conceived research interests, past research accomplishment, and intellectual biography."

The molecular biology admissions committee at the University of Colorado Anschutz Medical Campus asks: "What sets you apart? Give some insights into who you are as a person and as a scientist."

And Dartmouth's molecular and cellular biology program asks for narrative with a constraint attached: "Ground your answer in one or two specific moments or turning points rather than a general summary."

That last clause is the reconciliation, and it is worth sitting with. The anti-narrative camp is not banning your history. It is banning history that carries no information.

The disagreement about form

Once you accept that the document contains both purpose and evidence, faculty split again on what shape to pour it into.

Roman Feiman, assistant professor of cognitive and psychological sciences at Brown, proposes an architecture in advice the department publishes for applicants:

So, if not a compelling autobiography, what should your applicants write? I propose we ask them to produce a statement "in three acts," each of which would convey a key piece of information

Tom Alberts, associate professor of mathematics at the University of Utah, prefers a different genre entirely: "In general, I prefer personal statements that are structured more along the lines of a cover letter for a job. I am most interested in reading about a student's current interests in mathematics and why they believe my department's program is a good fit, rather than a lengthy description of what first drew the applicant towards mathematics."

Three acts or a cover letter. Both readers exist. Both are reading for the same thing underneath: current purpose, supported.

The part nearly everyone agrees on: it is not a contract

Here is the reassurance that the proposal camp itself supplies, and that anxious applicants almost never see.

Harchol-Balter, in the same guide that calls the document a research statement, adds:

"It's important to realize that the research statement is not a commitment to do research in that area. A third of all applicants end up working in an area different from that which they described on their research statement."

Harvey Mudd's computer science department says the same thing about naming a subdiscipline: "This is not a contract that forces you to study that subdiscipline and you might change your mind later." The same page still advises naming one, and being as specific as you can.

The University of Iowa's political science department builds the caveat into the instruction: "Please know that this is not a firm commitment: as their studies continue, most graduate students shift and refine their focus. We're looking for a sense of where you'll be starting from."

The University of Texas at Austin's mathematics department gives applicants explicit permission to be uncertain: "(Note: some applicants have a very clear idea of what mathematical directions interest them; others far less. That's fine; be clear and honest.)"

So the Alabama and Athey positions are less opposed than they first look. Alabama wants a project described. Athey warns against a project faked. The failure mode both are pointing at is the same one: a proposal you cannot discuss.

What to do with a draft

Work in this order, and the camps stop fighting.

1. Lead with present purpose. What you want to work on now, in the vocabulary of the field. Both camps read the first paragraph for this.
2. Attach evidence to every claim. A project, a course, a result, a failure you can characterize. This is what the research-dossier camp is asking for and what the voice camp accepts as candour.
3. Keep origin material subordinate and specific. A turning point that changed what you work on can stay. A childhood scene that only proves you like the field cannot.
4. Say how fixed your direction is. "This is where I would start" is a legitimate sentence. Iowa, UT Austin, Harvey Mudd, and Harchol-Balter all say so in different words.
5. Read the department's own page before choosing the shape. If it says "research statement," give it one. If it asks who you are as a scientist, answer that too.

A review against a published rubric is a fast way to see which of these camps your current draft is already satisfying, and which one it is only gesturing at.

Related reading

• Should you name a professor in your SOP? — the other big disagreement among SOP readers
• Five types of graduate school purpose evidence — what counts as support for a claim
• SOP mistakes: the kisses of death — the failure patterns readers name most often
• The hidden rules of the SOP genre — why these conventions stay unwritten
• What CS professors look for in an SOP — one field's advice, in its own words

All quotations in this article were re-checked against their live source pages on 16 August 2026. Departmental guidance changes; verify against the program page you are applying to.