Boston Consulting Group · Primly Community

Boston Consulting Group coding interview and online assessment: format, difficulty, and what tripped me up

sre_sol · 6 replies

I'll keep this technical and skip the feelings part.

BCG's engineering pipeline includes a HackerRank OA and then two live coding rounds in the onsite. Here's what I observed:

Online Assessment (HackerRank) 90 minutes 3 problems in my case: one easy warmup (string manipulation), one medium (tree traversal), one that was technically medium but had an edge case that would catch you if you just pattern-matched to the obvious solution No webcam, no proctor for the one I did Standard HackerRank judge, test cases visible on pass, hidden on fail

The third problem is where they're probably differentiating. I finished with about 10 minutes to spare but nearly got the third one wrong because I didn't read the constraints carefully. The input size meant a naive O(n^2) would time out on large cases but pass the visible tests. Classic.

Live coding rounds (2 rounds, 45 min each) Done in a shared editor, I used Python First round: graph problem, BFS/DFS variant, interviewer gave hints when I got stuck but tracked how fast I needed them Second round: more of a design-and-code hybrid, less algorithms, more about structuring a small feature cleanly

I'd call both rounds "LeetCode medium" in difficulty. Nothing I'd classify as hard. But they were watching how I worked, not just whether I got the right answer. I talked through my approach before coding anything, which the interviewer explicitly said was helpful.

Couple of notes: They do not require you to memorize sorting algorithms from scratch. I was not asked to implement quicksort. What they cared about was: do you know when to use a hashmap vs. a heap, and can you reason about complexity.

If you're coming from a pure consulting background and trying to get into BCG's tech org, the OA is the real filter. Brush up on trees, graphs, and hashing. Not DP-heavy in my experience.

6 replies

newgrad_neil

Did they tell you the OA results or just move you forward silently? I have one coming up and didn't know if I'd get a score.

ml_mike

They didn't give me a score. Recruiter just emailed a few days later saying they wanted to move forward. No breakdown.

ds_dmitri

The O(n^2) trap on the OA is so consistent across companies. They design those problems specifically to catch people who test on visible cases and don't think about complexity. Has cost me before.

ml_mike

Exactly. Always check the constraint box before writing a single line. 10^5 inputs means you need O(n log n) or better, basically always.

frontend_fran

What language did most people seem to use? I mostly do JavaScript but can write Python if needed.

ml_mike

Use whatever you're fastest in. Python seemed fine, I didn't ask about others specifically.