McKinsey Hours: The Honest Read

A first-year Business Analyst at McKinsey typically works 55 to 65 hours a week on a client project. That's the range Hacking the Case Interview gives for McKinsey's Business Analysts, the role McKinsey hires undergraduates into, and the same range StrategyCase, run by a former McKinsey consultant, gives for that level. First-year analysts at McKinsey, BCG, and Bain report averaging about 60 hours in Glassdoor reviews, according to Hacking the Case Interview.

I'm Stephen Turban, founder of WSG and a McKinsey & Company and Harvard alum. I went through McKinsey's on-cycle recruiting myself, and I've since guided dozens of students through it.

Long hours are easier to weigh once you know what they pay, so see the full McKinsey compensation breakdown from Business Analyst to Partner here. The Business Analyst seat is where most undergrads start, and what that job actually involves is covered here.

How the Hours Change From Week to Week

A year at McKinsey is mostly project weeks, with crunch weeks and quieter stretches mixed in. Most project weeks land near 60 hours, crunch weeks before a big client presentation or deal deadline reach 70 to 80 or more, and weeks between projects fall to around 40.

Crunch weeks: 70 to 80 hours or more. Hacking the Case Interview's author, a former Bain manager, writes on the site's work-life balance page that the weeks that hit 70 or more came around client board presentations and tight due diligence timelines.

Between projects: 30 to 40 hours on that page, and 30 to 60 with an average in the low 40s on StrategyCase. These weeks go to proposals, recruiting, training, and internal work, and there aren't many of them: StrategyCase puts junior consultants' utilization, the share of their time billed to clients, at roughly 80 to 95 percent.

By office: Hours at McKinsey, BCG, and Bain are generally at the higher end of the range in the US. Former consultants in New York and Dallas report 60 to 65 hours, and offices such as Amsterdam and Zurich report closer to 50 to 55, according to Hacking the Case Interview's hours page.

Higher estimates you'll see: Hacking the Case Interview's McKinsey page gives a general figure of about 60 to 70 hours a week for McKinsey consultants while staffed, above the 55 to 65 it gives Business Analysts on the same page. CaseCoach puts a standard week at the top strategy firms at 70 to 75 hours, because it counts lunch and travel time.

What a McKinsey Project Week Looks Like

The longest days are the ones at the client site, often 10 to 16 hours with the evening spent on slides, while Friday at the home office is a shorter day of 6 to 8 hours. The traditional consulting week has you at the client Monday through Thursday and back at your home office on Friday, and the hours fall like this:

The long days come Monday through Wednesday, while Thursday and Friday are shorter and the weekend is mostly off.

StrategyCase lays that week out day by day, with what fills each day:

Day	What happens	Hours
Monday	Leave home around 5:30 a.m. for a 7 a.m. flight, then a full day at the client	10 to 16
Tuesday and Wednesday	Client work by day, then slides and analysis in the evening, often until around midnight	10 to 16
Thursday	Work from 9 a.m. until about 5 p.m., then fly home, landing between 8 and 11 p.m.	About 8, plus the flight
Friday	Home office, finishing around 5 or 6 p.m.	6 to 8
Weekend	Usually off; many consultants choose to spend an hour or two on Sunday evening getting organized for the week	0 to 2

Sources: StrategyCase (July 2026) for the day-by-day pattern and the Monday to Wednesday hours; Hacking the Case Interview (May 2026) for the Friday and Sunday hours. Hacking the Case Interview counts every Monday to Thursday client day at 12 to 14 hours, so Thursday can run longer than StrategyCase's version.

Fewer teams fly out every Monday now. StrategyCase says most McKinsey teams travel two to three days a week, so on the other days you're working from the office or home. Hacking the Case Interview's schedule for a standard week on an active MBB project, based on its author's experience at Bain, starts a client day with a team standup at 8 a.m. and analysis, modeling, and slides until lunch. Client meetings, interviews, and workshops fill the afternoon, and synthesizing findings and preparing for the next day run until dinner. The evening session, from 8 to 10 p.m., goes to polishing slides and responding to partner feedback.

What Pushes a Week Up or Down

The type of project, how close you are to a major client meeting, and your engagement manager and client decide whether a week lands near 55 hours or climbs past 70.

Project type: Short, intense projects run the longest days. A due diligence, where the team assesses a company for an investor before a deal, often runs 2 to 4 weeks, and a PrepLounge coach who worked at McKinsey puts those at more than 12 hours a day. Implementation projects, where the team works alongside the client to put a plan in place over several months, run closer to 8 to 10 hours a day. Long strategy projects of 3 to 6 months tend to have more predictable, moderate hours, according to Hacking the Case Interview's hours page.

Project phase: The final two weeks before a major deliverable are the crunch, according to Hacking the Case Interview's work-life balance page. Each steering committee meeting, where the team updates the client's senior executives, brings its own run-up too, and StrategyCase calls that usually the most stressful stretch of the cycle.

Your engagement manager: StrategyCase's McKinsey page says, "The single biggest determinant of your hours is not McKinsey, it is your engagement manager and your client." The engagement manager (EM) leads the day-to-day execution of the project, according to McKinsey's own EM posting. On the work-life balance page, Hacking the Case Interview's author writes that teams whose managers set norms early, such as no emails after 9 p.m. or one meeting-free evening a week, had much better balance.

Your client: StrategyCase lists demanding, political, or ex-consultant clients among the things that push hours up, and notes that more senior partners on a project often means more conflicting demands and longer hours.

How Travel Adds to Your Hours

Flying out Monday morning and home Thursday evening adds 6 to 10 hours of travel a week on top of your working hours, and how often your team flies depends mostly on the client. That's Hacking the Case Interview's count for the traditional travel week, when you're on site four days.

Teams on site two or three days a week spend fewer nights away, but no published estimate gives their travel hours.

McKinsey's careers blog said in 2019 that teams now "evaluate the best working model for their engagement before beginning work," and StrategyCase's 2026 view is that your client, more than any firm rule, decides how much you travel.

Do McKinsey Consultants Work Weekends?

Weekends at McKinsey are usually protected, and weekend work tends to come in crunch weeks such as the run-up to a steering committee or a short due diligence.

Hacking the Case Interview's hours page says former McKinsey and Bain consultants describe weekend work as a last resort, and its work-life balance page cites Vault's 2026 survey, in which a majority of MBB consultants reported working weekends fewer than once a month. StrategyCase calls weekends "mostly protected in practice" and says a bad week before a steering committee might take part of a Sunday. The PrepLounge coach writes of never working a single weekend at McKinsey, which is one person's experience. The long hours go into weeknights instead.

Has AI Changed McKinsey Hours?

AI tools now do much of the research and first-draft work that junior consultants used to do, but the hour estimates published in 2026 don't report a shorter week as a result.

McKinsey's internal AI tool, Lilli, searches and summarizes the firm's past work, and more than 75 percent of McKinsey's employees were using it monthly by June 2025, according to Fortune. In a January 2026 report on CEO Bob Sternfels's remarks at CES, Inc. wrote that McKinsey saved 1.5 million hours the year before by using AI for search and synthesis. StrategyCase's McKinsey page says AI absorbed the research and first-draft work that used to be the junior consultant's apprenticeship, and it still describes a normal week at McKinsey as roughly 55 to 70 hours.

How McKinsey Teams Set Working Norms

McKinsey's careers blog describes teams agreeing on working norms at a kickoff called a team learning, which gives you a set moment to ask for the evening or commitment you need to protect.

In a 2019 post, it said every engagement kicks off with a team learning, where the team sets its norms, the rules it agrees to work by. Teams also fill out an anonymous survey every other week, which asks, among other things, "Are we adhering to the norms we set in the team learning?" A norm can be as simple as an hour off in the evening for dinner or the gym, which Hacking the Case Interview's McKinsey page says many teams now support as long as the work gets done. The survey is your second chance to speak up, when you can say which nights a week went wrong. Hacking the Case Interview's work-life balance page adds that McKinsey monitors hours through internal tracking systems and penalizes managers and partners who consistently overwork their teams.

When you talk to current Business Analysts while recruiting, ask how many nights they were away last month and what their last team's norms looked like. Those two answers give you a realistic read on the office's current travel and team habits.

How McKinsey Hours Compare With Investment Banking

A McKinsey Business Analyst's typical week of 55 to 65 hours is shorter than the 70 to 80 hours or more that most investment banking analysts spend in the office, and consultants' weekends are more often protected. Mergers & Inquisitions puts most banking analysts in the office at least 70 to 80 hours a week, with some weekend work and busy weeks that can pass 100 hours. A consultant's travel time, though, comes on top of the 55 to 65.