In a typical Platinion first round of eight, I score three or four candidates as technically fluent and still no-hire. They can diagram a target state. They cannot land it: cash, downtime, integration tax, and who owns the cutover.
That is the thesis most prep never states. BCG Platinion is BCG's specialized technology consulting entity for architecture and large-scale IT and AI transformation. The interview is not a certification exam. After you read this, you should know how the published loop separates business and IT cases, how to drive a technology prompt like a partner would, and how to practice the commercial half without inventing a fake architecture quiz.
What Platinion is — and what the posting is not
BCG's own digital overview puts Platinion next to BCG X with a clean split: Platinion combines BCG strategy with tech know-how to implement and secure large-scale tech transformations; BCG X is the tech build and design unit. Platinion's about page (as of late 2025 site copy) describes 1,000+ tech experts across 70+ offices, founded in Cologne in 2000, with work spanning architecture, AI, cybersecurity, ERP, and risk.
If the requisition says Platinion (AI Tech Architect or AI Tech Consultant), expect architecture judgment, transformation sequencing, and client-facing synthesis. If it says BCG X, expect shipping. If it says Associate or Consultant on a generalist track, use the BCG case interview guide and stop reading architecture blogs as your primary prep.
Do not invent Platinion salary bands from forum screenshots. Role, market, and level move the number. Ask the recruiter.
The published loop: two cases, not one vibe
Platinion's application process page is unusually explicit for a consulting brand. Client-facing paths run at least two interview rounds with case studies. Round 1 is typically two interviews covering background, motivation, and a case that tests analytical, qualitative, technical, and presentation skills. Some regions add a logic test before that round. Round 2, in the version they publish, often pairs a BCG business case with a BCG Platinion IT case, including senior Platinion and sometimes BCG leadership interviewers. Extra rounds happen; decisions and Round 2 are often combined.
| Stage | What they publish | What I listen for |
|---|---|---|
| CV + intro call | Project list for consulting roles | Can you name outcomes, not only tools? |
| Round 1 | Fit + case (tech and presentation) | Structure under ambiguity; plain English |
| Logic test (some offices) | Before Round 1 | Accuracy under time, not cleverness |
| Round 2 | BCG business case + Platinion IT case | Both halves: commercial and architectural |
Their prepare page tells candidates to practice structuring cases, stay fluent with numbers and KPIs, and understand that Platinion's focus is IT architecture design and AI strategy rather than pure implementation theatre. That line matters. You are not there to recite Kubernetes flags. You are there to design a target state a CIO can fund and a plant manager can survive.
Confirm the exact format for your office in the intro call. Regional variants are real. Forum timelines are folklore until your recruiter says otherwise.
The scoring sheet in plain language
I score Platinion cases on five lines. Miss two and you are done, even if the diagram is pretty.
- Business sentence first. Why does this architecture choice move revenue, cost, risk, or compliance?
- Constraint before stack. Downtime caps, residency, typescript of legacy skills, budget ceiling, regulatory freeze windows.
- Options that are real. At least two viable paths plus a "stabilize and wait" when that is honest.
- Cash that closes. Capex, run, integration, delay cost — rough is fine; silent zeros are not.
- Landing plan. Cutover shape, rollback, operating model, who owns week one after go-live.
Ned's rule. Name the hard constraint before you name a product. If the recommendation needs more downtime, more cash, or more rare skills than the client has, it is not a recommendation. It is a wishlist.
Engineers who skip line one fail the BCG business case half of Round 2. Strategy candidates who skip lines two through five fail the IT case. The firm designed the pair that way.
Worked example: strangler vs big bang for a payments core
Prompt. NordPay is a fictional €1.1 billion payments processor in three EU markets. Its authorization core sits on a 17-year-old mainframe that handles 4,200 transactions per second at peak. Mean time between severity-1 incidents has dropped from 90 days to 22 days. The board wants a cloud-native core within 30 months and will not accept more than 15 minutes of authorization downtime in any cutover window. Budget envelope: €48 million all-in. Two vendors bid.
Option A — big bang rewrite. Build a new core on managed cloud services. Capex €31 million. Run cost after cutover €4.2 million/year versus €6.8 million today. Cutover weekend: vendor estimates 6 hours of dual-write freeze. Mainframe team exits 14 months after kickoff.
Option B — strangler with API facade. Put an API layer in front of the mainframe, carve out services (fraud, limits, auth routing) over 28 months. Capex €22 million. Integration and dual-run add €1.8 million/year for three years, then fall away. Peak downtime per slice: 8–12 minutes. Mainframe exits only after the last slice.
Ask for the exhibit they hope you request. Big-bang dry runs at peer processors averaged 47 minutes of authorization outage, not 6 hours of planned freeze — because reconciliation and card-scheme sync overran. That violates the 15-minute board rule. Strangler dry runs stayed under 12 minutes per slice in the vendor's last three banking clients.
Math you can do in the room (undiscounted, interview-grade).
Five-year cash, Option A: 31 + 4.2×5 = 31 + 21 = €52 million, plus a probability-weighted outage cost. If one failed cutover costs €9 million in scheme penalties and merchant churn (your assumption, stated aloud), and historical dry-run failure rate is one in three, expected penalty ≈ €3 million. Effective picture ≈ €55 million, with a hard constraint breach on downtime.
Five-year cash, Option B: 22 + (1.8×3 dual-run) + (4.5×2 steady new run after year 3, assume new platform run settles at €4.5 million) = 22 + 5.4 + 9 = €36.4 million. No 15-minute violation on the vendor's own dry runs. Residual risk: mainframe skills cliff if you schedule exit too early — keep two contractors through month 30 (add €1.2 million; say so).
Synthesis. "I would not take Option A on this quote. The board's 15-minute rule is binding, peer dry runs break it, and five-year cash is worse once you price the outage. Recommend the strangler: fund the €22 million build, budget €1.8 million/year dual-run for three years, sequence fraud and limits first because they drive 60% of Sev-1s, and keep mainframe contractors through final cutover. Revisit full rewrite only if scheme rules force a hard date the strangler cannot meet."
That answer is Platinion-shaped: constraint, options, cash, landing, residual risk. No religion about cloud. No silent zeros.
Where strong engineers leak points
Stack theatre. "We should go event-driven microservices" with no mention of peak TPS, scheme SLAs, or who runs on-call. I stop listening.
One option dressed as analysis. If every path leads to your favorite vendor, you are pitching, not casing.
Ignoring the business half. Round 2 includes a BCG-style case for a reason. Practice a pure profitability or market-entry case the week before. Architecture depth does not excuse a broken issue tree.
Fake precision. Citing "pass rates" or Platinion pay bands you cannot source is worse than saying you do not know. The firm does not publish those figures on the careers site.
Wrong brand story. A Platinion interview is a poor place to narrate shipping a consumer app as if you were applying to BCG X. Read the posting. Architect vs build.
How to prep in three weeks without a fake exam
Week 1 — translate your projects. Take two systems you actually worked on. For each, speak aloud: objective, hard constraint, option A/B, rough TCO, cutover risk, what you would do differently. Record yourself. Cut jargon by half.
Week 2 — split practice. One generalist candidate-led case so the BCG business case half does not surprise you (BCG case practice). One technology prompt like NordPay: integration, migration shape, cash. Drill the commercial math on /drills/math.
Week 3 — fit and presentation. Platinion still hires people they want next to a CIO. Prepare one conflict story where IT and the business wanted different dates, and one time you killed a pet architecture because the constraint would not move. Behavioral length differs by firm; see consulting behavioral interviews.
Confirm with recruiting whether Casey, a take-home, or a calculator appears for your market. Invitation text beats Reddit.
Practice this today
Run one 20-minute drill: open a blank page, write the NordPay prompt above (or invent a peer), force yourself through constraint → options → five-year cash → 60-second synthesis. Then do a clean generalist case on /start (three typed turns, instant scores, no account required) so Round 2's BCG business case does not feel like a different sport. For a full voice loop with debrief, use /interview. Everything on CoachNed is open for seven days with no card; then $120 for a recruiting season or $49 a month.
Frequently asked questions
How many interview rounds does BCG Platinion have?
Platinion publishes a minimum of two rounds with case studies after a CV screen and intro call. Some regions add a logic test before Round 1, and extra interviews can appear by case. Confirm your office's path with recruiting.
What is the difference between BCG Platinion and BCG X?
On BCG's digital capabilities page, Platinion implements and secures large-scale tech transformations; BCG X is the tech build and design unit. In interview terms: architecture and landing versus shipping product and platforms. Read the job title, not the BCG logo alone.
Do Platinion interviews include a normal BCG business case?
Yes, in the Round 2 format Platinion describes publicly: a BCG business case paired with a Platinion IT case. Treat the commercial half as seriously as the architecture half.
What should I put on a Platinion project list?
Outcomes, constraints, your decision, and scale. "Led cloud migration for payments auth, cut Sev-1s 40%, under 15-minute cutover SLA" beats a stack laundry list. They ask consulting applicants for a project list for a reason.
Does CoachNed simulate Platinion-specific architecture exams?
No. CoachNed drills case structure, math, charts, and voice cases so you can land technology prompts commercially. Pair that with your own architecture depth from real projects. CoachNed is not affiliated with BCG or BCG Platinion.
Sources
- About Us | BCG Platinion — entity description, founding, headcount and office claims on firm site. Checked 2026-09-24.
- Application Process | BCG Platinion — published interview rounds, logic test note, Round 2 business + IT case pairing. Checked 2026-09-24.
- Prepare for Your Application | BCG Platinion — prep guidance on structure, KPIs, architecture focus vs pure implementation. Checked 2026-09-24.
- Digital, Technology, and Data Consulting | BCG — firm distinction between BCG X (build) and BCG Platinion (implement and secure transformations). Checked 2026-09-24.
- BCG Platinion | BCG — BCG network description of Platinion's role. Checked 2026-09-24.