faculty-interview
Skill8 starsChanged 5 months agoMITView on GitHub
Prepare for an academic job interview: job talk, chalk talk, 1:1 meetings with PIs and deans, dean's talk, dinner etiquette, thank-you emails, and start-up package negotiation (funds, lab space, equipment, moving, partner accommodation). Use when invited for an on-site or virtual on-site for a faculty position.
In this repository125 other files it gives its agents.
- AGENTS.mdAGENTS.md
- skills/AGENTS.mdAGENTS.md
- batch-processingSkill
- bowtie2-alignmentSkill
- bwa-alignmentSkill
- bwa-mem2-alignmentSkill
- codon-usageSkill
- compressed-sequence-filesSkill
- fastq-quality-scoresSkill
- filter-sequencesSkill
- format-conversionSkill
- hisat2-alignmentSkill
- motif-searchSkill
- paired-end-fastqSkill
- pysam-genomicsSkill
- read-write-sequencesSkill
- reverse-complementSkill
- sam-bam-basicsSkill
- samtools-bam-processingSkill
- seq-objectsSkill
- sequence-propertiesSkill
- sequence-slicingSkill
- sequence-statisticsSkill
- star-alignmentSkill
- transcription-translationSkill
- academic-cvSkill
- fellowship-applicationSkill
- industry-transitionSkill
- negotiationSkill
- tenure-dossierSkill
- admet-predictionSkill
- conformer-generationSkill
- covalent-designSkill
- docking-rescoringSkill
- free-energy-calculationsSkill
- generative-designSkill
- molecular-descriptorsSkill
- molecular-ioSkill
- molecular-standardizationSkill
- pharmacophore-modelingSkill
- pose-validationSkill
- protac-degradersSkill
- qsar-modelingSkill
- retrosynthesisSkill
- scaffold-analysisSkill
- shape-similaritySkill
- similarity-searchingSkill
- substructure-searchSkill
- virtual-screeningSkill
- snakemake-workflow-engineSkill
- ai-disclosureSkill
- data-privacySkill
- image-integritySkill
- irb-protocolSkill
- ai-detection-awarenessSkill
- ai-disclosure-statementSkill
- scientific-voice-styleSkill
- text-humanizing-editorialSkill
- cellprofiler-pipelinesSkill
- image-analysis-best-practicesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
No fabricated citations: Every cited work must resolve to a verifiable
- Distinctive: line 21
No claim without provenance: Every quantitative or factual claim
- Distinctive: line 22
No silent failure: Every script invocation, API call, or tool use must declare its exit status and what to do on non-zero.
- Distinctive: line 106
Do not read from slides; use them as a backdrop.
- Distinctive: line 147
Take notes: after each meeting: names, topics, follow-up actions.
- Distinctive: line 161
Be a generous conversationalist: ask about the host's research, hobbies, and history at the institution.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- metadata:
category: career-navigation
oversight: high
version: 1.0.0
author: Pradyumna Jayaram
tags: [career-navigation, research]
difficulty: intermediate
-->Academic Faculty Job Interview
Hard rules
- No fabricated citations. Every cited work must resolve to a verifiable
- No claim without provenance. Every quantitative or factual claim
- No silent failure. Every script invocation, API call, or tool use must declare its exit status and what to do on non-zero. A skill that silently swallows errors is a violation.
When to use
- You have been invited to an on-site or virtual on-site for a tenure-track faculty position.
- You are preparing a job talk for a research seminar, a chalk talk, or a teaching demonstration.
- You are negotiating a start-up package after receiving an offer.
- You are preparing for a dual-career / partner-accommodation conversation.
- You are deciding between multiple offers and need a structured comparison.
When NOT to use
- Postdoc interview — much shorter; no start-up package. Some sections (job talk, 1:1 meetings) still apply, but at a smaller scale.
- Industry interview — see
ors-career-navigation-industry-transition. - Tenure case — see
ors-career-navigation-tenure-dossier. - Government / national-lab interview — overlaps with faculty but the start-up package is different (federal positions have stricter rules on negotiation).
Prerequisites
- A current CV (see
ors-career-navigation-academic-cv). - A research statement and teaching statement (typically submitted with the application)."
- A list of 5-7 representative projects for the "story bank".
- Knowledge of the department: faculty pages, recent hires, recent seminars, recent news, the search committee chair's research area.
- Knowledge of the institution's tenure criteria (see
ors-career-navigation-tenure-dossier). - Names of the people you will meet (the search committee or HR will provide a schedule; ask for the full list and short bios in advance).
- A 30-60-90 day plan for the first three months of the position.
Core workflow
1. Pre-interview preparation (2-4 weeks out)
- Read the department's website: faculty list, recent hires, research areas, courses taught. Identify 2-3 potential collaborators whose work overlaps with yours.
- Read 3-5 recent papers from likely committee members: this signals respect, gives you talking points, and reduces the chance of an awkward question.
- Read the institution's strategic plan, faculty handbook, and tenure criteria: align your talk and answers with their priorities (research excellence, teaching quality, diversity, broader impacts).
- Draft the talk (see step 2).
- Draft the chalk talk (see step 3) — for R1, this is a separate session.
- Build a Q&A bank (see step 4) — 20-30 questions with rehearsed answers.
- Plan your wardrobe: business formal for the job talk and dean's talk; business casual for 1:1 meetings; check the institution's local customs (some R1s are more formal, some land-grants are less so).
- Logistics: book travel, plan to arrive the night before, plan a 10-15 minute buffer for walking between meetings.
2. The job talk (45-60 min talk + Q&A)
The job talk is the single most evaluated component of the interview. The audience is a mix of people in your subfield, people in adjacent fields, and people in unrelated fields. Design for the median: assume the audience is smart but not in your subspecialty.
Structure (45-50 min talk, 10-15 min Q&A):
- Title slide with the talk title, your name, your current position, and the institution logo (small, in a corner).
- The big question (1 slide, 2-3 min): what problem are you working on, and why does it matter? Plain language. Analogies welcome.
- Background and prior work (2-3 slides, 5-7 min): what was known before you started. Cite the field, not just your papers.
- Your approach (1-2 slides, 3-5 min): what is distinct about your method or angle.
- Major results (10-15 slides, 15-20 min): the core of the talk. For each result: what you did, what you found, what it means.
- Future directions (3-5 slides, 8-10 min): where the program is going, what you will do in the first 3-5 years, what the first papers and grants will be. Be specific: name the techniques, the model systems, the datasets.
- Funding, students, and fit (1-2 slides, 3-5 min): your funding trajectory, the students and postdocs you will recruit, how the program fits the department's strengths.
- Acknowledgements (1 slide, 1 min): collaborators, funding sources, mentees.
Style guidance:
- Less is more: 1 idea per slide; 1 figure per slide; minimal text.
- Speak to the median: define jargon on first use; explain a method in 1 sentence.
- Time the talk: practice with a timer. A 45-minute talk is usually 35 minutes of content and 10 minutes of breathing room for Q&A.
- Rehearse 5+ times: in front of a real audience, not just a mirror.
- Build a "back pocket" slide: a slide with 2-3 results you can show if asked a question you did not anticipate.
- Test the AV: get to the room 30 minutes early; test the clicker, the audio, the adapter, the screen layout.
3. The chalk talk (R1: research vision; teaching-focused: classroom simulation)
The chalk talk is a more interactive session, often 30-60 minutes, with a smaller audience (search committee, department leadership). Two flavors:
R1 chalk talk: research vision. The candidate presents a 2-3 year research plan in detail and the committee asks questions. The chalk talk is not just about content; it tests how you think on your feet, how you receive critical feedback, and how you would build a program in the first few years.
- Bring 5-7 slides; present at a high level; expect to be interrupted often.
- Be ready to discuss: the first 3-5 papers, the first 1-2 grant submissions, the first hires (postdoc, technician, students), the lab setup, the equipment, the collaborations.
- Have a clear "Plan B" for each research thread: if the first approach fails, what is the fallback? Committees want to know that you can pivot.
Teaching-focused chalk talk: classroom simulation. The candidate teaches a 15-20 minute segment of a course they would offer, with department members playing the role of students.
- Pick a topic that is engaging and self-contained.
- Plan 2-3 questions to ask the "students" to check understanding.
- Be ready to handle a "student" who is confused, off-topic, or challenging.
- Show your teaching philosophy in action: how you structure the lesson, how you check understanding, how you adjust on the fly.
For both flavors:
- Bring chalk or markers that work on the board (or use a tablet with a stylus).
- Do not read from slides; use them as a backdrop.
- End by asking the committee what they would want to see next.
4. The Q&A bank
Prepare answers to:
- "Why this department?" — fit, collaboration, students, location, mission.
- "What is your 5-year plan?" — funding, papers, people, equipment.
- "How will you fund your program?" — be specific about agencies, mechanisms, timelines.
- "What is your mentoring philosophy?" — see
ors-mentorship-teaching-ors-mentorship-onboarding. - "What courses could you teach?" — be ready with 2-3 specific course proposals.
- "How do you handle failure / negative results?" — be honest, give an example, show the pivot.
- "What is the most novel idea in your program?" — single sentence; then elaborate.
- "Who at our institution would you want to collaborate with?" — name 2-3 people; have read their work.
- "What is your teaching philosophy?" — see
ors-career-navigation-academic-cvfor teaching statement guidance. - "How will you support diversity, equity, and inclusion in your program?" — concrete actions, not platitudes.
- "What is your biggest weakness?" — pick a real one and explain what you are doing about it.
- "What questions do you have for us?" — always have 2-3 thoughtful questions prepared.
For tough questions, the formula is: pause, acknowledge the question, give a direct answer, and offer a follow-up. Do not get defensive. Do not bluff — say "I do not know, but I would find out by X".
5. 1:1 meetings with PIs and deans
The on-site typically includes 8-15 individual meetings, 30-45 minutes each, with:
- Search committee members
- Department leadership (chair, vice chair)
- Senior faculty in your area
- Junior faculty (often a critical vote; they will ask different questions)
- Potential collaborators
- The dean or school-level leadership (often a separate "dean's talk")
- A graduate student meeting (often informal; very important — students will be honest with the chair about their impressions)
- A meeting with HR or the office of faculty affairs (administrative: benefits, start-up, policies)
For each meeting:
- Read the person's most recent papers (one or two) before the meeting.
- Open with a question about their work: "I read your 2024 paper on X; how is that line of work evolving?"
- Have a 2-minute "research in 2 minutes" pitch ready: a tight, plain-language summary.
- End with a forward-looking question: "What would you want to see from a new colleague in their first year?"
- Take notes after each meeting: names, topics, follow-up actions.
For the dean's talk: this is often a higher-level conversation about institutional priorities, support, and expectations. Listen for:
- The dean's priorities (research, education, diversity, community engagement).
- The school's funding model and how start-up is allocated.
- The school's expectations for tenure (often stricter than the department's).
- The dean's openness to dual-career accommodation and family-support policies.
6. Dinner etiquette
The dinner is a chance to show that you are collegial, normal, and would fit the department socially. The dinner is also evaluated — search committees do not write down everything, but they do share impressions.
- Order something easy to eat (avoid spaghetti, ribs, very messy dishes). Wine or beer is fine; one or two drinks.
- Be a generous conversationalist: ask about the host's research, hobbies, and history at the institution.
- Avoid hot topics (politics, religion, hot-button institutional controversies).
- Do not be the loudest voice in the room: the goal is to be pleasant and interested, not to perform.
- If asked about your "other offers": be honest but brief. "I am in conversation with a few other institutions; I will keep you posted."
- End by thanking the host: a short text the next morning is appropriate.
7. Follow-up thank-you emails
Send a thank-you email within 24 hours to:
- The search committee chair (always).
- The department chair (always).
- The dean (always).
- Anyone who is a likely strong advocate (a senior faculty member who was very engaged; a junior faculty member who championed you).
- The graduate students you met with (often neglected; a thank-you note here is remembered).
Each email: 1-3 short paragraphs, mention a specific topic from the conversation, reaffirm your interest. Do not send a form letter.
8. Start-up package negotiation
The start-up package is the single most consequential negotiation of the early career. See ors-career-navigation-negotiation for the full framework. Key points for the academic case:
Components of a start-up package:
| Component | Description | Range / context |
| Start-up funds | One-time allocation for equipment, personnel, supplies, travel | Varies by field and institution; consult senior mentors |
| Lab space | Square footage, location, renovations | Negotiate before signing; space is hard to add later |
| Equipment | Shared vs dedicated; service contracts | Often the largest single line item |
| Moving allowance | Relocation costs; sometimes includes temporary housing | Varies; sometimes taxable, sometimes not |
| Partner accommodation | Dual-career support; spousal hire, adjunct, or career services | Varies dramatically by institution; ask early |
| Summer salary | First 1-3 summers; reduces teaching | Common at research-intensive institutions |
| Course release | Reduced teaching in year 1 or 2 | Often negotiable; helps lab ramp-up |
| Graduate student support | Funded slots, recruiting priority | Critical in lab sciences |
| Postdoc support | Funds for first postdoc | Often a separate line; sometimes indirect |
| Administrative support | Grant-writing, HR, IT | Increasingly important |
| Salary | 9-month base; sometimes a 12-month option | Usually set by rank; sometimes negotiable |
Negotiation principles:
- Everything is negotiable until the offer letter is signed.
- Get the offer in writing before negotiating.
- Negotiate components, not just total dollars. Equipment may be more useful than a salary bump.
- Be specific in your asks. "I would like a 200 sq ft dedicated tissue culture room and a 1-year postdoc line" beats "more resources".
- The BATNA (best alternative to a negotiated agreement) is your other offer, your postdoc, or your current position. Know your BATNA before the call.
- Be collegial and appreciative. The chair and dean are also negotiating with you in mind; they will work with you for years.
Dual-career / partner accommodation:
- Bring it up early in the process — typically after the on-site, before the offer.
- The earlier you raise it, the more options HR has. Asking the day before signing puts HR in a corner.
- Be ready with your partner's CV, research area, target roles, and geographic constraints.
- Options: spousal hire (a tenure-track line for the partner), spousal adjunct, spousal consulting, dual-career office assistance (resume review, networking), partner relocation support.
- Some institutions have formal dual-career programs; others handle case by case.
9. Comparing multiple offers
Build a comparison table:
| Dimension | Institution A | Institution B | Institution C |
| Position | Assistant Prof | Assistant Prof | Assistant Prof |
| 9-mo base | X | Y | Z |
| Start-up | $X | $Y | $Z |
| Lab space | A sq ft | B sq ft | C sq ft |
| Course release | 1 sem Y1 | None | 1 sem Y1+Y2 |
| Partner accommodation | Dual-career office | Adjunct possible | Spousal hire possible |
| Location | City A | City B | City C |
| Tenure criteria | Document X | Document Y | Document Z |
| Mentor / chair support | Strong | Variable | Strong |
Weigh what matters to you and your family. The "best" offer is not always the highest start-up.
Code patterns
Job talk outline (Markdown)
# [Title]
## 1. The big question (2-3 min)
- Plain-language statement of the problem
- Why it matters
## 2. Background (5-7 min)
- What was known
- What was missing
## 3. Our approach (3-5 min)
- What is distinct
- Why it works
## 4. Major results (15-20 min)
- Result 1
- Result 2
- Result 3
- Result 4
## 5. Future directions (8-10 min)
- Year 1-2 plan
- Year 3-5 plan
- Collaborations at [institution]
## 6. Funding, students, fit (3-5 min)
- Funding trajectory
- Recruitment plan
- Departmental fit
## 7. AcknowledgementsQ&A bank template
| Question | Short answer (30 sec) | Long answer (2-3 min) |
|----------|------------------------|------------------------|
| Why this department? | [Fit, people, place] | [Specific collaborators, courses, mission] |
| 5-year plan? | [3 papers, 1 grant, 2 students] | [Specific aims, named agencies, named trainees] |
| Funding strategy? | [NSF, NIH, foundation] | [Mechanisms, timelines, parallel submissions] |
| Mentoring philosophy? | [One-sentence] | [See ors-mentorship-onboarding] |
| Teaching interest? | [Course titles] | [Syllabus sketch, philosophy] |
| DEI contribution? | [Concrete actions] | [Past record, future plan] |
| Weakness? | [Real one] | [What you are doing about it] |Start-up budget (rough categories, amounts in your local context)
| Item | Year 1 | Year 2 | Year 3 | Total |
|------|--------|--------|--------|-------|
| Postdoc (1) | X | X | X | X |
| Grad student (1-2) | Y | Y | Y | Y |
| Technician | Z | Z | Z | Z |
| Equipment | A | 0 | 0 | A |
| Supplies | B | B | B | 3B |
| Travel | C | C | C | 3C |
| **Total** | X+Y+Z+A+B+C | ... | ... | T |This is a planning tool for the conversation with the chair, not a final budget.
Common pitfalls
| Pitfall | Why it fails | Fix |
| Job talk is a 60-minute paper | Committee zones out; the future-directions section is cut | Restructure to 35-40 min content + 10-15 min future |
| Slides have too much text | Audience reads, not listens | 1 idea per slide; figures dominant |
| Q&A answers are 5 minutes long | Other committee members lose the thread | Aim for 1-2 minutes; offer a follow-up |
| No plan for funding | "I will write grants" is not a plan | Name 2-3 specific mechanisms and timelines |
| No knowledge of the department's courses | "I can teach whatever is needed" is vague | Propose 2-3 specific courses with one-line descriptions |
| Bad-mouthing the previous advisor | Signals poor judgment | Speak about your work, not theirs |
| Not asking questions in 1:1s | "I don't have any" signals lack of interest | Prepare 2-3 questions per meeting |
| Drinking too much at dinner | One drink is plenty | Know your limit; switch to water after one |
| Neglecting the grad student meeting | Students talk; their impressions matter | Treat them as colleagues; take their questions seriously |
| No thank-you emails | Committee wonders why; missed opportunity | Send within 24 hours; personalized to each person |
| Negotiating the start-up before knowing the components | Total dollar is a proxy for the wrong things | Negotiate each line; get the package in writing |
| Not raising the dual-career question | Awkward to raise after the offer | Raise it after the on-site, before the formal offer |
| Signing the offer too fast | Missed negotiation window | Always take the time to read, ask questions, and counter |
| Burning bridges after declining | Academic world is small | Thank the chair and dean; keep relationships warm |
| Failing to ask about tenure criteria during the on-site | Surprise later | Ask senior faculty and the chair what the criteria mean in practice |
| Skipping the lab / space walkthrough | Surprises after arrival | Walk the lab; ask about renovations, equipment, and neighbors |
Validation
A complete faculty-interview preparation satisfies:
- Job talk drafted, rehearsed 5+ times, time-checked, AV-tested
- Chalk talk content prepared (R1 research vision or teaching simulation)
- Q&A bank with 20-30 questions; rehearsed with a mentor
- 2-3 specific course proposals drafted
- Research 3-5 papers from each committee member
- 2-3 specific questions per 1:1 meeting prepared
- Dinner behavior rehearsed (e.g., mock dinner with mentors)
- Thank-you email templates drafted
- Start-up budget prepared
- Dual-career / partner accommodation strategy ready
- Offer comparison table ready (if multiple offers in hand)
- BATNA analysis complete (see
ors-career-navigation-negotiation) - 30-60-90 day plan for the first three months drafted
- Mentorship team briefed: who is your senior advisor at the new institution?
- Logistics: travel, hotel, ground transport, wardrobe, materials all set
Open alternatives
| Commercial / proprietary | Open equivalent | Trade-offs |
| PowerPoint, Keynote | LibreOffice Impress, Beamer (LaTeX), reveal.js (HTML) | Beamer is the academic-standard; reveal.js works well in browsers |
| Mentorship matching platforms (e.g., ADPList) | Senior mentors in your network, formal mentoring programs at the new institution | Institutional mentoring is more durable |
| Pre-move relocation services | Self-research via public HR pages, city-data sites, school district data | Public sources are usually sufficient |
| Polished CV-writing services | A trusted mentor in your field | Mentor review is more credible and tailored |
References
- AAUP standards on academic hiring and tenure
- Nature Careers "Futures" column archive
- Science Careers "Interviewing for an Academic Job" article series
- Hertz Foundation public interview-preparation guidance
- MIT, Stanford, UC Berkeley, and University of Michigan public faculty search handbooks
- National Center for Professional and Research Ethics (NCPRE) resources
- Public university policies on dual-career accommodation (institutional HR pages)
- NSF CAREER award guidelines (relevant to start-up and tenure planning)
- NIH K99/R00 and other early-career mechanisms (relevant to start-up planning)
- University of California "Faculty Recruitment Toolkit" (publicly available)
Related Skills
ors-career-navigation-academic-cv— the CV that goes into the application packetors-career-navigation-tenure-dossier— the long-term plan that the job talk and chalk talk should foreshadowors-career-navigation-negotiation— full negotiation framework for the start-up packageors-career-navigation-industry-transition— for candidates running academic and industry searches in parallelors-mentorship-teaching-ors-mentorship-onboarding— mentoring statement for the packetors-research-grants-nsf-standardandors-research-grants-nih-r01— funding plan contentors-scientific-slides— slide design for the job talk
Changelog
- 1.0.0 (2026-06-10): Initial adaptation by Pradyumna Jayaram. Compiled from public AAUP, university faculty handbooks, Nature Careers, Science Careers, and Hertz Foundation guidance; cross-referenced to negotiation and tenure skills.
Cross-references
Other skills in this category:
- academic-cv
- fellowship-application
- industry-transition
- negotiation
- tenure-dossier
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

