What Does a Consultant Actually Do All Day?

A management consultant is hired to answer a specific business question a company cannot answer well on its own, then to build a slide-backed argument for what to do about it. Day to day, that means gathering data, building models in Excel, turning findings into a deck, sitting in client meetings, and presenting a recommendation to executives on a deadline measured in weeks. The job is less about deep expertise in one industry and more about structured problem solving, communication, and speed, applied to whatever problem the client happens to be paying to fix this quarter.

I spent years on the other side of the hiring table at McKinsey, reviewing resumes in batches of roughly 400 and running interviews for people trying to get into this exact job. What struck me, watching people join, was how fast the outside image of consulting collided with the inside reality. Candidates picture strategic pronouncements in a boardroom. What they get for the first several years is spreadsheets, data cleaning, and a deck that has to be perfect by 7 a.m.

What a consulting engagement actually looks like

Most engagements run six to sixteen weeks, staffed with a small team: one or two analysts or associates, a manager who runs the day-to-day, and a partner who shows up for the big moments and is otherwise selling the next project. The client is not buying headcount. It is buying an answer, so every week has something concrete attached to it, usually a working session or an interim readout with a handful of slides that move the argument forward.

The work itself sits in three buckets, and almost everyone at the junior levels spends most of their week rotating through them.

• Gathering and structuring information: pulling data from the client's systems, interviewing their staff, reading industry reports, and turning a pile of scattered facts into something you can actually reason about.
• Analysis: building the model that turns those facts into a number, whether that is a market sizing, a cost breakdown, or a scenario comparison, and stress-testing it so it survives a partner's questions.
• Communication: turning the analysis into a deck and a narrative, then presenting it, defending it, and revising it after the client pushes back.

None of that requires industry expertise walking in the door. It requires being fast and rigorous with unfamiliar problems, which is exactly what a case interview is built to test before anyone gets hired.

A typical week, roughly

No two weeks look identical, but a project week for a junior team member tends to follow a shape close to this.

That Monday-through-Thursday-on-site pattern has loosened up since 2020. Plenty of engagements now run two or three days on-site instead of four, and some are staffed close enough to home that travel barely factors in. But the shape of the work inside each day, gather, analyze, present, revise, has not changed much.

The hours and travel question, honestly

This is the part every candidate wants a real number on, and the honest answer is a range rather than a single figure. Per publicly reported figures and firm reviews from recent cycles, entry-level consultants at the top firms tend to report somewhere in the 55 to 65 hour range per week during active projects, with heavier weeks around a deadline pushing higher and quieter weeks between staffings pulling that down. Travel has historically run three to four nights away per week on client-facing projects, though hybrid and local staffing options have become more common and firms increasingly let people request less travel-heavy assignments. Ask about both numbers directly in your recruiting conversations, because they vary by firm, office, and practice area, and the person interviewing you will respect the question rather than penalize it.

What changes as you move up

The tasks above do not disappear as you get promoted. What changes is which bucket eats most of your week, and how much of the thinking is yours versus assigned to you.

By the time someone reaches partner, they are spending far more time selling work and managing relationships than they are building models themselves. The skills tested in the hiring process, structuring a problem from scratch and defending a recommendation under pressure, matter at every one of these levels. They just get applied to bigger and messier problems as you climb.

The promotion clock also moves faster than in most careers. Two to three years as an analyst, another two or three as a consultant, and someone can be running client relationships by their late twenties. That speed is a large part of the appeal, and also why the hours in the first few years get framed as a trade rather than a permanent condition. Most people who stay past the first promotion do so because the problems get more interesting, not because the hours get lighter.

What the job is not

People walk into this career expecting a lot of high-level strategy talk and not much grunt work. The actual ratio, especially in your first two or three years, runs the other way. You will spend far more hours in Excel than in a strategy conversation with a CEO. You will format slides at 11 p.m. more often than you will deliver a bold recommendation to a boardroom. None of that means the job is dull. Building a model that survives scrutiny and finding the one insight buried in a messy dataset is genuinely interesting work, once you get past expecting it to look like a business school case study.

The other misconception is that the job requires a business background. It does not. My own background was chemical engineering, with zero business coursework, and the skills that got me hired were the same ones tested in every case interview: structuring an unfamiliar problem, doing clean math under time pressure, and communicating a conclusion clearly. If you are coming from a technical or non-business background and wondering whether you fit, the prep guide for non-business majors walks through exactly how that translates.

A related misconception is that every project feels the same. A cost-cutting engagement in manufacturing runs nothing like a growth strategy project for a software company, even though the underlying muscle, breaking an ambiguous problem into pieces you can actually solve, stays constant. That variety is the reason people who like the job tend to like it for years. You are rarely doing the same task twice in a row, even when the hours are long.

MBB versus Big Four, and why the day-to-day differs

Not every consulting job looks like the description above. The day-to-day at a strategy-focused MBB firm and the day-to-day at a Big Four advisory practice can diverge quite a bit, in project length, in how much of the work is implementation versus strategy, and in how the hierarchy is structured. If you are choosing between paths, the comparison of MBB versus Big Four consulting breaks down where each one actually spends its time. And if you want the fuller picture of what management consulting means as an industry, not just as a job description, I go through that in what management consulting actually is.

The bottom line

A consultant's day is built from three repeating tasks, gathering information, analyzing it, and communicating a recommendation, done under a deadline for a client who is paying for an answer, not for effort. The titles and the size of the problems change as you move up, but that core loop does not. If you are deciding whether this job is for you, the fastest way to find out is to see if you enjoy that loop in a practice case, which is exactly what a case interview is designed to simulate.

Go deeper

If the day-to-day sounds like something you want, the next step is getting through the hiring process built to test for it, starting with a resume that survives a 400-deep screening pile.

Get the free resume module →

Get the complete Cut to the Case course →

One payment, lifetime access, 30-day guarantee.