How to Help Your Advocate on the Search Committee

You are not in the room when the committee decides.

Someone who likes your file is.

That person is describing your research to colleagues who have read many files and remember only a few of them. They are answering questions you will never hear. Everything they have to work with is what you gave them.

This is the other half of the veto rule. The veto rule says: give no one a reason to kill your file. This rule says: give someone a reason to fight for it.

Both are true. A file with no objections and no advocate does not get hired. It gets set aside while the committee argues about the candidates whose advocates came prepared.

You arm your advocate through the file, not by contact.

Be clear about one thing first. You do not know who your advocate is. You will not hand them a briefing, and you must not try.

Everything your advocate uses comes from two places: the documents you submit and what you do on the visit. That is the only channel. This article is about filling it.

This is also different from the strategy in Forget the game that got you here. There, the mistake is recruiting one champion and ignoring the room. Here, you are not recruiting anyone. You are building a file so clear that whoever likes it can defend it. Not a champion you recruit. An advocate your file creates.

Your advocate’s real audience is two subfields over.

In many business schools, the people who judge you are mostly from the department itself. After a shortlist, the wider faculty often discusses the finalists. Details vary by school, but one pattern is common: your advocate must persuade colleagues who do not share your specialty.

Think of the asset-pricing professor asked to vote on a corporate finance hire. The theorist evaluating an empirical researcher. The marketing modeler reading a consumer-behavior file.

That colleague is your advocate’s real audience. If your work cannot be explained to them in one minute, it cannot be defended in the meeting.

There are three decisions, and each needs different support.

1. The first cut.

The committee reduces a large stack to a longlist. The first read is fast. (For how fast, and what it looks for, see the eight-minute read.) Your advocate here is whoever read your file closely enough to say your name out loud.

What they need: a file whose contribution is visible on the first page.

2. The interview decision.

Interview slots are scarce. Your advocate argues that you deserve one.

What they need: a pipeline of research beyond one paper, evidence of teaching, and a credible reason you would come.

3. The final ranking.

After the campus visits, the department meets. Your advocate describes your visit to colleagues who met several candidates in the same weeks.

What they need: things those colleagues personally remember.

Give your advocate six things.

1. The one-sentence contribution.

What your research shows, in words a colleague outside your subfield can repeat. Your advocate will say this sentence in the meeting. If they cannot say it simply, they cannot say it at all.

The first sentence describes your method. The second describes your finding. Only the second can be repeated in a meeting. Write it, test it on a friend in another area, and put it where your file opens: the first paragraph of the cover letter and the top of the research statement.

2. The pipeline at a glance.

Your job-market paper (the main paper you present to schools), its status, and what comes after it.

“Revise and resubmit at the Journal of Finance” is a sentence your advocate can use. “Working papers available on request” is not. Show at least two further projects with a clear status, so no one can say your record is a single paper.

3. Where the work sits.

Business schools use a journal hierarchy that everyone in the room understands. Make it easy to see where your work stands: which journals have accepted it, which are reviewing it, and at what level.

One warning. Never present a working paper as a top-journal paper. An inflated claim gives the skeptic in the room an easy objection, and it embarrasses the person defending you.

4. Answers to the usual objections.

Almost every file faces the same three questions. Can this person teach our students? Would this person actually come here? Does this person fit what we need?

Put the answers in the file before anyone asks. Summarize your teaching evaluations with real numbers and courses. State specific reasons for this school. State your research fit plainly. Your advocate needs the answers before the objections are raised, not after.

5. Things people remember from the visit.

Your job talk must leave two or three sentences the audience can repeat the next day. Each one-on-one meeting should give that faculty member one specific thing they learned from you.

People argue for candidates using what they personally remember. They do not remember slide forty.

6. A reason you would say yes.

The department’s greatest fear is a failed search: an offer declined after months of work. Your advocate must be able to say why you would accept.

Give them specifics: the courses you want to teach, the colleagues you want to work with, the reason this school fits. For how to show this honestly, read why the committee asks whether you will take the job and how to show real interest.

Three things not to do.

Do not manufacture a champion. Flattering one committee member, writing only to their interests, or contacting people to lobby before the process begins: the department notices. It creates the vetoes you were trying to avoid.

Do not give anyone gossip to repeat. Private complaints about other schools, promises made over coffee, anything you would not want said in the meeting. Assume it will be said in the meeting.

Do not confuse the advocate with the decision. The advocate argues. The group decides. Your job was never to win one person’s support. It was to make your file so clear and so complete that whoever likes you can argue with facts.

But what if no one on the committee works in my area?

Then this article matters even more.

Without a specialist in the room, your advocate is the colleague two subfields over. Everything depends on the one-sentence contribution, the visible pipeline, and the answers already in your file. A file that a non-specialist can defend is a file that anyone can defend.

You will never meet the person who argues for you in that meeting.

Give them the words before they need them.

Make your file easy to defend. Then someone will defend it.