The Academic Job Masterclass

Module 0Start Here

Most people lose the academic job market before they ever submit an application. Not because they lack credentials, but because they build the wrong thing first, in the wrong order, for the wrong reader.

Here is the single most important thing in this entire document: an academic search committee is not reading your materials to find out how impressive you are. They are reading to find out whether you solve a specific problem they have. That problem is usually one of three things — a course that nobody can teach, a research area the department wants to grow, or a service gap nobody wants to fill. Every document you write is an argument that you are the answer to their problem, not a catalog of your accomplishments.

Internalize that and the rest of this masterclass becomes mechanical.

Find your path

Four kinds of people apply for academic jobs. They have different assets, different liabilities, and therefore need to build their materials in a different order. Find yourself below.

The module map

The hiring calendar

Academic hiring runs on a calendar that has almost nothing to do with when you feel ready. Missing the window costs you a full year. The rhythm below is typical for North American institutions; adjust by roughly one term for UK/EU/AUS cycles, which are more rolling.

What "fit" actually means

You will hear the word fit constantly, usually as the explanation for a rejection. It sounds like a polite non-answer. It isn't. Fit has four measurable components, and you can influence three of them:

• Curricular fit. Can you cover the courses on their teaching schedule, including the unglamorous required ones? This is the most decisive and the most ignorable-in-your-favor. A candidate who can teach the required stats course beats a more distinguished candidate who can't.
• Intellectual fit. Does your work complement rather than duplicate existing faculty? Committees avoid hiring a second version of someone they have.
• Institutional fit. Do you understand what kind of place this is? A research-intensive R1 and a regional teaching-focused comprehensive want opposite things in the same document. Applying to both with the same letter is the single most common self-inflicted wound.
• Collegial fit. Will people want to sit in a curriculum committee meeting with you for twenty years? Unfair, unfalsifiable, and completely real.

Everything in Module 1 onward is the practice of demonstrating those four things on paper and in person.

Know the institution type before you write a word

Module 1Academic Branding

Branding in academia is not self-promotion. It is the discipline of being legible — of making it effortless for a stranger to say, in one sentence, what you do and why they'd want you in their department.

Here is the test. A search committee member is walking to the parking lot with a colleague and says, "We should look at that candidate — the one who—". Whatever comes after that dash is your brand. If nobody can finish that sentence, you don't have one. And if you don't supply the ending, they will invent one, and it will be something forgettable like "the one from Michigan."

Most candidates fail this test because they describe themselves by category ("I'm an organizational behavior scholar," "I'm a data scientist") rather than by the specific problem they own. Category descriptions put you in a bucket with two hundred other applicants. Problem ownership puts you in a bucket of one.

Identifying your exact teachable zone and expertise

Your teachable zone is the intersection of three things: what you have genuine authority in, what students need to learn, and what a department actually has to staff. It is not the same as your research area, and for anyone on Path A or Path C it matters far more than your research area.

Step 1 — Inventory your authority (90 minutes)

Open a blank document. Do not edit while you do this. List:

• Every project, engagement, study, or product you've owned end to end. For each, write the decision you were trusted to make.
• Every tool, method, framework, or technique you can operate at an expert level — not "familiar with," but "have used to produce a real outcome."
• Every topic on which someone has asked you for advice more than three times. This list is more valuable than the other two, because it's external evidence of authority.
• Every mistake you've made professionally that taught you something a textbook wouldn't. These become your best teaching material.
• If you have research: the three questions your work has actually answered, in plain language, no jargon.

Step 2 — Map real curricular demand (2 hours, and it must be real research)

This is the step nearly everyone skips, and it is the step that produces the advantage.

1. Pull 15–25 job postings in your target space from HigherEdJobs, the Chronicle, Interfolio, discipline-specific job wikis, and — most importantly — the HR pages of the 20 specific institutions you'd actually take a job at.
2. Extract every named course from the "teaching needs" sections. Put them in a spreadsheet. Count frequency.
3. Then go to the course catalogs of those same 20 institutions. Find the courses in your area. Note which ones are required vs. elective, and which ones are listed but not offered this year — a listed-but-unoffered course is a staffing gap with a course number already attached to it.
4. Look at the faculty roster. Who currently teaches what? Who is emeritus or about to be? Which areas have exactly one person covering them? A department with one methods person is a department that is one retirement away from a crisis.

Step 3 — Write the zone statement

Compress the overlap into a single sentence in this shape:

Step 4 — Build your course coverage list

Every candidate should have a standing list of courses they can teach, organized in three tiers. This list goes into cover letters, informational calls, and interviews, and it is the thing chairs remember.

Step 5 — Name your through-line

A through-line is the idea that connects everything you do — teaching, research, and practice. It's what makes a portfolio feel coherent rather than assembled. It usually takes the form of a claim you'd defend:

• "Quantitative training fails students when it's divorced from the decision it informs."
• "Design education overweights the artifact and underweights the constraint."
• "Public health interventions fail at the implementation layer, not the evidence layer."

You'll use the through-line in your teaching philosophy opening, your research statement framing, your cover letter close, and the answer to "tell us about yourself." One idea, four documents. That repetition is what makes someone memorable.

Thought leadership

Thought leadership in academia is not posting takes. It is producing artifacts that make you findable and citable by the specific people who make hiring decisions. The goal is that when a chair Googles you before the screen call, they find evidence that you're a serious person with a point of view. That's it. That's the whole objective.

The visibility ladder

Work up this ladder. Each rung is more effort and more credibility than the last. You do not need the top rungs to get hired; you need the bottom three to not be invisible.

The one-topic rule

Pick one topic and stay on it for at least twelve months. The instinct is to demonstrate range. Range makes you forgettable. If everything you publish for a year sits inside your teachable zone, then by month twelve, people in your field associate that topic with your name — and association is the entire mechanism by which opportunities arrive unsolicited.

Turning content into course material

The highest-leverage move: write your public pieces as teaching modules in disguise. Each piece should be a concept, an example, a common misunderstanding, and a takeaway. Do this twelve times and you have simultaneously built visibility, a course, and the evidence base for your teaching philosophy. Nothing is wasted.

What to avoid

• Credential theater. Listing affiliations and titles without producing anything. Committees discount it instantly.
• Fighting on the internet. Search committees Google you. Public conflict, however justified, reads as collegiality risk.
• Range-signaling. Publishing across five unrelated topics to seem broad. Reads as unfocused.
• Waiting for the perfect piece. Twelve adequate pieces beat one excellent piece you never finished.

Module 1 checklist

• Completed the 90-minute authority inventory
• Pulled and coded 15–25 job postings into a course-frequency spreadsheet
• Reviewed course catalogs and faculty rosters for 20 target institutions
• Written a one-sentence teachable zone statement
• Built the three-tier course coverage list (Ready now / With prep / Would propose)
• Named a through-line claim you'd defend
• Personal website live with bio, CV, courses, and contact
• Google Scholar / ORCID / LinkedIn current and consistent with your CV
• Committed to a publishing cadence and picked the one topic

Module 2The Academic CV

A résumé argues. A CV documents. Confusing the two is the most common and most immediately visible error a candidate coming from industry makes — and it is also, quietly, a mistake plenty of PhDs make in the other direction.

What makes a good CV

A good academic CV does four things. In order of how often candidates get them wrong:

1. It is scannable in 45 seconds

Committee members review 80–250 applications. Your CV gets a first pass measured in seconds, and that pass is looking for four things: degree and field, publication/teaching record, institutional history, and whether your record matches the level of the position. If those four aren't findable without scrolling and squinting, you lose on formatting alone.

Practically: consistent heading hierarchy, generous white space, dates in a fixed position on every line, no dense paragraphs, no two-column layouts that break when printed, no graphics.

2. It is ordered by what this specific job weighs most

The sections after your education can be reordered, and should be. This is the only meaningful tailoring an academic CV needs.

• Research-intensive posting: Education → Appointments → Publications → Grants → Presentations → Teaching → Service
• Teaching-focused posting: Education → Teaching Experience → Courses Taught → Teaching Awards/Evaluations → Curriculum Development → Publications → Service
• Practitioner/professional school posting: Education → Professional Experience → Teaching Experience → Courses Taught → Professional Credentials → Publications & Practitioner Writing → Service

3. It quantifies where quantification is meaningful

Academic CVs are factual, not boastful — but facts include numbers. Numbers convert vague experience into verifiable scale.

4. It is scrupulously honest and internally consistent

Every date, title, and claim will be checked against your LinkedIn, your website, your letters, and your references. Inconsistency — even innocent inconsistency — is the fastest way to be quietly removed from a list.

Sections you should include

Below is the full menu. Not every section applies to every person — include a section only if you have real content for it. An empty or near-empty section draws attention to the gap.

Always include

Include when you have content

Special guidance by path

Path A — translating industry into academic form

Your problem is not lack of substance; it's that your substance is in the wrong vocabulary. Translate:

Two more rules for Path A: drop the résumé bullets (achievement-verb bullets look out of place; use scope lines instead), and do not shorten to two pages — a two-page academic CV from a twenty-year professional reads as a thin record, not a disciplined one.

Path B — the early-career CV

Yours will be 2–5 pages and that is correct. Do not pad. Instead: include "in preparation" work with honest labels, list conference presentations fully, list every course including TA work with the role labeled precisely, and include departmental service (grad student rep, seminar organizer) — it shows citizenship.

Path C — foregrounding teaching scale

Your CV's job is to convert "adjunct" from a status into a body of evidence. Aggregate: total students taught, number of distinct course preparations, number of institutions, evaluation means against departmental means, courses you redesigned. "Taught 14 distinct courses across 3 institutions to 2,100 students since 2018" is a serious record and most adjunct CVs never state it.

Path D — pruning, not padding

Senior CVs get long and lose their shape. Reverse-chronological within sections, cut nothing factual, but move dated material (graduate teaching, decade-old service) below current material and consider a brief "Selected" designation for talks if the list exceeds a page. Add sections that signal readiness for the level you're seeking — external funding, doctoral supervision, program leadership, editorial roles.

Annotated CV excerpt

Formatting rules

• File format: PDF, always. Name it Lastname_Firstname_CV.pdf. Never send a .docx unless explicitly requested.
• Font: One serif (Garamond, Palatino, Times) or one clean sans (Calibri, Helvetica). 11–12pt body.
• Margins: 1 inch. Do not shrink margins to fit — length is not a sin here.
• Page numbers and running header with your name on every page after the first. Pages get separated.
• Dates right-aligned or in a consistent left column — pick one and never deviate.
• No tables with visible borders, no columns, no color, no logos, no headshot, no skill bars.
• Hyperlinks on your website, DOIs, and ORCID — live and tested.
• Update it every single time something happens. A CV maintained continuously takes ten minutes a month; a CV reconstructed under deadline takes two days and has errors.

Module 2 checklist

• CV converted to academic format (no résumé bullets, no design elements)
• Sections ordered to match the target institution type
• Teaching Experience distinguishes instructor of record from TA/assistant roles
• Enrollment numbers and evaluation means (with departmental comparison) included
• "Courses Prepared to Teach" section added with 6–10 courses in three tiers
• Every publication has an honest status label
• Dates, titles, and institutions match LinkedIn, website, and letters exactly
• Running header with name and page numbers on every page
• Exported as PDF named Lastname_Firstname_CV.pdf
• Read aloud once, and proofread by one other person

Module 3The Cover Letter

The CV documents. The cover letter argues. It is the only document in your packet where you get to tell the committee what the evidence means — and it is, empirically, the document that decides whether anyone reads the rest.

Committee members typically read the cover letter first, and it functions as a filter. A generic letter gets your file moved to the "no" pile before your CV is opened. A specific letter earns your CV a careful read. That asymmetry is why 45 minutes of tailoring per application beats 45 more applications sent generically.

The five-paragraph architecture

Length: 1.5 to 2 pages for teaching-focused roles, 2 pages for research-intensive. One page reads as insufficient effort. Three pages reads as an inability to prioritize.

Paragraph 1 — the hook

Do not open with "I am writing to apply for..." — it wastes the highest-attention sentence in the document. But do name the position and requisition number somewhere in the first two sentences, because HR systems and committee chairs both need it.

Paragraph 4 — the fit paragraph

This paragraph is where letters are won and lost. It must contain named specifics. Generic praise ("your department's excellent reputation") is worse than nothing because it signals you didn't look.

Sources for genuine specifics, in descending order of value:

1. The course catalog. Name two or three specific courses by number and title that you're prepared to teach. Nothing else in the letter is this persuasive.
2. The posting itself. If it names courses, centers, or program needs, address each one explicitly.
3. Faculty pages. Name one or two people and a real point of complementarity — not flattery. "Dr. Okafor's work on X connects to my Y in the following way." Never name someone whose work you haven't read.
4. The strategic plan / dean's letter / accreditation report. Almost always public, almost never read by applicants. It tells you exactly what the institution says it's trying to become.
5. Student profile and mission. If it's an HSI, an MSI, a heavily first-generation or transfer-heavy student body, a religious institution, or a workforce-aligned college — say so, and say what you'd do about it concretely.
6. Anything you learned in a conversation. If you did Module 8 properly, you have information the other applicants don't.

Path-specific letter moves

Annotated sample cover letter

Line-level craft

• Address a person. Find the search chair's name. "Dear Search Committee" is acceptable; "To Whom It May Concern" is not.
• Cut every instance of "I believe," "I feel," and "I am passionate about." Replace with the evidence that would justify the belief.
• Verbs over adjectives. "I redesigned the course around a live client project" beats "I am an innovative and dedicated instructor."
• Numbers in every substantive paragraph. Enrollment, sections, evaluations, team size, dollars, students placed.
• Never explain a gap defensively. If you must address something — a career change, a leave, a nonlinear path — do it in one forward-facing sentence and move on.
• Match their vocabulary. If they say "student success," use "student success." If they say "scholarly productivity," use that. This is not pandering; it's demonstrating you speak the institution's language.
• Proofread the university name in every paragraph. Sending a letter with the wrong institution's name is the most common fatal error in the entire process, and it happens constantly because people copy-paste.

Module 3 checklist

• Master letter written at ~2.5 pages
• Reverse-engineering table completed for this specific posting
• At least three facts in the letter that are true only of this institution
• Specific course numbers and titles from their catalog named
• Explicit willingness to teach required/service courses stated
• One named faculty member with a genuine, specific connection (whose work you have read)
• Numbers in every substantive paragraph
• "I believe / I feel / I'm passionate about" eliminated
• Institution name correct in every instance — checked twice
• Addressed to a named person where possible
• Under 2 pages, PDF, named Lastname_Firstname_CoverLetter.pdf

Module 4The Teaching Philosophy

Almost every teaching philosophy statement is bad, and they are bad in exactly the same way: they describe values instead of practices. "I believe in creating an inclusive, student-centered learning environment where all students can reach their potential" is a sentence that appears in thousands of statements and distinguishes none of them.

A teaching philosophy earns attention when it makes a falsifiable claim about how learning works in your subject, and then shows what you concretely do because you believe that. Claim → practice → evidence. Everything else is filler.

The five-move structure

Move 1 — Open with a claim, not a value (1 paragraph)

Your opening should state something about learning in your discipline that a reasonable colleague could disagree with. Disagreement is what makes it a position rather than a platitude.

Move 2 — Show the practice that follows from the claim (2–3 paragraphs)

This is the bulk of the statement and where most people go abstract. Be granular enough that a reader could picture your classroom. Name the assignment. Name the sequence. Name what students actually do on a Tuesday.

Good specificity looks like: "In week three, before students have seen a formula, I give them a dataset and a decision — a marketing director must choose between two package designs — and ask them to defend a recommendation in writing. They argue. They discover they need a way to distinguish signal from noise. Only then do we build the t-test, and it arrives as an answer to a question they already have."

Cover, across your paragraphs:

• How you sequence material — and why in that order
• What students actually produce — the assignments, projects, artifacts
• How you assess — and what your assessment choices reveal about what you value
• How you handle the students who struggle — specific mechanisms, not sentiment
• What you do differently for different populations — first-generation, transfer, working, returning, ESL, neurodivergent students

Move 3 — Give evidence that it works (1 paragraph)

Claims plus practices plus no evidence reads as theory. Evidence can be:

• Evaluation data, with departmental comparison
• Direct quotes from student evaluations (two short ones, maximum — more reads as insecure)
• Outcome data: pass rates, DFW rate changes, enrollment changes, downstream course performance, placement
• Adoption: other instructors using your materials, department adopting your structure
• Peer observation notes or teaching awards

Move 4 — Show that you revise (1 short paragraph)

The most underrated move in a teaching philosophy: describe something that didn't work and what you changed. It signals reflective practice, which is precisely what the genre is supposed to demonstrate and almost nobody actually does. Two or three sentences is enough.

Move 5 — Point forward (1 short paragraph)

What you want to teach next, what you want to learn about teaching, and — briefly — what you'd contribute to this specific program. This is the only lightly-tailored part.

Annotated sample teaching philosophy

Path-specific notes

• Path A: Your practitioner authority is your differentiator, but it can read as "war stories." Anchor every industry reference to a pedagogical purpose. The claim in ¶1 should come from something you learned by doing the work.
• Path B: Thin teaching experience is fine — but be honest about scope and specific about what you did. TA-ing a discussion section well, described precisely, beats an inflated claim. Draw on what you learned as a student in your field: what confused you, and what you'd do about it.
• Path C: You have the most evidence of anyone and usually undersell it. Aggregate across institutions. Note where you've taught the same course to different populations — that comparison is genuinely interesting and almost nobody has it.
• Path D: Include mentorship and doctoral supervision, and include evidence of teaching development at the program level: curriculum you built, colleagues you've mentored, assessment work.

Module 4 checklist

• Opening paragraph makes an arguable claim, not a value statement
• At least two specific classroom practices described at week-level granularity
• Assessment approach explained with the trade-off made explicit
• Concrete mechanisms for supporting struggling and underprepared students
• Evidence paragraph with numbers and comparison context
• A paragraph describing something that failed and what you changed
• Forward-looking paragraph with one specific connection to this program
• Every banned phrase removed
• Under 2 pages, PDF

Module 5The Research Statement

The research statement answers one question: if we hire you, what will exist in five years that doesn't exist now? It is a document about the future that uses the past as evidence. Most candidates write the reverse — a memoir of completed work with a vague gesture at "future directions" in the last paragraph — and it fails.

Structure

1. The through-line (1 paragraph)

Open with the question that organizes everything you've done and will do — the intellectual problem, not the topic. "I study how organizations make decisions when the data they have does not answer the question they face" is a through-line. "I study organizational decision-making" is a topic. The through-line makes disparate projects cohere; the topic makes them look scattered.

2. Completed work — organized as a line, not a list (2–4 paragraphs)

Group your work into two or three streams, and show how each answered part of the through-line question. For each stream: the question, the approach, the finding, and — critically — what it opened up. That last element is what turns a retrospective into a trajectory.

Cite your own work inline so the reader can map claims to CV lines. Name the venue when it's strong.

3. The forward agenda — the actual point of the document (3–5 paragraphs)

This is where you win or lose. Describe two or three specific projects with enough operational detail that a committee believes they will happen. For each:

• The question and why it matters now
• The approach — method, data, site, population
• Current status — data collected, pilot run, IRB submitted, draft in progress. Concreteness here is everything.
• Expected outputs — target venues, named honestly
• Timeline — a realistic year-by-year arc
• Funding — specific programs you'd target, and whether you've submitted before

4. Infrastructure and fit (1 paragraph)

What you need to do this work — lab space, computing, archival access, course release, travel — stated modestly and realistically. Then what their institution offers that enables it: a center, a data resource, a colleague, a student population, a partnership. This paragraph also quietly signals that you understand what you cost.

5. Students and research (1 short paragraph)

Frequently omitted and always noticed. How will students participate? Undergraduate research assistants at a liberal arts college; doctoral supervision at an R1; capstone teams at a professional school. Name specific tasks students could do and what they'd get out of it.

Annotated sample research statement excerpt

Calibrating by institution type

Module 5 checklist

• Through-line question stated in the first paragraph, jargon-free
• Passed the jargon test with a non-specialist reader
• Completed work grouped into 2–3 streams, each ending with what it opened up
• 2–3 forward projects with question, method, status, venue, timeline
• Concrete status markers (data, IRB, agreements, drafts) for each project
• Specific funding programs named, with honest history if applicable
• Infrastructure needs stated realistically and scaled to the institution
• A named connection to this department's resources or people
• Student involvement paragraph with specific tasks by level
• Length calibrated to institution type; PDF

Module 6Making a Sample Syllabus

The sample syllabus is the most underused document in the academic job search. Most postings don't require one. Most candidates therefore don't send one. Which is exactly why sending one works.

A syllabus is the only document in your packet that is operational. Everything else describes what you would do. A syllabus is what you would do — a fourteen-week commitment, written down, gradeable, and immediately usable. When a chair is choosing between two candidates and one of them has already handed over a working version of the course they need staffed, that is not a small advantage.

Choosing which course to build

The strongest packet contains two: one required workhorse course and one proposed elective. That combination says "I will carry the load, and I will also build something."

Anatomy of a strong sample syllabus

1. Header block

Course number and title matching their conventions, credit hours, term, meeting pattern, modality, prerequisites, instructor name, contact, office hours. Getting the course number format right signals you looked at their catalog.

2. Course description (1 paragraph)

If the course exists in their catalog, start from their official description and extend it. Do not contradict it.

3. Learning outcomes (4–6, measurable)

This is where syllabi are judged by anyone with curriculum or accreditation experience — and every department has one of those people on the committee. Outcomes must use observable verbs and must map to assessments.

4. The alignment table

A simple three-column table — Outcome / Assessment / Weight — instantly demonstrates curricular competence. Very few candidates include one. Anyone who has done accreditation work will notice.

5. Assessment scheme

Show your pedagogical values through structure. Frequent low-stakes work signals attention to skill-building. A single midterm and final signals a content-delivery model. Neither is wrong; be deliberate and be able to defend it. Include the grading scale and late policy.

6. The week-by-week schedule

This is the heart of the document and where committees look hardest for competence. A strong schedule shows:

• Deliberate sequencing — a visible logic to the order, not just a march through textbook chapters
• Realistic pacing — including a lighter week around midterms and a buffer week before finals
• Reasonable reading loads — 40 pages of dense theory per week for a 100-level course is a red flag to anyone experienced
• Named readings with real citations — placeholders like "readings TBD" undercut the whole document
• Assessment due dates distributed rather than stacked
• Currency — at least a few readings from the last three years

7. Policies

Attendance, late work, academic integrity, accessibility/accommodations, and — as of the current landscape — a clear and thoughtful generative AI policy. That last one is now read closely by committees as a signal of whether you're teaching in the present. Take a defensible position, whatever it is, and explain the reasoning to students.

8. Resources and support

Tutoring, writing center, disability services, food and housing insecurity resources, mental health services. At teaching-focused institutions this section is read as evidence of student-centeredness — and, more importantly, it's the right thing to include.

Formatting and length

6–10 pages. PDF. Named Lastname_SampleSyllabus_COURSECODE.pdf. Use the target institution's course numbering, credit-hour language, and term structure (semester vs. quarter). Include a short header note if it's a proposed course: "Proposed course, prepared for [Institution]. Aligned to [Program] learning goals."

Module 6 checklist

• Chose a required/high-need course, not only a passion elective
• Course number, credit hours, and term structure match their conventions
• 4–6 measurable learning outcomes using observable verbs
• Outcome-to-assessment alignment table included
• Full 14–15 week schedule with real, cited readings — no "TBD"
• Pacing is realistic; assessments distributed, not stacked
• At least some readings from the last three years
• Explicit and reasoned generative AI policy
• Accessibility, integrity, and student support sections present
• 6–10 pages, PDF, clearly labeled as a sample or proposed course

Module 6bThe Supporting Documents

The four documents nobody teaches you to write, all of which are read, and two of which can sink an otherwise strong file.

Diversity, equity, and inclusion statement

Required at many institutions, prohibited at some, and increasingly variable by state and system. Check the posting and check the institution's current policy. Where it's requested, it's evaluated seriously — and it's the document where generic writing is most conspicuous.

Length: 1–2 pages. Structure that works:

1. What you've actually done — specific actions with specific populations. Course redesigns, mentoring programs, recruitment work, accessibility improvements, curriculum revisions, pipeline programs. Include what you learned from the ones that didn't work.
2. What you do in the classroom — concrete pedagogical practices: how you structure group work to avoid the usual dynamics, how you handle participation for students who won't speak first, what your assessment design does for students with irregular schedules or caregiving responsibilities, how you build a course that works for a student on their third attempt.
3. What you'd do here — tied to this institution's actual student body. If it's an HSI, a rural-serving regional, a heavily transfer or first-generation campus, a community college — the specifics of that population should shape the paragraph.

References and letters

• How many: Three is standard, four to five for senior roles. Follow the posting exactly.
• Who: A mix that covers your claims — someone who can speak to research, someone to teaching, and someone who has supervised you. For Path A: a department chair or faculty member who has seen you teach is worth more than a senior executive who hasn't.
• Ask properly: Six to eight weeks out. Ask in a way that lets them decline: "Would you be able to write me a strong letter for teaching-focused positions?" The word "strong" gives them an honorable exit, and a lukewarm letter does more damage than a missing one.
• Give them a packet: Your CV, the job posting, your cover letter for that job, a bulleted list of the specific things you'd like them to speak to, and the deadline in bold. This is not presumptuous; letter-writers are grateful for it and the letters get better.
• Track and remind: A spreadsheet with institution, deadline, submission method, and status. One gentle reminder at two weeks out and one at three days out.
• Thank them, and tell them the outcome either way. This is how you get to ask again.

Teaching portfolio

Requested at teaching-focused institutions and at the campus-visit stage nearly everywhere. Typically 15–30 pages, assembled as a single PDF:

• Teaching philosophy (2 pages)
• List of courses taught with enrollments and roles
• One or two sample syllabi
• Sample assignments and the rubrics that go with them
• Evaluation summaries — quantitative, with departmental comparison, across all courses (not just your best)
• Selected student comments, presented honestly
• Peer observation letters
• Evidence of teaching development: workshops attended, certificates, SoTL reading
• A brief statement of teaching goals

Web presence

Assume every committee member Googles you before the screen call. What they should find:

• A personal site that ranks first for your name: bio, CV PDF, courses, teaching statement, contact, headshot
• Google Scholar and ORCID current (if you publish); LinkedIn current and consistent with your CV (if you're Path A)
• Nothing that contradicts your materials — mismatched dates and titles are the most common problem
• No public conflict, no unprofessional content, no abandoned profiles with stale information

Module 6b checklist

• DEI statement (if requested) grounded in specific past actions and classroom practices
• Three to five referees confirmed, asked with the word "strong," and sent a full packet
• Reference tracking spreadsheet built with deadlines and submission methods
• Teaching portfolio assembled as a single PDF with full evaluation data in context
• Personal website live and first result for your name
• All online profiles consistent with the CV — dates and titles checked

Module 7The Teaching Demo

For teaching-focused positions, the demo decides the hire more often than any other component. Committees will forgive a mediocre research talk from a candidate who taught brilliantly. They will not hire someone who taught badly, no matter how good the paper.

What it is and when it's used

A teaching demonstration is a live class session — 20 to 50 minutes — delivered to some combination of real students, faculty, and committee members. It appears in several forms, and the form changes how you should prepare:

When it's used: nearly always at teaching-focused institutions, liberal arts colleges, and community colleges; usually at professional schools; sometimes at R2s; occasionally at R1s where it may be replaced or supplemented by a "chalk talk" on research. Path A and Path C candidates should assume a demo is coming and prepare one before it's requested.

How to make a good one

Step 1 — Get the brief right (do this the moment you're invited)

Email the coordinator with these questions. Asking them is itself a positive signal — it shows you think about context before content.

Step 2 — Choose the topic (if it's your choice)

Pick a topic that meets four criteria:

• You could teach it with the lights off. Never use a demo to teach something you're still learning.
• It contains a genuine difficulty — a common misconception, a counterintuitive result, a place where students reliably go wrong. Teaching something easy demonstrates nothing.
• It has a visible payoff within the session. Students should end knowing something they didn't know at minute one.
• It's core, not exotic. Teach a concept from the required curriculum, not your niche research. The committee is assessing whether you can teach their courses.

Step 3 — Design for one idea

The single most common failure in teaching demos is cramming a full lecture into 30 minutes. Committees read that as an inability to prioritize, which is the core skill of course design.

One idea. One misconception addressed. One thing students do. One visible payoff.

Step 4 — Make students do something

A demo with no student activity is a talk. Even with a room of faculty pretending to be students, build in participation — it's the thing they're watching for, and faculty observers will play along.

Activities that work in a compressed session:

• Think-pair-share — 60 seconds alone, 90 seconds in pairs, then report out. Nearly foolproof.
• Predict-then-reveal — pose a problem, have them commit to an answer by show of hands, then reveal. Commitment before information is what makes learning stick.
• Sort or rank — give six items, have pairs rank them and defend the ordering.
• Find the error — hand out a flawed analysis, argument, or design and have them locate the flaw.
• One-minute paper — at the end: "what's still muddy?" Collecting these in front of the committee visibly demonstrates formative assessment.

Step 5 — Prepare your handling of hard moments

Step 6 — Rehearse properly

• Full run-throughs out loud: at least five. Silent review does not count. The demo is a performance and it needs rehearsal, not review.
• Record yourself once and watch it. Unpleasant, unavoidable, and the fastest way to find your verbal tics and pacing problems.
• Do one run in front of two real humans who will ask you unexpected questions.
• Time every segment and know your cut points cold.
• Rehearse the first ninety seconds until it's automatic. Nerves peak at the start; automaticity carries you through.

Step 7 — Logistics that get overlooked

• Arrive 20 minutes early and test the room, the clicker, the display resolution, and your ability to be heard from the back.
• Bring a printed handout — it works when nothing else does and it gives students something to write on. Bring five extra copies.
• Bring your own adapters and a backup of your slides on a USB drive and in email to yourself.
• Learn students' names if you can — even three of them, from a roster or by asking as they arrive. It is disproportionately memorable.
• Leave a one-page handout with your name and the session's key idea. It sits on the table during deliberation.
• Dress one notch above the department's norm.

What separates a strong demo from an adequate one

• Students talk more than expected. Adequate demos have a few answers. Strong demos have students arguing with each other.
• A wrong answer became the best moment of the session.
• You covered less than you could have, deliberately, and said so.
• The close returned to the opening. The session had a shape.
• You used the room. Moved, wrote, sat on a desk, went to the back. Standing behind a podium reading slides is the default failure.
• Someone learned your name and used it.

Module 7 checklist

• Sent the logistics questions to the coordinator
• Chose a core-curriculum topic containing a genuine difficulty
• Designed around one idea with one visible payoff
• Built in a mandatory student activity of 6+ minutes
• Prepared responses for the seven hard moments
• Five full out-loud rehearsals completed, with one recorded and watched
• First ninety seconds memorized
• Cut points identified in advance
• Printed handout prepared with your name and the key idea
• Whiteboard-only fallback version ready
• Adapters, USB backup, and emailed slide copy

Module 8Networking

This is the module people skip, and it is the module with the highest return on effort in the entire masterclass. A very large share of academic positions — especially adjunct, lecturer, professor-of-practice, and visiting lines — are effectively shaped before they are posted. Not corruptly. Simply because when a department realizes it has a need, someone in the room says a name.

Your entire objective is to be a name someone says.

That is a lower bar and a more humane goal than "networking" usually implies. You are not trying to charm strangers into doing you favors. You are trying to become a known quantity in a small number of specific places, so that when a need arises you are already in the room's memory.

How to find people to reach out to

Build the target list first

Do not network broadly. Network narrowly and deeply into 15–25 specific institutions you would genuinely accept a job at. Geography, institution type, and program fit should all pass before an institution goes on the list. A focused list of twenty beats a scattered list of two hundred, because depth is what produces the "I've talked to her" sentence.

For each institution, build a small map:

Where to find people beyond the institution list

• Conference programs — especially teaching-focused divisions and pedagogy tracks, which are smaller, friendlier, and full of the people who staff teaching lines. This is dramatically underused.
• Journal editorial boards and reviewer lists in your area.
• Your own alumni network — your degree program's graduates are the warmest possible contacts and most people never mine this. Ask your department for the alumni list.
• Second-degree LinkedIn connections into target departments. A shared connection converts a cold message into a warm one.
• Authors of things you actually read — the most natural reason to reach out that exists.
• Professional associations — teaching sections, regional chapters, special interest groups. Volunteering for one of these is the highest-leverage networking act available and almost nobody does it.
• Podcast and webinar guests in your area — already comfortable talking to strangers about their work.

What to message them

Cold outreach fails for predictable reasons: it's long, it's vague, it asks for something expensive, and it's obviously a template. Fix those four things and your response rate goes from near-zero to somewhere between 30% and 60%.

Script 1 — Cold outreach to a faculty member whose work you know

Script 2 — Outreach to a department chair (highest value for Paths A and C)

Script 3 — Warm intro request to a mutual connection

The forwardable blurb is the key detail. It makes saying yes a ten-second act instead of a writing task, which is why this version gets forwarded and the version without it doesn't.

Script 4 — After meeting someone at a conference

Send this within 48 hours. The half-life of a conference conversation is about four days.

Script 5 — Reaching out to a recent hire

Recent hires reply at a much higher rate than anyone else, they give you the most useful information available, and they're often on the next search committee. Contact every recent hire at every institution on your list.

Script 6 — The re-engagement (for contacts that went quiet)

How to run coffee chats and continue the conversation

Before the call (20 minutes of prep)

• Read two things they wrote. Not skimmed — read.
• Look at their courses and their department's curriculum.
• Write down five questions. Not a script — a safety net for when the conversation stalls.
• Decide the one thing you want them to remember about you. Usually your teachable zone statement.
• Decide what you can offer. Always have something.

The 20-minute structure

Questions that actually produce useful information

• "What's the department trying to build over the next few years?"
• "Which courses are hardest to staff?" (The single most valuable question you can ask. Ask it every time.)
• "What kind of person does well in your department, and what kind struggles?"
• "If you were advising someone with my background, what would you tell them to do in the next six months?"
• "What surprised you about how searches actually run here?"
• "What do candidates from industry usually get wrong when they apply to programs like yours?" (Path A)
• "How does your department think about the difference between adjunct and full-time hires?" (Path C)
• "Who else should I be talking to?" (Always. Every call.)

What to offer (you must have something)

Reciprocity is what converts a one-time call into a relationship. You have more to offer than you think:

• Guest lecture. Free, useful, and it puts you physically in front of a department. The highest-conversion offer in this entire module.
• A capstone or project brief from your organization. Programs are chronically short of real client projects. (Path A — this is enormously valuable to them.)
• Industry contacts for their students' internships or job placement.
• A dataset for teaching use.
• A panel appearance or a career-night speaker slot.
• A relevant article, person, or resource — the smallest offer, always available.
• Reading a draft or reviewing for a journal they edit.

Follow-up: the part that decides whether any of this worked

Mindset

Most people don't fail at networking because they lack scripts. They fail because something in them resists doing it. Here is the honest version of the objections.

"This feels transactional and gross."

It feels that way when you're extracting. It stops feeling that way when you're contributing. Every framework in this module is built on offering first — a lecture, a brief, a contact, a resource. If you spend a year being useful to twenty departments, you have not manipulated anyone; you have participated in a field. The discomfort is a signal to reorient toward giving, not a signal to stop.

"I'm imposing on busy people."

You are asking for fifteen minutes with an explicit permission to decline. Faculty are asked for far more, far less politely, constantly. And the specific ask you're making — "tell me about your work and your field" — is one most academics genuinely enjoy. The people who are too busy will not reply, and that is a complete and painless outcome.

"I don't have anything to offer someone senior to me."

Usually false, and it's the belief that does the most damage. If you're Path A, you have a professional network, real data, live cases, and student placement pathways — all of which departments actively want and rarely have. If you're Path B, you have current methods knowledge, energy for collaboration, and a reason for a senior person to feel useful, which is its own reward. If you're Path C, you have front-line knowledge of how the curriculum actually lands on students. Everyone has something. Name yours before your next call.

"I've been rejected and I don't want to reach out again."

Rejection in academic hiring is overwhelmingly about fit, timing, and internal candidates — not about your worth. A department that ranks you second this year is a department that knows your name next year, and second-place candidates are called with startling frequency when a first choice declines or a new line opens. Send the gracious note. Stay in the network. That note costs three minutes and it has landed people jobs eighteen months later.

"I don't have time."

Two hours a week. One hour of outreach — that's four to six messages — and one hour of calls and follow-up. Over six months that's roughly 100 messages and 40 conversations, which is a substantial network in any field. Compare that to the time spent polishing a cover letter that goes into a portal with 240 others.

The weekly networking practice

Module 8 checklist

• Target list of 15–25 institutions built
• Contact map made for each: chair, program director, overlapping faculty, recent hires
• Tracking spreadsheet created with a follow-up column
• First 10 outreach messages sent using the scripts
• Decided in advance what you can offer, and it's specific
• Five questions prepared before every call
• "Which courses are hardest to staff?" asked on every call
• "Is there one other person I should talk to?" asked on every call
• 24-hour thank-you sent every time, without exception
• One guest lecture offered
• Two hours per week blocked on the calendar and protected

Module 9The Interview

By the time you're interviewing, everyone in the room is qualified. The committee has already decided you can do the job on paper. What they're deciding now is whether they want you in the building for the next twenty years — and whether, if they offer, you'll accept.

What to expect

Stage 1 — The screening interview (20–45 minutes, video)

Usually the full search committee, often with a rigid script — the same questions asked of every candidate in the same order, because HR requires it. That rigidity is useful information: it means your answers are being compared directly, and it means unusual answers stand out.

• Purpose: narrow eight to twelve candidates down to three or four.
• What decides it: clarity, fit, and whether you sound like a colleague. Almost nobody wins a job at this stage; plenty of people lose one.
• Prepare: a 90-second self-introduction, a 3-minute research summary, a 2-minute teaching summary, three specific reasons for this institution, and three questions to ask.
• Setup matters: camera at eye level, light in front, plain background, wired headset, and a printed one-page cheat sheet taped just beside the camera so your eyes stay in frame.

Stage 2 — The campus visit (1–2 days)

A typical two-day schedule:

Stamina and logistics

• Eat when food is offered. You will not get another chance and you will be talking for nine hours.
• Ask for the schedule in advance, plus dietary restrictions and accessibility needs. Asking is normal.
• Build in bathroom breaks — say "could I have five minutes?" between blocks. Everyone does this.
• Bring printed copies of your CV, syllabus, and one-page research summary.
• Keep a small notebook. Write down names immediately. Using someone's name on day two is disproportionately effective.
• Keep alcohol to zero or one drink at dinner, regardless of what others do.
• Ask every group the same one or two questions — the variation in answers tells you more about the department than anything on the website.

The research talk (job talk)

Typically 40–50 minutes plus 10–20 of questions. At R1s this is the single most decisive component. At teaching-focused schools it may be shorter or replaced by a teaching demo.

Structure

Slide craft

• Roughly one slide per 60–90 seconds. Forty-minute talk, 25–35 slides.
• One idea per slide. A sentence-form title that states the takeaway — not "Results," but "Procedural legitimacy predicted allocation better than evidence quality."
• No slide you'd have to apologize for ("I know this is busy…"). If you'd apologize, cut it.
• Figures readable from the back of a large room. Test this literally.
• Have three backup slides for anticipated technical questions. Pulling one up when asked is impressive.

Handling questions

• Repeat the question before answering. Buys thinking time and helps the room hear it.
• Answer the question asked, not the one you prepared for.
• "I don't know" is a strong answer when followed by how you'd find out.
• Concede real limitations. Defending an indefensible point is the fastest way to look junior. "You're right, that's a genuine limitation — here's why I made the trade-off" is what a colleague sounds like.
• If someone is hostile, stay warm and brief. The room is watching your temperament, not the substance. Often the hostile questioner is testing exactly that.
• If a question is confused, find the reasonable version of it and answer that.

The lecture demo within the visit

Everything in Module 7 applies. Three visit-specific additions:

• You will be tired. The demo is often on day two after eleven hours of talking. Rehearse to the point where you could deliver it exhausted, because you will be.
• Real enrolled students may be indifferent — they didn't choose to have a stranger teach their class. Win them in the first two minutes with something concrete, and use their names.
• Ask what they've just covered and reference it explicitly in the first minute. "You worked on X last week — today we're going to break X." Nothing signals preparation faster.

The question bank

Prepare an answer for every question below. Not memorized — but rehearsed enough that you're not composing under pressure. For each, the note in italics tells you what's actually being assessed.

Opening and identity

• "Tell us about yourself." Whether you can prioritize. 90 seconds: current role, through-line, why this position, stop.
• "Why this position, and why now?" Whether you'll accept an offer. Be specific about them.
• "Why our institution specifically?" The fit test. Name courses, programs, people, student population. Generic answers are fatal here.
• "Where do you see yourself in five years?" Whether you'd stay. Describe a trajectory that requires this institution.
• "What questions do you have for us?" Seriousness. Never have none.

Teaching

• "Describe your teaching philosophy." Give the claim from Module 4, then one concrete practice. Don't recite the document.
• "What courses could you teach for us?" Your three-tier list. Include the required ones by name.
• "How would you teach [their required course]?" Have a real answer. This question is asked constantly and answered vaguely.
• "Describe a time a class went badly. What did you change?" Reflective practice. The candidate who has no example is the concerning one.
• "How do you handle students who are underprepared?" Mechanisms, not sympathy.
• "How do you engage students who don't participate?" Specific techniques — structured pairs, cold-call-with-warning, written-first formats.
• "How do you approach generative AI in your courses?" Now near-universal. Have a considered position tied to learning outcomes.
• "What would you do about a student who challenges your expertise?" Temperament. Curiosity, not defensiveness.
• "How do you assess learning?" Alignment thinking. Reference outcomes.
• "What's a new course you'd want to develop?" Curricular imagination — but tie it to a program need, not just your interest.

Research

• "Summarize your research for a non-specialist." Practice this until it's 60 seconds and jargon-free.
• "What's your next project?" Status markers. Data, IRB, drafts, dates.
• "What's your funding plan?" Name programs and cycles.
• "How would you involve students in your research?" Specific tasks by level.
• "How will you maintain research productivity on a 3-3 load?" Realism. A concrete weekly structure beats an expression of commitment.
• "What would you publish in the next three years?" Calibration. Name plausible venues.
• "How does your work relate to Professor X's?" Whether you did the reading.

Service, collegiality, and the department

• "What service would you want to take on?" Willingness. Name something specific and unglamorous.
• "Describe a conflict with a colleague and how you handled it." The collegiality test. Never blame. Show what you learned.
• "How do you contribute to an inclusive environment?" Actions with outcomes, not values.
• "What would you want to change about our program?" A trap and an opportunity. Answer with humility plus one genuine, well-informed observation. Pure flattery reads as unserious; sweeping critique reads as arrogant.
• "How do you work with colleagues who disagree with you?"

The hard ones, by path

Questions you should ask them

Vary these by audience. Asking a dean about photocopying, or a grad student about the budget, signals you don't understand roles.

• To the chair: "What does the teaching load actually look like in practice — preps, sections, and course releases?" · "What does success look like for this person in year three?" · "How are courses assigned?" · "What's the department's biggest challenge right now?"
• To junior faculty: "What surprised you in your first year?" · "How is mentoring handled?" · "Is the tenure process transparent?" · "What do you wish you'd asked before accepting?"
• To senior faculty: "How has the department changed over your time here?" · "What holds it together?"
• To students: "What do you wish this program had?" · "What makes a professor good here?" · "What do students complain about?"
• To the dean: "Where is the school investing over the next five years?" · "How does this position fit that?" · "How does the school think about enrollment trends in this area?"
• Ask everyone: "What do you like most about working here?" The variance in answers is the most honest signal you'll get about the place.

The offer and negotiation

Between the visit and the offer

• Thank-you emails within 24 hours to the chair, the search chair, and anyone who spent substantial time with you. Reference something specific from each conversation. Individual notes, not a group email.
• If you have a competing timeline, tell the chair honestly and early. Departments can sometimes accelerate; they can never accelerate a deadline you told them about the day before it hits.
• Silence is normal. Searches take weeks. One polite status inquiry after the stated timeline has passed is appropriate.

When the offer comes

• Express genuine enthusiasm, then ask for it in writing and for time to review. Two weeks is standard and reasonable to request.
• Never accept on the phone, and never negotiate on the first call. "I'm delighted. Could you send the written details? I'd like to review carefully and come back to you within the week."

What's negotiable

Handling multiple offers and declining

• Be honest about timelines with everyone. Playing offers against each other clumsily is a small world's fastest reputational damage.
• You may tell a department you have another offer and ask whether they can accelerate. That's normal and expected.
• Decline graciously and promptly. The chair you decline this year sits on a committee, reviews your papers, and may hire you in a decade. Thank them specifically, don't over-explain, and mean it.

Module 9 checklist

• 90-second self-introduction rehearsed out loud
• 60-second jargon-free research summary rehearsed
• Three institution-specific reasons prepared and verified
• Job talk built, timed, and rehearsed at least five times
• Backup slides prepared for anticipated technical questions
• Answers prepared for every question in the bank, including your path's hard ones
• Different question sets prepared for chair, dean, junior faculty, and students
• Video setup tested: camera height, lighting, audio, background
• Printed CV, syllabus, and one-page research summary packed
• Notebook for names
• Salary research done before any offer conversation
• Negotiation asks decided in advance as one bundled request
• Thank-you notes sent within 24 hours to everyone who spent time with you

Module 10Being a Great Professor

Getting the job is the shorter half. This module is about the part nobody trains you for — and the part that determines renewal, promotion, and whether the work is sustainable.

Managing a classroom

Classroom management is not discipline. It's design. Nearly every problem that shows up in week ten was created by an ambiguity in week one. The professors who seem to have effortless classrooms are usually the ones who front-loaded the structure.

The first day sets everything

Students form a durable model of your course in the first fifty minutes. Spend that time deliberately:

• Teach something real on day one. Do not just read the syllabus. Twenty minutes of actual content establishes that class time is used, and it is the single highest-leverage decision in the term.
• Name the norms explicitly and say why. "I cold-call, and here's why: it makes me responsible for hearing from everyone, not just the confident. I'll always give you a moment to think first."
• Say what you're strict about and what you're not. Ambiguity is what generates conflict. Being clearly strict about two things and clearly relaxed about others is easier to live with than being vaguely strict about everything.
• Learn names fast. Name tents, a seating chart, photos, whatever it takes. Nothing else changes the atmosphere of a room this much for this little effort.
• Explain the arc. Where the course goes and why it's ordered that way. Students who understand the shape complain less about the middle.

Structures that prevent problems

Managing energy and attention

• Change the mode every 12–18 minutes. Lecture, then problem, then discussion, then lecture. Attention is a resource with a refresh cycle.
• Use silence. After asking a question, count to seven. It feels unbearable and it produces answers.
• Move around the room. Physical proximity does more for engagement than any slide.
• Start on time, end on time. Every time. It's a trust signal.
• Give the room a break in a 75-minute-plus session. You lose five minutes and get thirty back.

Dealing with difficulty

The disengaged student

Disengagement is usually a signal, not a character trait — often confusion, competing obligations, or a belief they can't succeed. The move is private and early: a short, non-accusatory email. "I noticed you've missed the last two sessions. No judgment — I wanted to check whether everything's okay and whether there's something I can do." A surprising share of these emails resolve the problem entirely.

The dominating student

Handle it structurally rather than personally. "Let's hear from someone who hasn't spoken yet." Use think-pair-share so airtime is distributed by design. If it persists, a private conversation framed around their strength: "You're clearly engaged — I want to use that. Can you help me draw out the quieter students?" That framing converts a problem into an ally more often than confrontation does.

The student who challenges your authority

Especially common for early-career faculty, women, faculty of color, and practitioners without a PhD. Two principles: never get defensive, and never over-explain your credentials. Treat the challenge as an intellectual question, engage the substance briefly, and move on. "That's a fair challenge — here's the evidence I'm relying on, and here's where it's contested. Let's look at it." Calm engagement resolves this far faster than assertion of authority, and the rest of the room reads it as confidence.

The grade dispute

• Have a written regrade policy: requests in writing, within one week, explaining which rubric criterion was misapplied. Requiring a written argument filters out most disputes and improves the remaining ones.
• Never regrade in the moment or in the hallway. "Send me that in writing and I'll look at it carefully."
• Regrade the whole assignment, and say so in advance — the grade can move in either direction.
• Document everything. If it escalates, the paper trail is what protects you.
• Know when to involve the chair. If a student threatens, invokes a parent, or raises a formal complaint, loop in your chair immediately. Do not manage it alone.

Academic integrity

• Follow your institution's process exactly. Do not handle it informally, however tempting — informal handling leaves you unprotected and is unfair to students handled formally.
• Design out the opportunity: rotating problem sets, process-based assignments, drafts and check-ins, in-class components.
• On AI specifically: detection tools are unreliable and produce false positives that fall hardest on non-native English speakers. Build assessments that make AI use either irrelevant or visible — oral defenses, in-class writing, personalized data, staged drafts — rather than relying on detection.
• When you do confront it, be procedural and unemotional. State what you observed, cite the policy, describe the process.

Students in distress

You will encounter students in genuine crisis — mental health, food or housing insecurity, family emergency, harassment. Your role is to be a bridge, not a counselor.

• Know your campus resources before you need them: counseling, dean of students, CARE/behavioral intervention team, food pantry, Title IX. Have the numbers saved.
• Say plainly: "I want to make sure you're supported. Can I connect you with someone?" Then actually make the connection — walking a student to an office is dramatically more effective than giving them a URL.
• Understand your reporting obligations. Most faculty are mandatory reporters for certain disclosures; know what yours are before a student discloses, so you can tell them at the start of the conversation.
• Be flexible on deadlines where you can, but don't become the student's support system. That's not sustainable for you and it isn't the help they need.

Difficult colleagues and department politics

• Say little in your first year. Listen, observe who aligns with whom, and don't take a side in a conflict you don't understand.
• Never criticize a colleague to a student. It travels, always, and it costs you more than it costs them.
• Find one honest senior mentor outside your immediate area, and one peer at your level. The second is often more useful.
• Say yes to service that is visible and bounded; decline service that is invisible and unbounded. Junior faculty — and especially junior women and faculty of color — get disproportionately loaded with the second kind. Learn the phrase: "I'd like to, but I need to check with my chair about my service load."
• Document your contributions continuously. Reconstructing them for a review file two years later is miserable and inaccurate.

Course evaluations

Course evaluations are a flawed instrument that measures real things imperfectly and is used consequentially anyway. The mature position is neither to dismiss them nor to be governed by them.

What the evidence says

• Evaluations correlate weakly, at best, with actual learning outcomes.
• They carry well-documented biases related to gender, race, accent, age, and appearance. Women and faculty of color receive systematically lower ratings for equivalent teaching.
• Required, quantitative, and early-morning courses score lower than electives, regardless of instructor.
• Grading leniency correlates with higher ratings.
• They do reliably measure some genuinely useful things: clarity of expectations, organization, responsiveness, perceived fairness.

Knowing this lets you do two things: improve on the dimensions evaluations actually measure well, and provide context when your numbers are read by others.

How to improve them without teaching worse

How to read them without being wrecked by them

• Don't read them the day they're released. Wait a week. The emotional response distorts your judgment about what's actionable.
• Read all of them at once and sort: actionable, contradictory, and personal. Act on the first bucket. Note the second. Discard the third — cruel comments about your appearance or accent contain no information about your teaching.
• Look for patterns across sections and terms, not individual comments. One student's complaint is noise; the same complaint from nine students is data.
• Weigh comparison, not raw score. A 4.1 in a required quantitative course may be considerably stronger than a 4.6 in a senior elective.
• Ask a trusted colleague to read them with you the first few times. They will see the pattern you're too close to see, and they'll tell you which comments to ignore.

Presenting evaluations in a review or application file

• Give the full record with departmental comparison means, not a curated selection.
• Contextualize honestly: course type, level, required vs. elective, enrollment, response rate.
• Show the trend. Improvement over time is more persuasive than a single high score.
• Pair quantitative data with peer observation letters and evidence of pedagogical development. A file resting only on student ratings is a weak file.
• If there's a bad term, address it in one sentence with what you changed. Explained is better than hidden — and hidden things get noticed.

Building the record from day one

Whatever your institution's review process, it will ask you to document things you cannot reconstruct later. Start a folder in week one and put things in it as they happen:

• Every syllabus, every term
• Every evaluation, quantitative and qualitative, with departmental comparisons
• Peer observation letters — request one per year even if not required
• Thank-you emails from students (save them; they're evidence and they're morale)
• Records of course and curriculum development
• Student supervision: names, projects, outcomes, placements
• Service: committee, dates, what you actually did
• Publications, presentations, and submissions with dates
• Grant submissions including unfunded ones, with scores
• Teaching development: workshops, certificates, reading
• A running one-page "what I did this year" file, updated monthly

Module 10 checklist

• First-day plan includes real content, not just the syllabus
• Written policies for late work, missed exams, regrades, and AI
• Rubrics distributed with assignments, not after
• Mid-semester feedback scheduled for week 6–7, with a plan to report back
• Campus support resources saved and reporting obligations understood
• One senior mentor and one peer identified
• Record-keeping folder created in week one
• Monthly 30-minute maintenance block on the calendar

AppendixThe Master Checklist

Everything, in order, in one place. Print this.

Phase 1 — Position (weeks 1–3)

• Authority inventory completed (M1)
• 15–25 job postings pulled and coded into a course-frequency spreadsheet
• Course catalogs and faculty rosters reviewed for 20 target institutions
• One-sentence teachable zone statement written
• Three-tier course coverage list built
• Through-line claim named
• Personal website live; Scholar/ORCID/LinkedIn current and consistent
• Publishing cadence committed to, one topic chosen

Phase 2 — Build the document set (weeks 3–8)

• Academic CV in proper format with "Courses Prepared to Teach" (M2)
• Master cover letter at ~2.5 pages (M3)
• Teaching philosophy with an arguable claim and a failure paragraph (M4)
• Research statement with forward agenda and status markers (M5)
• One required-course syllabus and one proposed elective (M6)
• DEI statement grounded in specific actions (M6b)
• Teaching portfolio assembled as a single PDF
• Three to five referees confirmed and sent a full packet
• Every document proofread by another person

Phase 3 — Network continuously (start immediately, never stop)

• Target list of 15–25 institutions with contact maps (M8)
• Tracking spreadsheet with a follow-up column
• Two hours per week blocked and protected
• 4–6 outreach messages sent weekly
• "Which courses are hardest to staff?" asked every call
• "Is there one other person I should talk to?" asked every call
• 24-hour thank-you sent every time
• One guest lecture offered and delivered

Phase 4 — Apply (Aug–Oct, and again Apr–Aug)

• Reverse-engineering table completed per posting
• 45 minutes of genuine tailoring per application
• Three institution-only facts in every cover letter
• Institution name verified in every paragraph — twice
• Referees notified with deadline and submission method
• Network contacts at that institution emailed before the file lands
• Application tracker updated

Phase 5 — Interview (Oct–Mar)

• 90-second intro and 60-second research summary rehearsed out loud (M9)
• Job talk built and rehearsed five times, with backup slides
• Teaching demo designed around one idea, rehearsed five times (M7)
• Full question bank prepared, including your path's hard questions
• Separate question sets for chair, dean, junior faculty, students
• Video setup tested; printed materials packed; notebook for names
• Thank-you notes within 24 hours

Phase 6 — Offer and arrival

• Salary research done before any offer conversation (M9)
• Negotiation asks bundled into one warm, specific conversation
• Other institutions and referees informed graciously
• First-day plan with real content (M10)
• Written policies drafted before term starts
• Week-7 feedback scheduled
• Record-keeping folder created; monthly maintenance block on the calendar