This guide is designed for practical use. You will look up a title, decide whether a candidate is a fit, and translate seniority across firms—often quickly. The fastest way to make a mistake is to anchor on the label and assume it means the same thing everywhere. The role profiles in this guide are built to prevent that by describing jobs in a consistent, structured way.
2.1 The Nine-Field Role Template
Every role profile uses the same nine fields. Think of the template as a translation tool: it separates the title (a local naming convention) from the role (scope, authority, and outcomes). Read the fields in sequence. Each field narrows what the title can realistically mean.
Title: The label the firm uses for the role. Treat it as an index entry, not a conclusion. The same word can represent different seniority bands across firms. Even within one firm, the same word can mean different things in a strategy group versus a technology delivery unit. The title tells you where to start, not where to end.
Client-facing: Whether the role regularly interacts with client stakeholders. The guide uses Yes, Sometimes, and No. “Sometimes” is common for specialists who join key workshops, for knowledge roles that brief teams, and for internal roles that become client-adjacent during proposals or governance. This field matters because stakeholder exposure increases decision risk, and decision risk is a strong proxy for level.
Geography: Whether the title is used globally or is specific to a region or country. Global titles are more likely to be stable rungs, though responsibilities can still stretch by market. Region-specific titles are often local translations, bridge bands, or compressed ladders. Geography is also a warning that a familiar title may be used differently because of local labor market norms.
Business unit: Where the role sits inside the firm. This is one of the most important fields. Many firms run multiple ladders under one brand: core consulting, analytics, digital studios, engineering, implementation, managed services, and specialist practices. A title can only be interpreted correctly inside its ladder. When a business unit is specified, treat it as part of the title.
Typical degree required: The most common education credential at entry. This is a hiring pattern, not a strict gate and not a quality judgment. It helps you infer the intended entry point in the ladder (undergraduate, post-MBA, advanced degree, or technical master’s). It also signals where clients and regulators expect credentials (for example, actuarial or economics work).
Typical work experience when starting this role: Common prior roles and years of experience at entry. This field is your fastest validator when titles are ambiguous. A “Consultant” that starts at 0–2 years is not the same as a “Consultant” that starts post-MBA. A “Senior Consultant” that starts at 3–6 years is not the same as a “Senior Consultant” that starts at 8–12 years. When leveling a lateral hire, this field often matters more than the word in the title.
Plain-language description: What the role actually does. This field should reveal day-to-day responsibilities, decision rights, and typical outputs. If the title suggests one level but the description suggests another, the description wins. It is also the best place to detect whether the role is advisory, build-and-deliver, implementation-heavy, or internal enablement.
Typical duration in role: How long people usually hold the title. Short durations often indicate an apprenticeship ladder with frequent promotion reviews. Longer durations often indicate broad bands where growth is expressed through scope expansion rather than title changes. Indefinite durations often signal senior career bands where progression is measured by portfolio size, authority, or commercial contribution.
Typical next role(s): The most common progression paths inside the firm. This field tells you which ladder the role sits on and whether it is a bridge band, a feeder role, or a long-tenure destination. It is also the clearest signal of whether the role is generalist, specialist, digital, delivery, or internal.
A practical reading order helps you avoid anchoring on the label. Business unit: identify the ladder. Client-facing: estimate stakeholder exposure. Typical experience: estimate the band. Description: validate ownership. Next role(s): validate trajectory. Title: interpret last.
When the fields conflict, don’t force a mapping. Use the profile to ask targeted clarifying questions. Three questions resolve most ambiguity.
- Scope: What is the biggest piece of work you personally owned end-to-end?
- Authority: What decisions could you make without escalation?
- Outcomes: How was your success evaluated in that role?
If those answers align with the profile’s typical experience and next roles, you can translate the title with confidence. If they don’t, you have learned something more valuable than a title: you have learned how the role actually behaved.
2.2 Understanding Regional and Business-Unit Specific Titles
Most title confusion comes from two forces: regional variation and business-unit variation. Regional variation happens when firms adapt titles to local labor market norms and hiring channels. Business-unit variation happens when firms operate multiple ladders under one brand. In both cases, translation works the same way: map the job first, then map the title.
Regional variants are most common in the middle of the ladder. Entry and partner labels are often more stable. The “messy middle” includes Senior Consultant, Senior Associate, Associate Consultant, and Director, because firms use these labels differently to fit local promotion structures.
When a title is region-specific, it is usually one of three things. Local norm alignment: a label chosen to match the local market vocabulary. Bridge band: a transitional rung inserted between two broader levels. Ladder compression: a broader band used because the region has fewer formal levels. You can usually identify which one applies by reading Typical duration in role and Typical next role(s). Bridge bands tend to be shorter and point to one obvious next role. Compressed ladders tend to show wider experience ranges and broader descriptions.
Business-unit specific titles can differ even more than regional titles. A firm may have a classic consulting ladder and, in parallel, a digital studio ladder using Product Manager and Design Lead. It may also have analytics and engineering ladders using Data Scientist, Data Engineer, and Architect, plus implementation ladders using Program Lead and Transformation Lead. The visible labels differ because the work differs.
To interpret a unit-specific title, answer three questions. Delivery mode: is the unit advisory, build, implement, or operate? Evaluation system: is performance judged by insight quality, production delivery, adoption, or revenue? Career endpoints: does the track lead to partner-equivalent roles, senior specialist leadership, or both? Once you know the answers, translate the role using scope and accountability rather than vocabulary.
Some titles are repeat offenders because they are used inconsistently. These “trap titles” should trigger extra validation.
- Associate: Entry level at some firms, post-graduate at others.
- Consultant: Entry level at some firms, mid-level at others.
- Senior Consultant: Pre-manager at some ladders, project lead in some delivery units.
- Director: Partner-track at many firms, senior non-partner at others, senior individual contributor in some studios.
- Managing Director: Partner-equivalent in some firms, senior non-equity leadership in others.
When you see a trap title, rely on three alternative signals. Client counterpart: who they regularly work with on the client side. Leverage: how many people they lead, and whether they lead through other leaders. Commercial contribution: whether they originate work, expand accounts, or primarily deliver sold work. These signals travel across firms more reliably than labels.
One final nuance: even “global” titles can stretch by region because of staffing realities. In a lean office, people may carry broader responsibility at the same title. Treat this as stretch in scope, not a different rung, and calibrate the person’s first assignment in the receiving organization accordingly.
2.3 Typical Education and Experience Patterns by Level
Education and prior experience patterns are entry ramps into a ladder, not status markers. Firms hire from multiple channels to meet demand and to bring different kinds of credibility to clients. Use these patterns to infer what the firm expected on day one, then validate with evidence of what the person actually owned.
Entry band: Most commonly bachelor’s hires and early-career hires. The expectation is rapid learning, clean analysis, and visible improvement through feedback. In technical units, specialized master’s graduates may enter at equivalent entry bands, but the evaluation still emphasizes reliability, clarity, and coachability.
Core consultant band: A mix of promoted entry hires, post-MBA hires, advanced-degree hires, and experienced hires. Post-MBA and advanced-degree hires are typically expected to own modules quickly, manage stakeholders, and contribute to storylines with less ramp time. Experienced industry hires can enter here when they bring relevant functional depth and can demonstrate structured problem solving and client-ready communication.
Project leader band: Primarily internal promotions, plus selective experienced hires. The defining expectation is end-to-end delivery leadership. This includes planning discipline, team leadership, and day-to-day client management. Industry hires can enter here when they have led complex programs, handled stakeholder conflict, and delivered measurable outcomes under constraints.
Senior leader and partner-track bands: Multiple routes with weaker education patterns. At these levels, track record dominates. Generalists are evaluated heavily on relationship leadership, commercial contribution, and the ability to scale through other leaders. Specialists are evaluated heavily on domain authority, asset building, and client pull.
Some practices are credential-driven by necessity. Actuarial, economics, and certain regulatory specialties value credentials because external credibility and defensibility matter. In those practices, degree and certification patterns tell you something real about the market’s requirements, not just the firm’s preferences.
Digital and data roles introduce a different kind of evidence: portfolios and production experience. Seniority is often revealed by the ability to design systems, manage trade-offs, operationalize models, and communicate risks to non-technical stakeholders. Degree still matters, but it is less predictive than demonstrated delivery outcomes.
A simple validation question works across channels: “What were you expected to own when you started the role, and what did you own by the time you left it?” The delta in scope and authority is the real level signal. Titles and degrees provide context for that story.
2.4 Promotion Timelines and “Up or Out” vs. Alternative Paths
Promotion systems shape how titles are used and how long people hold them. Some firms run rapid early promotions with clear apprenticeship expectations. Others use broad bands where growth is expressed through increasing scope and influence rather than title changes. Most modern firms are hybrids, especially as they add specialist, digital, and implementation tracks.
Up or out: a model where advancement within an expected time window is strongly encouraged. In strict forms, failing to advance can trigger an exit expectation. In softer forms, top performers advance quickly while others plateau and later exit or shift tracks. The key nuance is that “up or out” is rarely uniform across all business units. Expert, digital, and delivery organizations often have more varied progression paths than classic generalist ladders.
Promotion timing is most structured in the early and middle ladder. That is why the profiles include Typical duration in role. Duration helps you interpret tenure. A long tenure at one title can signal stalling in a fast-promotion environment and can be normal in a broad-band environment. Without duration context, resumes are easy to misread.
Across firms, promotion decisions usually blend four categories. Client impact: did the work change outcomes. Problem solving: did the person structure ambiguity and produce clear decisions. Leadership: did the person lead teams and develop others. Commercial contribution: did the person strengthen relationships and create demand. The weights shift by level. Junior roles emphasize quality, speed, and growth. Project leaders emphasize delivery ownership and stakeholder management. Senior leaders emphasize leverage and commercial outcomes.
Alternative paths are now mainstream because consulting includes multiple crafts. Expert tracks reward domain authority and reusable intellectual property. Data and engineering tracks reward production quality, architecture decisions, and reliability. Product and design tracks reward adoption, user outcomes, and roadmap leadership. Transformation tracks reward change adoption and benefits realization. These tracks can lead to senior leadership, but the evidence required for promotion differs from the classic generalist story.
When you translate a role, translate the promotion model too. A candidate moving from a fast-promotion ladder into a broad-band ladder may feel stalled unless expectations are explicit. A candidate moving the other way may feel overwhelmed if the receiving firm assumes a polished storyline and high-tempo delivery immediately. Use the profile’s Typical duration and Next role(s) to set expectations on pace and progression.
A reliable way to prevent title mismatch is to define the role in three lines before finalizing a level. First assignment: the type of work and what the person will own. Success metrics: what good looks like in the first 90 days. Review timing: when level will be reassessed if performance is strong. When those are clear, the title becomes a label for a known job, not a guess about status.
