Describe a Co-Authored Paper in Your SOP

Describe a Co-Authored Paper in Your SOP

Describe a co-authored paper in one contribution sentence: what you did, in plain role verbs your recommender can confirm, plus the paper's status. Your place in the byline goes on the CV, with every author listed in the published order.

Our view: the byline is the weakest evidence you have. "Second author" does not tell a US faculty reader whether you ran every experiment or edited one section, and "co-first author" means only what your lab agreed it means. A sentence that names your work does what the position cannot. If your research paragraph is already drafted, a PhD statement of purpose review reads it for exactly this: your own role in the work.

Every university and standards page quoted below was checked on October 31, 2026. Application forms change each cycle, so recheck where your target program wants publications listed before you submit.

Where each program wants your publications

Five official pages, read together, split the job: the list goes on the CV or a form, and the statement explains your part.

Four of the five put the publication list outside the statement. Berkeley is the one that tells you what the statement must add, and its four items are a usable formula: who you worked with, the project title, your responsibilities, and the outcome. Berkeley also says why the wording matters: "Write technically, or in the style of your discipline. Faculty are the people who read these statements."

Why the byline cannot carry your role

Author order is a convention, and nothing on the printed paper tells a reader which convention your lab used. The research community already keeps two separate records: who is on the paper, and who did what. NISO's CRediT role descriptors list "the 14 roles included in the Contributor Role Taxonomy (CRediT)" and say plainly that CRediT "is not designed to determine authorship; publishers adhere to strict guidelines around what qualifies as authorship."

That split is the useful part for an SOP. Borrow the role names as verbs: investigation (CRediT: "specifically performing the experiments, or data/evidence collection"), software, formal analysis, methodology, visualization, writing the original draft. Pick the two or three that are true for you. If the journal printed a contribution statement with your paper, your SOP must not contradict it.

The contribution sentence, in five parts

Write one to three sentences per paper you choose to discuss, in this order:

1. Project and people. The lab or PI and the paper's title, per Berkeley's "with whom" and "title of the project".
2. Your role, in verbs. Two or three CRediT-style roles that are true.
3. One decision you made. A choice, a fix or a failure you traced. This is the line a byline can never show.
4. The result. What the paper reports that depends on your part.
5. Status. Published, accepted, under review or in preparation, labelled exactly as the editor's last message allows. The guide to listing papers under review covers each label.

A sentence that stops after part 1 is a CV line with a verb. Part 3 is what makes it a research paragraph.

Four byline cases and what each sentence must add

Second author who ran the experiments. This is the case where position undersells you most. Say what you ran and built, then credit the first author's part in one clause. Credit is what makes your claim believable.

Co-first author. Do not write "first author". Use the paper's own mark ("equal contribution", an asterisk note) on the CV exactly as printed, and in the SOP name your half: "I designed the data pipeline; my co-first author designed the model."

One of many names. On a large paper, the honest sentence is small: one task, its size, and what it fed. "I calibrated the timing data for one detector subsystem" is stronger than any sentence about the paper's headline result, because a letter can confirm it.

First author on a Chinese-language paper. A US reader cannot open it. Give the English title in the SOP once, mark it "(in Chinese)", and say what the paper found in one clause. On the CV, keep the original title and add your translation in brackets. If the journal publishes an English title for the paper, use that one. Otherwise call it your translation. Never call it official.

The countercase: position does carry information when you are the sole student author and the paper is the direction you are applying to continue. Even then, lead with the decision, and let the CV show the position.

Keep the SOP, CV and letter telling one story

A reader can set three documents side by side: the CV entry, your SOP sentence, and your PI's letter. If your SOP says you "led" the project and the letter says you "assisted", the file contradicts itself, and only one of those documents is yours.

Before you submit:

1. Copy the author list and title from the published or submitted version, not from memory.
2. Check that the status label is the same on the CV, the SOP and any application form field.
3. Check that the verbs in your SOP are verbs your PI would use.
4. Send your PI a short list of facts: the paper, your tasks, the dates, the outputs. Do not send draft letter text. Stanford's application terms bar applicants from drafting their own letters; the summer research guide quotes the rule.
5. Delete any paper from the SOP that you cannot describe in the five-part sentence. It stays on the CV.

Berkeley EECS suggests the same kind of fact package for recommenders: "you may want to prepare packages for them that include copies of work you have done with them, transcripts, and a resume/CV" (Berkeley EECS graduate admissions FAQ).

Constructed example: a second-author paragraph, before and after

Constructed example, written by us, not a real applicant statement. Context (invented): a final-year student at a Chinese university is second author on a robotics paper. The first author designed the planner. The PI, "Professor H. Lin", is last author.

Before:

I published a paper at an international robotics conference as second author. This experience greatly improved my research ability and taught me the importance of teamwork. It made me determined to pursue a PhD in robotics.

After:

In Professor H. Lin's lab I worked on "Grasp Planning for Cloth Under Partial Observation" (second author; accepted, 2026). The first author designed the planner; I wrote the simulation benchmark and ran all evaluation trials. When the planner failed on thin fabrics, I traced the failures to a sensor-noise model I had reused from an earlier project, replaced it, and re-ran the full set. That fix is why the paper reports three fabric types instead of two, and it is why I want to work on perception under uncertainty rather than planning.

The first version gives a position and a feeling. The second gives Berkeley's four items (with whom, title, responsibilities, outcome), separates the first author's part from the applicant's, shows one decision, and ends on a research direction. Professor Lin's letter can confirm every clause.

Questions about publications in a PhD SOP

Should I name the journal or conference?

Yes, once, with the status. The CV carries the full citation, so the SOP does not need the volume, pages or DOI.

Should I mention the impact factor or a venue ranking?

No. Faculty in your field already know the venues, and a metric is a claim about the paper, not about your part in it. Spend the words on the decision you made.

Does every paper need a sentence in the SOP?

No. Stanford CS and Princeton SPIA both ask for the full list on the form or the CV. The SOP takes the one or two papers that show where you are going. If you have none, the guide to a PhD SOP with no publications covers what replaces them.

My PI is the last and corresponding author. Do I explain that?

No. Do not explain conventions. Explain your role, and the reader can work out the rest.

Can I cite my own paper with a reference in the SOP?

Only if the program's format allows references. The guide on citing papers in a PhD SOP covers when a citation helps and how to cite your own work without making its status unclear.

Get a free review of your statement of purpose

Get a free Quick Review of your PhD statement of purpose against GradPilot's research dossier rubric. It reads whether your past research shows how you think and what you can do, and whether the writing stays on your own role in the work. For a broader read of research direction, preparation and program fit, use the general PhD statement of purpose rubric.

More research-paragraph guides:

• Turn a thesis abstract into SOP evidence: the same five-part logic for a thesis.
• Research technician to PhD: showing your role when you executed someone else's design.
• CV for grad school applications: where the full publication list goes.
• Summer research internship in your SOP: a short project with no paper yet.
• More PhD writing guides are in the PhD essays hub.

Sources

Retrieved October 31, 2026, except where noted.

• UC Berkeley Graduate Division, Writing Your Statements (no cycle stated): research paragraph items; "Faculty are the people who read these statements."
• Stanford Computer Science, PhD Admissions Frequently Asked Questions (no cycle stated): publications on the supplementary form and resume.
• Princeton School of Public and International Affairs, Ph.D. Application (December 1, 2026 deadline cycle): résumé or CV contents.
• Carnegie Mellon School of Computer Science, Graduate Admissions (no cycle stated): resume contents.
• MIT EECS, Graduate Admissions FAQs (no cycle stated): copies of journal articles discouraged; links in the honors box.
• NISO, CRediT role descriptors (undated): 14 roles; CRediT does not determine authorship.
• UC Berkeley EECS, Graduate Admissions FAQ (no cycle stated): recommender packages.