What Makes a Successful Business PhD Application?

You’ve decided you really do like research, and you have a list of programs. Now the question is how to actually get in.

The most useful starting point is understanding who reads your application: research faculty. Not an admissions office, not HR. Professors on a PhD committee are asking one question: “Will this person become a productive researcher who I’d want to work with for the next five or six years?” Every piece of your application is evidence for or against that question.

Keep in mind this is all from my perspective, so take it as one data point to triangulate with other perspectives (see the end of this article for some good ones).

What committees are looking for

In my experience, a strong application makes four things believable:

You can do research. You’ve done real research work (CV shows research experience and/or papers), and someone credible says you’re good at it (relevant letters of recommendation).
You have the analytical horsepower. Your grades, coursework, and test scores show you can handle PhD-level quantitative training.
You know (roughly) what you want to study, and you know what research is. Your statement shows you’ve read the literature and have questions that fit the field, without being so locked in that you can’t be trained or shaped.
You fit this program. There are faculty here who broadly study what you want to study, and you can name them.

Here’s how each part of the application speaks to those four things, in roughly the order I think they matter.

Letters of recommendation

Letters are one of the most important parts of the application. You typically need three letters of recommendation.

The best letter comes from a research professor who has done research with you and can say specific things like “this student independently cleaned a messy dataset, found a problem I hadn’t noticed, and proposed a fix.” It’s even better if the letter writer is someone the committee knows and trusts, or is known in their same field.

Letters from professors who only know you from class are weaker; they can speak to your grades, but the committee can already see your grades. Letters from managers in industry carry very little weight with an academic committee, however impressive your job was. You may include one from industry if needed, but no more than that under any circumstances.

The practical implication: you need to work with research faculty well before you apply. That’s a big part of why I run my Innovation Research Lab. If you’re at BYU, the Marriott Research Fellows program and pre-PhD seminars are good on-ramps too. Ask your letter writers early (by late summer at the very latest), and give them your CV, a draft statement, and your list of schools.

Research experience

Research experience matters for two reasons. First, it gets you the letters above. Second, it’s the best evidence that you know what the job actually is and still want it. Committees worry a lot about admitting someone who discovers in year two that they don’t like research. They want someone who can hit the ground running.

Good ways to get it:

Work as an undergraduate research assistant for a professor (ideally on a real paper, not just one-off grunt tasks).
See if you can attend a conference or two with the professor. If you can present (or they present one of the papers you are working on) that’s great and can be added to your CV.
Some people take a full-time predoctoral research job for a year or two after graduating. These have become a very common path into top programs, especially for applicants who decide on a PhD late. If you’re a BYU student, you typically don’t have to do this if you start early doing research with professors.
Write an honors thesis or independent research project with a professor (I have no experience with this but I think it works for one letter)

Grades, coursework, and test scores

Committees use these as a screen for whether you can survive the first two years of coursework, and as a rough proxy for intellectual horsepower. A great transcript won’t get you in by itself, but a weak one can keep you out.

Coursework. Quantitative courses carry the most signal: microeconomics, econometrics, statistics, and math. For strategy, I recommend an Economics minor if you can fit it, including Industrial Organization if possible (see the recommended classes for my lab).
GRE/GMAT. Programs differ on which test they accept and whether it’s required, so check each one. I think most programs accept both. Where scores are used, the quantitative score probably matters more (certainly true in more Econ-focused programs). It’s worth the time and money to do a prep course. I recommend going all in on prep on a relatively fast schedule, like studying nearly full time for six weeks in a summer, so you can just hit it hard and move on.

Statement of purpose

Traditionally these were really important, though I’ve started to hear it’s less of a signal now with AI. However, it’s still important not to bomb it.

Typically I recommend using 80-90% of the same statement for all applications, with customization focused on connecting your interests to specific research-active faculty in the department.

A good statement:

Leads with research interests, framed as questions the field would recognize. Something like “How do firms decide which novel products to invest in when demand is hard to observe?” is a research question. “I’m passionate about innovation” is not.
Shows you’ve read the literature. Mention a stream of research or a couple of papers that shaped your thinking. This is where all that clicking around faculty pages (see where to apply) pays off.
Describes your research experience concretely: what you did, what you learned.
Explains why you are specifically applying to this program, naming specific faculty whose work connects to yours. Semi-customize this paragraph for every school. Ideally, focus on midcareer research-active faculty. Mentioning an assistant professor or nearly-retired person is fine, but for example focusing on three nearly-retired luminaries who haven’t published in 20 years is a red flag in my opinion. Show that you are interested in the people who might actually be your mentor or advisor (tenured and highly research active).
Stays focused on research. Avoid long life-story monologues, and avoid saying the main reason you want a PhD is to teach or to be a business guru. That’s a red flag to a research committee (see Should You Do a Business PhD? for why).

Show interests that are specific but not rigid. Committees know your interests will evolve; they want to see that you can think like a researcher, not necessarily that you’ve already picked a dissertation.

Here is a folder of example statements of purpose from successful business PhD applicants, compiled by Stephen Turban and Megan Gorges.

Academic CV

Use an academic CV, not a business resume. Put education and research experience at the top, then any papers, presentations, or working projects, then relevant skills (coding, statistical software, languages), and only then work experience. Keep it clean and keep it real; committees can tell when an RA task is being oversold.

Here is a folder of example CVs from business PhD applicants, from the same guide.

Interviews

Not every program interviews, but many do (often short video calls with a few faculty). The questions are rarely tricky. Expect things like:

What are your research interests, and how did you get interested in them?
Tell me about a paper you liked recently. Why did you like it, and what would you change?
Tell me about your research experience. What did you actually do?
Why this program, and which faculty would you want to work with?
What do you want to do after the PhD?

The best preparation is to know your own statement, have two or three papers you can discuss in depth, and be aware what the faculty you named are working on.

Keep answers fairly concise and conversational. Avoid long monologues. Smile. A lot of the purpose of the interview is to just make sure you’re someone who can hold a two-way conversation. You don’t need to impress them with how brilliant you are, just be curious, interested, professional, and kind.

Here is a compiled list of business school PhD interview questions that real applicants were asked.

A rough timeline

Most deadlines fall in December and early January, with decisions arriving roughly February through April. Working backward:

When	What
1–2+ years before	Start doing research with faculty (or take a predoc job). Take the quantitative coursework.
Spring–summer before applying	Study for and take the GRE/GMAT. Read papers and build your list of programs and faculty.
Late summer	Ask your letter writers, and give them your materials.
Fall	Write and revise your statement of purpose; get feedback from faculty.
December–January	Submit applications.
February–April	Interviews, visits, and decisions.

Common mistakes

Applying before you have research experience or research letters. If you’re not there yet, it might be better to spend a year as a predoc or RA and apply the next cycle.
A fully generic statement of purpose that could be sent to any program, or that is about wanting to teach.
Applying to the wrong department (for example, an economics-flavored strategy department when you want to study organizations). See where to apply; I made this mistake myself.
Applying too narrowly. Admissions are noisy. Expect to apply to roughly 10–20 schools.
Waiting too long to ask for letters. Your letter writers are busy, and a rushed letter is a weaker letter. They should know they are a letter writer well in advance of the applications.

Other perspectives

I wrote my articles before I came across these two guides. They’re more comprehensive on the application mechanics and worth reading alongside mine:

The Complete Guide to Business School PhD Applications by Stephen Turban and Megan Gorges (both from HBS). Covers each application component in depth, interviews, and the rise of predoctoral research jobs. It’s hosted on an education company’s site, so skip past the program promotions at the end. Its example CVs, statements of purpose, and interview questions are especially useful.
A Guide to Business PhD Applications by Abhishek Nagaraj (Berkeley Haas). A classic primer on the career and the application packet, with extra notes for international applicants. It was written in 2010, so specifics like test-score targets are dated, but the core advice holds up.

Still deciding? Start with Should You Do a Business PhD? and Where Should You Apply? Questions? Come talk to me.