How to Prep for McKinsey Knowledge Analyst as an Ex Engineer

Hi,

The first thing I would say is that I would not overthink trying to replicate the job before you start. The real working environment is very difficult to reproduce from the outside, especially in terms of intensity, pace, pressure, and the type of requests you will receive. And even where you can replicate parts of the job, the learning curve inside McKinsey will be incomparably faster, something that might take you weeks to figure out on your own could easily become clear within a day once you are working with the right people, tools, and feedback.

That said, there are still a few things you can do beforehand to arrive with a solid foundation:

1. Tools
Excel and PowerPoint are the obvious ones, and it is definitely worth being comfortable with both. You do not need to be an expert, but the less time you lose on basic tasks, the more you can focus on the actual content.

2. Industry knowledge
If Knowledge Analysts in your region tend to be relatively specialized by industry, I would try to build some general knowledge around the sectors you are most likely to cover. Books, industry reports, specialist publications, and annual reports can all help. The goal is not to memorize facts, but to make sure that once you start, everything does not feel completely new.

3. Synthesis of information
This is probably one of the most useful things you can practice before joining. Pick a topic you are genuinely interested in and take a long document or report with a lot of information. Then force yourself to reduce it to:

• 3–5 key messages
• the most important data supporting those messages
• a clear way of structuring it on a slide if needed
• and a 60–90 second verbal summary for someone who has not read the document

You can even explain it to a friend or family member and see whether, after a short explanation, they understand what really matters and why it matters.

For this type of role, a lot of the value comes from being able to extract the important points quickly and make them useful for consultants and engagement managers.

Best,
Carlos

Hi there,

MOST IMPORTANTLY: Know that no one can perfectly prepare for the job and that's the point: You will mess up, you will learn, you will be trained and supported. That's OK!

In terms of things you can learn and do to prepare beforehand:

1. Daily reading

The Economist, The Financial Times, BCG and McKinsey Insights

2. Industry deep dives

Learn, in depth, how the industries and companies your office advises work.

3. Analytics tools

Alteryx, Tableau, etc.

4. Excel

5. PowerPoint

Best practices and standards, different layouts, quickly editing and updating slides, and thinking in PowerPoint.

6. Presentation skills and sharp communication

There are some online and virtual classes for this.

In terms of doing well in your role when you're there:

1. Understand the context and prompt: what role are you in, what company, who's watching, etc.

2. Understand the objective: what, specifically, is expected from you, both day to day and in your overall career progression.

3. Quickly process information and focus on what's important. Take a lot of information and the unknown, find the most logical path, and focus on that.

4. Be comfortable with the unknown and learn to brainstorm. Think and speak like an expert without being one.

In summary, there will always be a flood of information, expectations, competition, etc. and not enough time. Find out which ones matter when. In other words, be visible and focus your efforts on the things people care about.

Based on what you've posted, read my Consulting Survival Guide for practical guidance on succeeding once you start. For a sustainable way to keep developing your business knowledge, I also recommend the Consulting Offer Blueprint podcast.

Hi there,

The list you have been handed is a generalist consultant's list, and that is not the job you are starting. Excel, PowerPoint and daily reading will make you a competent consultant. They will not make you a good Knowledge Analyst, because a knowledge role is usually judged on turnaround and reliability across several teams, rather than on depth within one.

• Declare a specialism rather than close a gap. Your field engineering background is the most useful thing you arrive with, not the thing to compensate for. The analysts who get pulled onto the work they want are the ones a partner can name a subject for.
• Practice the shape of the job, not the tools. Take a question a team might plausibly send you, give yourself 45 minutes, and produce the answer with sources attached. Do that 10 times before you start and you will have built the muscle the role actually uses.
• Build your retrieval stack in week 1. Where the internal material lives, who owns it, and your own external sources by topic. The gap between a fast analyst and a slow one is almost never analytical ability, it is knowing where to look.

I would resist the instinct to prove you can do a consultant's job. What works in these roles is becoming the person a team calls first, and that reputation is built on being fast and right on narrow questions rather than on producing the most complete answer.

hey there :)

honestly, your engineering background is a great fit for a Knowledge Analyst role. I’d add one important thing to your list: get very good at turning complex technical information into a clear business story. You’ll likely spend a lot of time researching, synthesizing information, speaking with experts and translating your findings into something senior stakeholders can actually use.

I’d also familiarize yourself with McKinsey’s typical problem solving approach and practice answering ambiguous questions with a clear hypothesis and recommendation. Excel and PowerPoint are definitely worth improving, but I wouldn’t overfocus on them before your start.

And don’t worry about becoming a “consultant” beforehand. Your technical expertise is exactly what you’re bringing to the role.

If you have more questions about the transition from engineering into McKinsey, happy to help!

best,
Alessa :)

Since you have already identified Excel, PowerPoint, daily reading and soft skills, I would spend most of your remaining preparation on turning research into an answer someone can use.

Once a day, choose a company or sector relevant to MENA. In 45 minutes, produce three things: the question you are answering, three evidence-backed insights, and a one-slide or one-page summary with a clear implication. Then explain it aloud in 60 seconds.

Also practise scoping requests. Before starting, ask what decision the team is supporting, who will use the work, how precise it needs to be, and when it is due. That matters because a strong Knowledge Analyst does more than find information; they make it useful quickly.

Your engineering background is an advantage if you translate technical detail into business meaning. You do not need to arrive as a finished consultant.