PhD scientist going into BCG Platinion interviews — how did you handle the IT knowledge gap?

Question

I have a PhD in pure science and just passed CV screening for an IT consulting role at BCG Platinion. No background in ERP, CRM, IT architecture — none of it. I'm honestly not sure why they found my profile interesting, and I'm trying to figure out how to approach both the behavioral interviews and the case prep.

A few specific questions:

1. Did your interviewers actually expect you to know IT concepts going in, or is the focus really on structured thinking? How much did your technical background from a non-IT field actually come up?

2. For behavioral questions — how did you translate academic/research experience into consulting language? Were interviewers receptive to PhD stories, or did they want more "business" examples?

3. For cases with a tech/IT angle — how do you handle it when you don't know the domain? Is "I'd approach this from first principles" actually a valid answer, or does it come across as a cop-out?

Any advice from people who made a similar jump (science/academia → IT consulting) would be especially valuable. Thanks in advance.

Answer 1

hey there!

BCG Platinion doesn’t expect you to know IT, they mainly test structured thinking. Many science PhDs start with zero ERP or architecture knowledge, so approaching tech cases from first principles is completely fine. For behavioral questions, translate your research into consulting language by framing it as problem → approach → obstacles → impact; interviewers are very open to strong PhD stories. In tech‑angled cases, stay high‑level: focus on business needs, user requirements, risks, and a simple current‑state to target‑state logic rather than technical details. Your clarity and reasoning matter far more than IT jargon.

Best, Alessa

Answer 2

Congrats on the CV screen.

IT knowledge bar is low for PhDs. They hire you for fast learning, not existing IT depth. Build basic vocabulary in a few hours, ERP, CRM, cloud, APIs, system integration. Be conversational, not technical.
Frame your PhD as a complex project with stakeholders, deadlines, and ambiguity. Talk about leadership, communication, and resilience. Quantify impact. Pure solo academic stories fall flat.
"First principles" works only if you actually show structured reasoning. Ask clarifying questions early, apply consulting frameworks to the tech problem, and acknowledge gaps honestly when needed.

Read BCG Platinion's reports for vocabulary. Practise tech-flavoured cases.

Good luck.

Answer 3

Hi there,

Just putting aside these questions for a moment, I would try and reach out to the recruiter and get a sense from them as to how much IT knowledge they are planning on evaluating during the interviews and how.

That should not only clarify your questions, but also give you a better sense of how to approach the prep.

Feel free to reach out again after and I'm happy to share a specific perspective on prep methods.

Best,
Cristian