Read a sample: 1. From Academic CV to Targeted Resume
An academic CV can tell the story of a career in considerable detail. It may document publications, conference presentations, courses, grants, committees, affiliations, awards, and works in progress. Its length is often a consequence of its purpose: to show the development and scope of scholarly work.
A resume for a nonacademic role has a different job. It helps a reader decide whether your experience is relevant to a particular position. Instead of preserving the full record, it selects and explains evidence that makes your fit easier to understand.
That change can feel uncomfortable. If you have spent years earning credentials, conducting research, and contributing to an academic community, leaving much of that work off a resume may seem like diminishing it. It is not. A resume is not a verdict on the value of your career. It is a document with a specific audience and a specific decision in view.
Your goal is not to make yourself sound as though you have never worked in academia. It is to help an employer understand what you did there, how you did it, and why that experience is relevant to the work they need done.
An academic CV and a targeted resume may draw from the same history, but they organize that history around different questions.
An academic CV often answers questions such as:
- What has this scholar published or presented?
- What subjects and courses has this person taught?
- What grants, appointments, and distinctions form part of the scholarly record?
- How has this person contributed to a discipline or institution?
A targeted resume is more likely to answer:
- What relevant work has this applicant done?
- Which responsibilities and tools can the applicant demonstrate?
- What kinds of problems, audiences, or projects has the applicant handled?
- Is there enough evidence to justify a closer conversation?
Neither set of questions is inherently more serious than the other. They serve different decisions. A hiring committee evaluating a faculty candidate may need a detailed publication record. A manager hiring a research analyst may be more concerned with how the applicant frames questions, works with data, communicates findings, and collaborates with others.
The distinction is not always perfect. Some employers request a CV, a publication list, a portfolio, or other materials alongside a resume. Some research-intensive positions outside universities may place substantial weight on scholarly output. Read the actual application instructions rather than assuming that every nonacademic employer wants the same document.
For many roles, however, a resume is selective by design. It is usually shorter than an established academic CV, uses space to emphasize relevant experience, and explains accomplishments in terms a reader outside the field can understand. Concision is useful because it helps the reader find the evidence; it is not an excuse to remove every detail that makes the evidence credible.
Academic writing often relies on shared knowledge. A reader in your discipline may understand the significance of a particular archive, method, fellowship, journal, or conference without explanation. A nonacademic reader may not.
Imagine that your CV lists a dissertation title, an award, and several articles. A reader in your field might infer the complexity of your work from those entries. A recruiter or hiring manager in another setting may see strong credentials but remain unsure what you actually did.
That uncertainty is your responsibility to reduce. You do not need to teach the reader your entire discipline. You do need to supply enough context for them to recognize the work.
For example, a dissertation entry might establish the subject of a project. A resume description can add the relevant activities: developing a research question, collecting and evaluating evidence, managing a lengthy project, using particular methods, or explaining findings to different audiences. Which details belong depends on the role.
Avoid assuming that a familiar academic label explains its own value. “Graduate researcher” may be an accurate title, but the title alone does not tell the reader whether you conducted interviews, maintained equipment, analyzed documents, wrote code, coordinated a team, or did something else entirely. A clear description gives the title practical meaning.
The reverse is also true: a job title from industry does not automatically describe your experience. Calling yourself a “product manager” because you managed a dissertation project could mislead a reader about your responsibilities. You can describe planning, coordination, or stakeholder communication without claiming a position you did not hold.
A CV encourages accumulation. A resume asks for selection. That does not mean that the experiences you leave out were unimportant. It means they are less useful to the reader making this particular hiring decision.
Suppose a hypothetical applicant has taught seminars, conducted interview-based research, served on a departmental committee, and presented at conferences. For a role involving qualitative research, the interviews and analysis may deserve the most space. For a role supporting learning programs, course design and feedback may be more prominent. For a project coordination role, the applicant might give more attention to scheduling, communication, and contributions to shared work.
The underlying history has not changed. The order, detail, and emphasis have.
A common first attempt is to shorten a CV by deleting older entries until the document looks more like a resume. This can produce a shorter document without producing a more useful one. The remaining entries may still emphasize academic categories rather than the work an employer needs to understand.
A…