Graduate CVs And Résumés

You open an old job résumé, add your undergraduate degree, and save it as “Graduate CV.” The file is tidy, but it still gives most of its space to duties that have little connection to the training you want. Meanwhile, the substantial project that led you toward graduate study occupies one vague line.

The problem is not the filename. A graduate application document should help a reader find relevant preparation and understand your contribution. Start with the program's instructions, then decide what evidence deserves space.

Let The Application Determine The Format

There is no universal U.S. rule that every graduate applicant must submit an academic CV. Princeton's Graduate School requests a résumé or curriculum vitae and lists education, employment, activities, service, and honors among the content. [1] Columbia's French MA also permits a CV or résumé, alongside separate statements, recommendations, and writing samples. [2]

Before choosing a template, record the exact document requested, any page or file limit, required content, and whether the department adds instructions beyond the graduate school. A portal asking for a two-page résumé is not an invitation to submit a ten-page CV. If the program permits either document and provides no further preference, choose the structure that presents your relevant experience clearly.

Career guidance can explain conventions without becoming an admissions rule. Columbia GSAS describes the CV as a comprehensive academic record and the résumé as a concise account of selected qualifications. [3] Cornell likewise distinguishes the documents by purpose and advises consulting people familiar with disciplinary conventions. [4] Neither distinction means that a longer submission earns more credit.

Build A Complete Record, Then Select

Create a private master record before editing the version you will submit. Include dates, role titles, degree details, project descriptions, relevant methods, teaching, employment, service, awards, presentations, and any publications. Keep source documents nearby so you can verify the information.

Then ask what the proposed degree needs the reader to understand. For a research application, substantial scholarly work may deserve a prominent section. For a professional master's, a relevant workplace project may show applied preparation. Both can include academic and professional evidence; the balance comes from the program and your background, rather than a rigid rule about degree names.

Use headings that make the distinctions visible. “Research Experience,” “Selected Projects,” “Professional Experience,” and “Teaching” can be clearer than one undifferentiated list. An early-career applicant does not need every heading. Empty publication sections, a page of generic skills, and unrelated material added to fill space do not help a reader understand readiness.

Harvard Griffin GSAS treats the résumé/CV and employment history as application materials that must accurately reflect the applicant's own work. [5] Keep that ownership principle in view as you adapt your document. Clear organization should make the facts easier to assess, not change them.

Describe The Work You Actually Did

A useful entry answers four questions: what was the project, what was your responsibility, how did you approach it, and what output or learning can you substantiate? You do not need a dramatic numerical outcome for every line.

Consider a fictional undergraduate who contributed to a public-transport research project. A weak description reads: “Worked on important transportation research and improved analytical skills.” It supplies almost no evidence.

A more informative hypothetical entry could read:

Undergraduate Research Assistant — Urban Mobility Project, September–May

• Cleaned and linked publicly available bus-arrival records for a supervised analysis of service reliability.
• Compared missing-data patterns across routes and documented exclusions in a reproducible analysis notebook.
• Presented a poster explaining the data limitations and the team's proposed next checks.

These are invented details for a writing example. A real applicant should include only work they performed and can explain. Notice that the entry identifies a contribution without claiming to have led the whole study, discovered a causal effect, or published a paper.

For a professional résumé, the same project might be condensed into two lines emphasizing the relevant analysis and communication. For a research CV, the project and poster might appear in separate sections if that makes the record clearer. Do not count the same output twice without making the relationship apparent.

Separate Outputs From Their Status

Use accurate status labels. A class paper is not a peer-reviewed publication. A manuscript being drafted is not accepted. A submitted manuscript has not yet received the same validation as an accepted paper. If a program requests publication information, distinguish these states in the format appropriate to your discipline.

Credit collaborators and your own role accurately. A team project can be valuable evidence without implying sole authorship. If a result belongs to the broader team, explain which part you handled. Where a professional project is confidential, describe the permitted scope and methods without disclosing protected material; an employer's permission to share a work sample is a separate question from its relevance.

Awards also benefit from context. Give the awarding organization, date, and a brief description if the title is unfamiliar. Quantify competitiveness only when you can verify it. “Selected for a departmental award” is preferable to an invented claim that you were the best student in the university.

Use Space To Show Relevance

Suppose a fictional applicant has three years of retail management experience and is applying to a public-policy master's. Removing the work history entirely could erase useful evidence about responsibility. Reproducing every operational duty could obscure the relevant preparation.

The applicant might select examples of scheduling decisions, analysis of inventory patterns, staff training, or communication with different groups, where those experiences genuinely connect to the program. The document should still state the actual role. It should not rename ordinary workplace responsibilities as formal academic research.

Penn's career guidance recommends descriptions that show specific actions and accomplishments rather than unsupported lists of soft skills. [6] Apply that principle carefully to admissions: describe an instance of analysis or collaboration, then leave the evaluation to the reader. The guidance is about communication, not evidence that a particular bullet style changes admission odds.

Prioritize material by relevance within a coherent structure, and use reverse chronology where it helps readers follow the record. Avoid a design that makes dates or role boundaries difficult to find. A consistent font, sensible spacing, and clearly separated entries usually matter more than decorative graphics.

Review The Document Against The Rest Of The Application

Read your résumé or CV beside the transcript, statement, and project descriptions. Names, dates, titles, authorship, and publication status should agree. The documents can emphasize different things, but they should describe the same history.

Ask a reviewer to identify your two strongest pieces of preparation after a brief read. If they cannot, reconsider the order and specificity. Ask a second question: “Which claim would you want me to explain in an interview?” That can reveal vague phrases or claims that exceed the actual contribution.

Finally, return to the live program instructions. Check the required length and file type, inspect the exported file, and make sure the correct version is attached. Keep the complete master record for future applications, but submit the version that satisfies this program and makes your relevant preparation easy to understand.