The hardest part of a professor resume is not writing it. It is deciding what to throw away. Most faculty keep a curriculum vitae (CV) that has grown by accretion for a decade: every publication, every conference talk, every committee, every guest lecture. Ours below started at nine pages. The resume version of the same career is two.

That cut is exactly the decision most searchers for this page are facing, so this article does it in the open. You will see the finished two-page professor resume, then a section-by-section account of what the nine-page CV contained, what survived, what was deleted, and why each call was made. Along the way we cover the adjacent questions: how to tell which document a posting actually wants, how to write an adjunct-to-assistant-professor progression as one story, which of twenty publications make the cut, and what changes again if you are leaving academia for industry.

The candidate is a tenure-track assistant professor of biology at a regional public university, six years past her PhD, with a route that ran adjunct, then full-time lecturer, then assistant professor. On her CV that career takes nine pages. Here it takes two, and nothing on these two pages is filler: every line either shows teaching scope, research funding, or the kind of service a hiring committee screens for.

Read it once as a committee member would, in under a minute, then come back for the cut-by-cut breakdown below.

Send the wrong document and you look like you did not read the posting. The rule is simpler than most guides make it: tenure-track and research faculty searches expect a full CV. Almost everything else expects a resume, or accepts either and rewards the shorter one.

The posting itself usually tells you, if you read the application instructions rather than just the job title. Look for these signals.

One more practical marker: if the application goes through an institution's careers portal (Workday, PeopleAdmin, Interfolio's HR side), assume an ATS parses it first. That is a resume environment even when the posting says CV, so keep the formatting plain and put keywords in the body text. If it goes by email to a search committee chair, it is a human-first read and the full CV is safe. Our guide on ATS-friendly CV formatting covers the parsing side in detail.

When a posting genuinely accepts either, send the resume and add a line at the bottom: "Full CV with complete publication list available on request." You lose nothing and you respect the reader's time.

This is the backbone of the page. The table below walks through each section of the original nine-page CV, shows what happened to it on the two-page resume, and gives the reason. The pattern to internalize: the CV proves completeness, the resume proves relevance. A CV answers "what is your entire record." A resume answers "can you do this specific job." Every cut below follows from that difference.

Total effect: nine pages become two, and the two read faster and hit harder. Nothing was falsified and nothing important was hidden. The full record still exists as the CV, one click or one request away. If you are unsure the two-page target is right for your experience level, our data-backed answer to one page or two applies to academics the same way: past roughly a decade of experience, two pages is the norm, and even a twenty-year academic career should not push a resume to three.

The most common structural mistake on academic resumes is listing every appointment as a separate entry. Our example candidate held seven distinct appointments before her current role: adjunct at two institutions, sometimes in the same semester, then a full-time lecturer post, then the tenure-track job. Listed separately, that is seven headers, seven date ranges, and a first impression of instability that is entirely unfair to how academic careers actually work.

The fix is to write it as a progression. Three entries, newest first, each with a clear title change that shows movement:

Grouping adjunct work under one header is legitimate and standard. You are not hiding anything: the institutions are named and the dates are accurate. You are refusing to let formatting turn a normal early-academic path into something that looks fragmented. The same logic drives reverse chronological format generally: recency and trajectory first, detail in proportion to relevance.

One more rule for the progression: bullet count should taper. Five or six bullets on the current role, three on the lecturer role, two on the adjunct years. If your oldest job has as many bullets as your newest, you have not decided what matters. Our guide on how many bullets per job gives the full breakdown by recency.

Our candidate has twenty peer-reviewed articles and two book chapters. Five entries made the resume, under the heading "Selected Publications" with a closing line: "Full publication list available on request." That label matters. "Selected" tells the committee you chose; without it, five publications reads as your entire output.

The selection logic, in priority order:

What never makes the resume: manuscripts "in preparation." Under review is acceptable with the journal named if your field's norms allow it; in preparation is a claim no one can verify and every committee discounts to zero. It is the academic equivalent of a skill you cannot demonstrate, and it invites the one interview question you do not want.

Here is where academic resumes lag every other profession. A sales resume states quota and attainment. A project manager resume states budget and headcount. Academic resumes, oddly, tend to state duties: "taught undergraduate courses, supervised students, conducted research." Those lines describe every professor alive.

The fix is scope lines: numbers that establish the size of what you carried. On our example resume, four kinds of scope do the work:

Notice what these lines have in common: a verb, a number, and a consequence. That structure is exactly what committees at teaching-focused institutions screen for, and it is what an HR screener at a portal-driven search can actually evaluate without a PhD in your field.

Grant funding is the single strongest scope line an academic resume can carry, and most candidates waste it. "Secured external research funding" says nothing. The line on our example resume says: "Co-Principal Investigator, NSF award, $412,000 over three years, funding two graduate assistantships and summer undergraduate research."

Every element of that line is doing a job. The role (Co-PI, not "contributor") tells the committee your standing on the award. The agency name carries the prestige signal, because a federal award means you survived federal peer review. The dollar amount converts research into a number a dean can compare across candidates. The "funding two assistantships" clause shows the money built capacity rather than just travel.

Two edge cases. If your only funding is internal (a university teaching innovation grant, say), include it with the amount anyway; small and real beats vague. And if you were senior personnel on a large award but not PI or Co-PI, say exactly that: inflating a grant role is the fastest way to lose a committee that can, and will, look the award up in the agency's public database.

The nine-page CV listed fourteen committees. The resume keeps four lines, and the selection principle is screening value: which service entries answer a question the hiring committee is actually asking.

What gets cut without hesitation: committee memberships with no output, one-off event volunteering, and anything from graduate school. Service earns tenure points internally; on an external application, it earns almost nothing unless it demonstrates leadership or matches the posting. Four lines is not a suggestion, it is a budget.

If the target is industry rather than another faculty post, the two-page resume above is still too academic. The cut order changes, and the first things to go are the sections academics consider most valuable.

The mental shift underneath all five: academia rewards the record, industry rewards the transfer. Our full guide to writing a career change resume covers the framing in depth, and it applies to leaving academia more than to almost any other switch, because no field's default document is further from what industry expects.

Faculty searches at smaller institutions, community colleges, and any posting routed through an HR portal get a keyword screen before an academic reads them. The screener, human or ATS, is matching the posting's required-qualifications language against your document. The terms below recur across professor and lecturer postings; the second column is where each belongs, because placement matters as much as presence. A keyword in a skills list is an assertion; the same keyword inside a bullet with a number is evidence.

Do not paste these into a skills block and call it done. Screeners increasingly read context, and a skills section stuffed with pedagogy terms and no supporting bullets reads as exactly what it is. The mechanics of matching a posting's language without stuffing are covered in how to beat the ATS without keyword stuffing.

Everything above is judgment you now have to apply to your own nine pages, against a specific posting, and the honest way to check your work is to compare the two directly. Pull the posting's required and preferred qualifications, and confirm every one of them appears on your two pages in the posting's own vocabulary. If the job says "learning outcomes assessment" and your resume says "evaluated student progress," a keyword screen scores that as a miss even though it is the same work.

This is the part Roleframe does mechanically so you do not have to eyeball it. Paste the posting, and the fit report scores your resume against it: an ATS score, the exact keywords the posting asks for that your document is missing, and a prioritized plan of what to change. You make the edits yourself, with Remi, the career copilot, proposing rewrites bullet by bullet that you approve or discard. For an academic juggling faculty, admin, and industry targets at once, keeping one base resume per target with tailored versions per application is the workflow that stops you from sending the teaching-college version to an R1 search. Our guide to base resumes and tailored versions explains the system.

One last mechanical note: export and submit as PDF. Academic portals parse PDFs reliably, your formatting survives, and the committee sees exactly the page you built. Only produce another format if a specific portal explicitly demands it.