Tech Consulting 2026: The Work, the Names, the Two Doors

What tech consulting is, and what the work consists of

Tech consulting is the part of consulting that does not stop at the recommendation. A strategy engagement ends when the decision is made. A tech consulting engagement usually begins there and runs through specifying, building, integrating and then operating whatever the decision implied.

The clearest published account of the daily content comes from a candidate rather than a firm. In an r/consulting thread of 26 August 2015, a consultant starting at a firm that described itself as a management consultancy listed the work he had been told to expect: "requirements elicitation, process design, business case development, use case development, options analysis, functional specification, feasibility studies". He posted it to ask the forum which job that actually was.

Read that list for its shape. Two of the seven items are recognizably strategy work, the business case and the options analysis. The other five are the specification of a system: what it must do, who does what around it, and whether it can be built at all. That is one person's account of one firm in 2015, and it is an anecdote rather than a job description, but it is the only itemized list of the work that anybody in our reading has published.

The technical content sits beside that rather than inside it. A second candidate in a thread of 19 August 2015 described the technical component of his own interview as "simple stuff like difference between black box and white box testing, overloading vs overriding, and some basic object oriented design principles". Both accounts are old and both are individual. What they establish is that the technical bar in a consulting interview was set at the level of a conversation rather than a coding test, at least at one firm in one year.

Which tech consulting firms publish which practice name

Here is the single most useful fact on this page for anybody searching the term. Not one firm we read calls its practice IT consulting, and only one of the three uses the word technology in the name at all.

Three firms, three vocabularies, and the term that brought you here appears in none of them. That has a direct cost: searching a firm's own site for IT consulting returns nothing, and people conclude the practice does not exist when it is sitting there under a name they did not search for. The same gap catches anyone who arrives from a list of tech consulting companies and then tries to find the matching job family on the firm's own careers site, because the list and the firm are using different words for the same practice.

The Accenture row carries the trap worth memorizing, because two pages with near-identical names describe different things. High Tech is an industry, meaning who the client is. Technology Strategy and Consulting is a service, meaning what the work is. A semiconductor company is the first; rebuilding its order system is the second. So Accenture tech consulting has two front doors with near-identical names, and only one of them is a job family. The section below on where openings hide works that distinction through.

The mapping for the rest of the market, with the practice name each of thirteen firms publishes, sits on our list of technology practices.

Two recruiting architectures, and they are opposites

McKinsey and BCG have taken opposite decisions here, and both publish theirs.

McKinsey runs one door. Its careers FAQ, checked 30 September 2026, states it in the firm's own words: "Please note, there is a single application portal that accommodates both generalist and specific practice preferences. You can list up to three office or practice preferences with your application." The same page sets the default: "Most new consultants begin their careers as generalists, working across a variety of industries and functions. Alternatively, some may join as practice consultants, focusing on a specific function or sector."

So at McKinsey the technology route is a preference inside a generalist application. You do not choose a different process. You spend one of three preference slots.

BCG runs a second entity. BCG Platinion has its own domain, its own careers section and its own application process, and the titles it hires into are named differently: "AI Tech Architect" and "AI Tech Consultant". A candidate who wants BCG's technology work and applies to the BCG Consultant posting has applied for a different job at a different legal entity.

Two firms, two architectures, and the same candidate has to make a different move at each one.

What the published technology process actually asks for

BCG Platinion's application process page, checked 30 September 2026, is the one technology process we could read end to end. It is worth quoting because it names things no strategy process page names.

The shape first: "Our application process consists of a minimum two rounds of interviews, including case studies." Then the documents: "Apply by sending your CV including a list of projects, and, if available, references and transcripts."

A list of projects is the tell. A strategy application asks what you did and what happened. This one asks what you built, itemized. If your record is delivery work, that instruction is an advantage, and it is the single cheapest piece of preparation on this page: write the list before you need it.

Then the assessment: "For client-facing positions, we'll also assess your problem-solving and analytical skills, as well as your IT skills, offering the necessary support and resources to help you prepare effectively for the interview."

The round contents, as the firm lays them out:

1. Round one, part one. Job profile, motivation and consulting life.
2. Round one, part two. A case study "to show analytical, qualitative, technical and presentation skills".
3. Round two, part one. Discussion of open questions left over from round one.
4. Round two, part two. A case study similar to round one.
5. Round two, part three. One interview with a BCG Platinion or BCG Director.

Four of those five words on the case, analytical, qualitative, technical and presentation, appear together in no strategy process we have read. Two of them, technical and presentation, are the difference. Our page on the BCG Platinion case interview works one of these through with the arithmetic shown.

Half of Accenture is delivery, in audited numbers

"Advice plus delivery" is a phrase everyone uses and nobody sizes. Accenture sizes it every quarter, because it has to file.

The 8-K exhibit for the quarter ended 31 May 2026, checked 30 September 2026, carries a table headed TYPE OF WORK, in thousands of dollars. For the quarter: Consulting 9,328,494 and Managed Services 9,389,650, against total revenue of 18,718,144. Add the two and you get the total exactly.

Work the share by hand. Half of 18,718,144 is 9,359,072. Managed Services exceeds that by 30,578, which is 0.16% of the total, so Managed Services is 50.2% of quarterly revenue and Consulting is 49.8%.

The nine month figures say the same thing with less noise: Consulting 27,602,702 and Managed Services 27,901,632, total 55,504,334. Half of the total is 27,752,167; Managed Services runs 149,465 above it, which is 0.27%, giving 50.3% against 49.7%.

Two cautions, both necessary. Accenture defines "Consulting" as an accounting category of its own, and that category is wider than strategy work. And no strategy firm publishes a comparable split, because McKinsey, BCG and Bain publish no revenue at all, so the symmetrical comparison cannot be made.

One more line from the same filing points the other way. New bookings for the quarter were Consulting 10.26 billion dollars and Managed Services 9.06 billion. Those sum to 19.32 billion, and 10.26 divided by 19.32 is 53.1%, so signed work in that quarter leaned back toward the advisory category by about three points against revenue. Bookings and revenue measure different things over different horizons, and one quarter is one quarter.

Where the opening hides, industry page or service page

This costs people interviews, and it is pure navigation. Accenture publishes an industry called High Tech and a service called Technology Strategy and Consulting, and they are different things under similar names. The industry page, checked 29 September 2026, names five client segments it supports: Enterprise technology, Consumer technology, Network equipment, Semiconductors, Medical equipment. Those describe who the client is. The service page describes what the work is.

Deloitte does something else again. Its consulting catalog, checked 29 September 2026, names AI and Engineering, Cyber and Enterprise Performance as its technology entries, and the phrase "IT consulting" appears nowhere in it. Searching a firm's site for the term you learned from a search engine returns nothing, and people conclude the practice does not exist.

The practical rule that follows: search the firm's own job board by the title it publishes, then check whether the page you landed on describes a client industry or a service line. Our list of the technology practices thirteen firms publish holds the mapping for the rest of them.

What two candidates reported about a technology interview

No firm we read publishes a technical interview for a consulting role. Candidates describe one. The accounts below were read on 30 September 2026 in the Discussions blocks a search engine renders for Reddit threads, because reddit.com returns 403 to our requests and the text proxy is blocked too. They are individual accounts, they are dated, and they are old.

In an r/consulting thread of 19 August 2015, a candidate who had gone through Big Four technology consulting recruiting wrote: "For tech consulting, I just used the cases the tech firms have on their websites. I found that to be fairly representative. There was not an underlying structure as you would think of in the 'strategy sense'. It was more a test of development cycles, user experience, other considerations, thinking beyond merely the price for some features. I had a small technical interview but it was just simple stuff like difference between black box and white box testing, overloading vs overriding, and some basic object oriented design principles."

A second candidate in the same thread agreed on both points: "Definitely use the cases available on the websites, they stress the keys brought up during the actual case (SDLC, etc.). One of the big keys is to combine soft skills with the tech knowledge you have, so try to hit both if you can."

Two independent accounts converging is a pair of anecdotes, so treat it as one. What it corroborates is narrow and it matches what BCG Platinion publishes in 2026: a short technical component sits beside the case, and the firm's own published cases are representative of what gets asked.

The third account in that thread family is quoted in the opening section of this page, where the itemized task list belongs. What it adds here is the confusion itself: the label on the firm did not settle what the job was, and the person who had accepted the offer had to ask strangers.

Four questions that settle the choice, using published facts only

Skip the prestige argument. These four have verifiable answers.

1. Do you want to be there when it ships? Strategy engagements end at the recommendation. Accenture's filed numbers say half its revenue is the running of things after the decision.
2. Does your record read as projects or as decisions? BCG Platinion asks for a list of projects. A strategy application asks what changed because of you. Apply where your record is already in the right shape.
3. Will a technical interview help you or hurt you? One track states that IT skills are assessed. The other does not mention them.
4. Which entity are you actually applying to? At McKinsey the answer is one portal and a preference slot. At BCG the answer is a different company with a different name on the offer letter.

Two of those four have answers you can write down today. Open the firm's careers site and find the posting you would actually submit, then note whether it is a technology posting or a generalist posting with a preference field. Then read your own resume and count the bullet points that end in a decision and the ones that end in a delivered system. Whichever count is higher tells you which application will be easier to write well, and that is a real input rather than a feeling about prestige.

The other two are about tolerance rather than fact. Neither has a right answer, and anyone who tells you one track is better work is describing their own preference. What the published material settles is only this: the two tracks are recruited differently, assessed on partly different criteria, and priced by the same firms under different service lines.

The preparation that transfers, and the part that does not

Most of the work is shared, and that is the good news. Both tracks run a case. Both reward a structure derived from the arithmetic of the problem rather than from a memorized framework, calculations you show, and a recommendation that leads with the answer. Our weights are the same for both: structuring is Coverage 45, Separation 25, Depth 20, Concision 10.

What does not transfer is the object of the case. A technology case is built on a system that has to exist afterward, so sequencing and feasibility carry real weight, and the case can open on a technical premise you have to handle without getting lost inside it. BCG Platinion says presentation is assessed too, which is not a line any strategy process we read includes.

What also does not transfer is the file. Rewriting a delivery record as a decision record is a different job from listing projects, and a candidate applying to both tracks needs both versions.

What nobody publishes about moving between the two

Four gaps, all of them checked and all of them held by someone other than us.

No firm read here publishes a mobility rule between a technology practice and a generalist one: no tenure requirement, no rate, no process. No firm publishes headcount split between advisory and delivery, including Accenture, whose split is in revenue rather than in people. No firm publishes whether a rejected BCG Platinion application affects a later BCG application, and the two entities publish separate processes without addressing the case. And nothing official states that a strategy firm runs a technical interview, so the only evidence for one at any firm is candidate accounts from a different firm in 2015.

We also could not read BCG X's careers pages at all. Direct requests return 403 and the text proxy serves BCG navigation instead of the content, the same failure recorded on 29 September 2026 against the BCG X overview page. What BCG publishes elsewhere about that unit is treated on our BCG X page, and it is not restated here at second hand.

Where to drill either version of the case

The mechanics are the same, so drill the mechanics once. Our drills run one exercise type at a time, structuring, arithmetic, exhibits, synthesis, and score each against the weights linked above, which is what makes a feasibility problem and a structuring problem separable. What the tool does not do: it runs no technical interview of any kind, it teaches no language, framework or architecture, and our assessments page states that 0 of 6 simulators are live. For anything about which entity pays what, the salary pages hold what is sourceable, starting with Accenture, which is the one firm on this page that files audited numbers.

If your own background is engineering rather than computer science, the question of which door takes an engineering degree is a separate one, and it is worked through on cases for engineers.

An order of work, if you are applying to both tracks this cycle. Build the project list first, because it is the artifact only the technology application asks for and it takes the longest to reconstruct from memory. Then drill structuring and arithmetic, which both tracks score. Then, and only if the posting you chose states that IT skills are assessed, spend time on the vocabulary of the systems in your own record, so that a short technical exchange lands on ground you know. Reversing that order is the common mistake, because technical revision feels productive and it is the narrowest of the three.

Corrections logged against this page

30 September 2026. Rewritten from a 198 word draft. Two of its claims were unsourced statements about the world rather than about any firm: that the distance from consequence is "the honest test" of fit, and that "strategy consultants leave before finding out whether it worked; technology consultants usually do not". Neither is measured, and section 6.8 of our own process rules out that family of assertion. What replaced them is the published material: two recruiting architectures, one process page in full, and one audited revenue split.

The draft also stated that technology cases "often carry a technical premise" without naming a firm. That claim now stands on the sentence where BCG Platinion says it assesses IT skills, and on nothing else.

One heading was dropped rather than rewritten. The draft asked which of the two jobs "suits you" and answered with a personality claim. The published material cannot support an answer to that question, so the section became a set of four questions whose answers a reader can look up, and the parts that remain matters of taste are labeled as such.

Third change, on the numbers. The draft carried none. This version carries the audited revenue split because it is the only public figure that sizes the delivery half of the work, and it carries the recalculation alongside it so a reader can check the division rather than take it.

Nothing in the draft was wrong about what the two jobs are. The recommendation stopping point and the longer engagements with larger teams both survived, and they are now the opening paragraph rather than two separate sections.