Understanding MBB Consulting Roles in the United States

Recommended resources

The freely available resources this lesson will direct you to.

Hello. In the previous lesson, you saw that consulting creates value by moving a client from an ambiguous problem to a decision, an executable plan, and ultimately measurable results. This lesson asks a practical follow-up question: which kinds of consultants do that work?

At MBB firms—McKinsey, BCG, and Bain—the answer is not simply “strategy consultant.” U.S. offices employ people with different depths of expertise and different points of emphasis in the journey from diagnosis to execution. By the end of this lesson, you should be able to distinguish generalist, digital, specialist, and implementation roles without treating them as rigid or mutually exclusive boxes.

Start with two distinctions: client service and role type

First, distinguish client-facing work from internal firm roles. A cloud engineer, researcher, recruiter, finance professional, or presentation designer can all work at an MBB firm. But not every role is a consulting role serving external clients.

MBB firms also have hybrid teams: research, analytics, knowledge, technology, and other capability groups may build reusable tools internally while contributing expertise directly to client engagements. So, before comparing jobs, ask:

Is this role principally serving clients, the firm internally, or both?

McKinsey’s career guidance provides a useful official map of this distinction, then introduces its client-facing role families.

Picking the right role

Read McKinsey’s career overview to see how a major MBB firm separates client service, internal, and hybrid roles, then describes generalist, practice, implementation, and technology-oriented client roles.

In the “Type of role” section, focus on the distinction between client service and internal or combination roles. Read the client-service description and the surrounding bullets on internal and combination roles. Then move to “Client facing roles.” Read all four role descriptions, from the generalist bullet through the technologist bullet: the four client-facing paths. As you read, identify each role’s source of value: breadth, deep expertise, sustained execution, or technical capability.

The image below is a helpful high-level orientation, but read it carefully. It combines career tracks—traditional consulting versus supporting roles—with seniority—consultant, manager, partner. These are different dimensions. A person may be a digital specialist or implementation consultant and still progress through a seniority ladder.

A high-level consulting career map showing traditional client-service tracks, supporting research and knowledge roles, and the separate seniority progression from consultant to manager to partner.

The four role types: a working taxonomy

The most useful way to compare roles is by asking four questions:

What problem is the person primarily equipped to solve?
How broad or deep is their domain expertise?
What work do they personally perform on a team?
Where do they concentrate in the path from strategy to sustained results?

Role type	Primary orientation	Typical contribution	Usual depth or breadth
Generalist	Broad business problem solving	Frames problems, analyzes evidence, develops recommendations, aligns leaders	Broad across industries and functions
Digital	Technology-enabled business change or technical delivery	Links business value to data, products, software, cloud, design, or AI	Can range from tech-aware consultant to deep technical specialist
Specialist	Deep industry or functional expertise	Brings informed judgment, benchmarks, methods, and targeted analysis	Deep in a practice, function, or sector
Implementation	Execution and value realization	Turns initiatives into operating changes, manages delivery, tracks benefits, develops capability	Deep in transformation, operations, and change execution

This table is a map, not four sealed departments.

For example:

A digital consultant may also be a specialist in cloud architecture.
An implementation consultant may specialize in supply chain or sales transformation.
A generalist team may work on a digital strategy project.
A specialist may contribute only for one critical phase of a broader generalist case.

The central distinction is therefore not prestige or intelligence. It is the combination of expertise, work style, and primary contribution to the client team.

1. Generalist roles: broad problem solving across contexts

A generalist consultant is trained to solve a wide range of business problems rather than being hired initially for one narrow technical domain. They may work across industries—healthcare, consumer, financial services, industrials, public sector—and across functions such as growth, pricing, cost reduction, organization, or corporate strategy.

On one engagement, a generalist might help a consumer company decide which customer segments to prioritize. On the next, they might support a bank considering a new operating model. Their core toolkit is portable:

Framing an ambiguous issue as a decision-focused problem.
Breaking the problem into logical components.
Building and testing hypotheses.
Analyzing financial, operational, customer, and market evidence.
Synthesizing findings into a recommendation.
Communicating with client stakeholders.

This is why generalist consulting is often associated with strategy. However, the terms are not identical.

A generalist may work on a strategy question, but they can also work on transformation, due diligence, pricing, operations, or execution support. Likewise, specialists and digital consultants can do strategy work within their fields. “Generalist” describes the breadth of the role, not a guarantee that every project consists only of high-level planning.

What generalists produce

Generalists often create decision-oriented outputs:

A market-entry recommendation.
A growth plan.
A cost-reduction program.
A portfolio or acquisition assessment.
A transformation roadmap.
A set of initiatives, with expected value, risks, owners, and next steps.

Notice the link to the prior lesson: a slide deck is not the value itself. The generalist’s value lies in improving the client’s decision and helping leadership commit to the actions required.

Who may prefer this path?

Generalist work tends to fit people who want:

Variety across industries and business questions.
A broad grounding in business before choosing a specialty.
Frequent exposure to senior client decisions.
A role centered on structured analysis, synthesis, and communication.

The trade-off is that generalists must become productive in unfamiliar industries quickly. They cannot rely on being the deepest expert in every subject.

2. Specialist roles: depth in an industry, function, or capability

A specialist—often called a practice consultant, expert, or functional/industry consultant—builds deeper expertise in a defined area. That area can be an:

Industry, such as healthcare, private equity, insurance, energy, or consumer products.
Business function, such as operations, marketing and sales, sustainability, procurement, or corporate finance.
Capability, such as pricing, organization design, risk, supply chain, or advanced analytics.

A specialist is not merely someone who has taken an interest in a topic. The role depends on expertise that repeatedly improves client work: understanding the economics, terminology, benchmarks, operating realities, stakeholder landscape, common failure modes, and practical interventions in that domain.

Imagine a hospital system trying to reduce the cost of patient care without lowering quality. A generalist may frame the overall financial and operational problem, identify the largest cost drivers, and coordinate the decision process. A healthcare operations specialist can add detailed knowledge of clinical workflows, staffing models, capacity constraints, reimbursement dynamics, and quality safeguards. The combined team is stronger than either profile alone.

What specialists do differently

The analysis process often looks familiar—interviews, data analysis, hypothesis testing, synthesis—but specialists tend to ask better initial questions within their domain.

For example, a pricing specialist might immediately examine:

List price versus net realized price.
Discounting behavior by customer segment.
Willingness to pay.
Competitive reference prices.
Sales incentives.
Margin effects by product and customer.

A generalist can learn these topics, but the specialist’s advantage is recognizing the important distinctions sooner and knowing which analyses are likely to change the answer.

What a specialist role is not

Do not assume that “specialist” means isolated technical work with little client exposure. Many specialists are deeply client-facing and participate in full consulting engagements. Nor does it necessarily mean the role has narrower advancement opportunities; that varies by firm, office, practice, and position.

The essential trade-off is straightforward:

Generalist: broader exposure and greater early exploration.
Specialist: faster depth and a clearer expertise-based professional identity.

3. Digital roles: business value created through technology, data, product, and design

“Digital” is the broadest and most easily misunderstood category.

A digital role is not automatically a software engineering job, and it is not automatically a generalist strategy role that happens to mention technology. Digital teams exist because many client problems now require capabilities beyond conventional business analysis: building products, modernizing systems, deploying cloud infrastructure, using data and AI, designing customer journeys, automating processes, or changing how technology teams operate.

Within MBB, digital roles can include:

Digital strategy consultants.
Product managers and product owners.
Software, cloud, and data engineers.
Data scientists and machine-learning specialists.
Enterprise architects and cybersecurity experts.
Designers and user-experience researchers.
Agile coaches and delivery leads.
Digital marketing or growth specialists.

This category therefore contains people with very different technical depth.

Two broad digital profiles

It is useful to distinguish two profiles, even though real roles exist on a spectrum.

Technically aware digital consultant

This person translates between business strategy and technology. They may assess a client’s digital maturity, define an AI or technology roadmap, prioritize product investments, establish a target operating model, or help leaders decide which customer journeys to redesign.

They need enough technical fluency to ask credible questions and identify delivery risks. But their main work is often problem framing, prioritization, business-case development, stakeholder alignment, and transformation design.

Technical digital specialist

This person brings a buildable skill set: software development, data engineering, machine learning, cloud architecture, product design, or security, for example. They may design, prototype, develop, test, and deploy an actual solution with the client.

Their client value is not simply “knowing technology.” It is applying technical expertise to a commercial or operational objective, such as increasing conversion, reducing service costs, improving forecasting, shortening cycle time, or modernizing a core platform safely.

A digital project is a team sport

Consider a bank that wants to reduce the cost and abandonment rate of opening a checking account.

A digital engagement might include:

A generalist assessing customer economics, strategic priorities, and expected business impact.
A digital product manager defining the target onboarding journey and product backlog.
A designer researching customer pain points and testing prototypes.
A data specialist identifying abandonment patterns and designing performance metrics.
A software or cloud engineer building integrations and improving the platform.
A risk or banking specialist ensuring that the design meets regulatory and operational requirements.
An implementation lead embedding the new process, training teams, and tracking results.

The point is not that every project uses every role. It is that “digital transformation” is rarely a single job. It is a client problem that often needs a multidisciplinary team.

Digital and implementation can overlap

BCG Platinion is a useful illustration of why digital and implementation are overlapping categories. A technology implementation role may begin by diagnosing an enterprise system, then define a target architecture, and finally support build and deployment. That work is both digital and implementation-oriented.

What is BCG Platinion?

Watch Rocketblocks’ “What is BCG Platinion?” for an illustrative example of a technology-focused implementation engagement. It uses a hypothetical reservation-system problem to distinguish core technology deployment from a high-level strategy project, a data-science project, or a new-venture build.

Watch the reservation example, which explains why an integrated reservation platform is a core technology and architecture problem. Then watch the project phases to see the progression from diagnosing a legacy system through solution design, build, and rollout. Treat the firm-specific labels as examples: structures and names can change, but the distinction between technology strategy, architecture, and technical delivery is the key idea.

4. Implementation roles: making change work in the real organization

An implementation consultant concentrates on turning a chosen direction into durable results. They may join during the strategy phase, but their distinctive role is to help the client carry the work through execution.

This matters because a client can approve an excellent recommendation and still fail to realize the intended value. The new process may not be adopted. The technology may not work reliably. Departments may disagree over ownership. Financial benefits may be claimed but not actually appear in the income statement or cash flow.

Implementation consultants help close that gap.

Typical implementation work

Depending on the project, implementation work can include:

Converting a recommendation into initiatives, milestones, owners, and dependencies.
Establishing a program-management or transformation office.
Redesigning operational processes and roles.
Supporting frontline adoption and change management.
Training managers and teams.
Identifying and resolving delivery risks.
Creating performance dashboards and benefit-tracking routines.
Ensuring that finance validates realized value.
Building client capabilities so the result lasts after the consulting team leaves.

Their work can be analytical. For example, a transformation lead may need to quantify savings, model staffing requirements, prioritize initiatives, or diagnose why a program is behind schedule. The difference is the purpose of the analysis: it is directly tied to delivery, adoption, and value capture.

The following comparison is useful, but intentionally simplified. It contrasts the dominant emphasis of a strategy-oriented generalist engagement with an implementation-oriented role. In practice, MBB teams often combine both.

Strategy Consulting vs Implementation Consulting (Differences Explained)

Watch My Consulting Offer’s “Strategy Consulting vs Implementation Consulting” for a straightforward contrast between decision design and execution support. Use it to reinforce the distinction, while remembering that generalist consultants can also support implementation and that implementation roles differ across firms.

Watch the work comparison for the coffee-chain example contrasting a strategic redesign with the work of deploying it in stores. Then watch the hiring contrast, focusing on why implementation positions often value demonstrated industry or transformation experience. The “strategy equals deck” framing is deliberately simplified: as the previous lesson showed, effective consulting connects recommendations to action and measured impact.

Implementation is not “less strategic”

It is tempting to picture strategy as intellectually demanding and implementation as operational follow-through. That distinction is misleading.

Implementation roles involve hard strategic choices all the time:

Which initiatives should be sequenced first?
Which benefits are credible enough to include in the business case?
How should leaders allocate scarce technology and operational resources?
What trade-offs preserve customer experience while reducing cost?
Which capabilities must be built rather than outsourced?
When should the organization adjust the original plan because evidence has changed?

The role simply places more weight on what happens after the decision: whether the organization can execute, realize, and sustain the intended outcome.

One client problem, four possible contributions

To make the differences concrete, imagine a U.S. retailer whose profits are declining and whose online shopping experience is weak.

The CEO asks: “How can we restore profit growth while improving the customer experience?”

A single MBB engagement might involve all four role types:

Role	Contribution to the retailer’s problem
Generalist	Structures the profit problem, tests revenue and cost hypotheses, evaluates strategic options, and synthesizes a recommendation for leadership.
Specialist	Brings retail, merchandising, pricing, supply-chain, or customer-loyalty expertise; identifies relevant benchmarks and practical industry constraints.
Digital	Redesigns e-commerce journeys, assesses data and platform gaps, prioritizes technology investments, or builds relevant products and analytics.
Implementation	Establishes initiative owners and milestones, supports store and digital-team adoption, resolves delivery issues, and tracks whether margin improvement is realized.

These roles should not be imagined as a sequence in which one group disappears before the next arrives. The specialist may shape the original diagnosis. The implementation lead may challenge an impractical strategy early. Digital experts may help estimate what is technically feasible before leaders select an option.

That is consistent with the value-creation model from the prior lesson: diagnosis, decision, installation, realization, and repeatability must stay connected.

How to interpret a U.S. job posting

Firm branding changes frequently. One firm may use “consultant,” another “associate,” “expert,” “implementation coach,” “product manager,” “technology architect,” or “data scientist.” Do not decide what a role is based on the title alone.

Instead, inspect the job description for five signals.

1. What is the stated client problem?

Look for the central object of the work:

Broad strategy, growth, performance, or transformation questions often signal a generalist role.
A defined industry or capability focus signals a specialist role.
Products, cloud, data, architecture, AI, design, or engineering signal a digital role.
Program delivery, adoption, transformation management, operational improvement, or benefit realization signal implementation.

2. What expertise is required on day one?

A role asking for evidence of software delivery, architecture, data science, product design, or domain-specific operations experience is not just a generalist role with a different label.

3. What will you actually do?

Pay particular attention to verbs:

Frame, analyze, synthesize, recommend often point toward generalist consulting.
Advise, benchmark, diagnose, design in a domain often point toward specialist work.
Build, architect, prototype, deploy, engineer often point toward a technical digital role.
Mobilize, implement, coach, manage, track, sustain often point toward implementation.

4. How is success measured?

Generalist roles may be evaluated heavily on quality of problem solving and client recommendations. Digital roles may be assessed through product performance, system delivery, or adoption. Implementation roles often emphasize operational KPIs, financial benefit realization, and the client’s ability to sustain changes.

5. What staffing model does the role imply?

Some roles rotate across cases and industries. Others are affiliated with a specific practice. Some operate in multidisciplinary product squads. Others spend longer periods embedded with a client transformation program. This affects daily work as much as the formal job title.

Choosing a direction: a practical first filter

Without assuming one path is universally better, you can use the following questions to identify an initial direction.

If you most want to...	A plausible starting direction
Explore industries and business problems before specializing	Generalist
Become recognized for deep expertise in a sector or function	Specialist
Combine business work with product, data, design, engineering, or technology architecture	Digital
Stay close to operational change and see initiatives through to measurable results	Implementation

There is also room for movement. Generalists often develop practice affiliations over time. Industry experts can broaden into general management work. Technologists can move into product or digital strategy leadership. Implementation professionals can build broad transformation leadership skills.

Still, it is important not to assume every move is automatic. Direct-entry roles, especially technical digital and implementation positions, usually expect evidence that you can already perform some of the role’s distinctive work.

For now, the most important outcome is clarity: choose the role based on the work you want to do repeatedly, the expertise you want to build, and the client value you want to own.

Key takeaways

MBB firms in the United States use varying names and structures, but the four categories can be distinguished clearly:

Generalists solve a broad range of business problems across industries and functions.
Specialists contribute deep industry, functional, or capability expertise.
Digital professionals connect business objectives with technology, data, design, products, and technical delivery; technical depth varies substantially by role.
Implementation consultants help clients convert plans into adopted changes, realized benefits, and lasting capabilities.
These are overlapping dimensions, not a strict hierarchy. A digital architect may be doing implementation; an implementation lead may be a supply-chain specialist; a generalist may work on a digital transformation.
Read job descriptions for the actual work, skills, measures of success, and staffing model—not just the title.

In the next lesson, you will compare direct-entry recruiting routes for experienced software engineers. The distinction between digital, specialist, implementation, and generalist work will become the basis for evaluating which paths match a candidate’s evidence, timing, and eligibility.