I applied through a recruiter. The process took 2 weeks. I interviewed at Oliver Wyman (London, England) in Apr 2017
Interview
Zeroth phase was a questionnaire spanning professional stuff (language preferences etc) through to film/book preferences.
First phase was a simple bit manipulation coding exercise to get familiar with their online IDE.
Second phase was a phone screen with a harder algo problem (max sub array, [again]). IDE misbehaved so we had to move to another website. Opportunity to ask questions to get some colour on typical project.
Third phase was on-site; 3 hour coding challenge. Should have prepared my BitBucket repository more carefully as burnt through a bit of time getting up to speed with that; on the other hand there's only so much spare time to devote to things like this when you're interviewing at multiple places and they each have their own favourite IDE/code repository etc. Was hoping for a little more friendly help to get over stuff you would expect a colleague to just help you with in a real work situation.
Wasn't made to feel particularly welcome; and (bad) rock music was played over their PA during the process(!); didn't feel a particularly happy environment from the outside.
Made progress with the exercise, but it only takes a few issues with maven 3rd party library dependencies in IntelliJ (it's not just me, right?) to cost you valuable 10s of minutes and then your time's up. Probably if you've written an html/json stripper once or twice before, you'd ace it. I've not come across that sort of work professionally (thankfully) so was a bit slow to progress.
Content for the process to end there; if stripping data out of html feeds is representative of their typical project and their office atmosphere is always like that, it wouldn't be a great fit on either side.
Build an application to strip tube times out of a JSON result feed from a TFL webpage. Present to display the next arrival, update every minute, that sort of thing.
I applied through an employee referral. I interviewed at Oliver Wyman in Mar 2022
Interview
The interview process starts with an HR screening via phone call. Was asked why I was seeking other opportunities and why Oliver Wyman. This phone screening was followed by a 1-hr case + fit interview. I was informed that a successful interview would be followed by another 2-3 rounds of interviews, which sadly didn't materialize in my case.
During the HR screening, I asked about the type of engagements OW has in the engineering front and was surprised (and found it odd esp for a consulting firm of OW's caliber ) to hear that the person at the other end didn't have much clue about it and was asked to ask the question during the technical interview.
I applied through a recruiter. The process took 2 days. I interviewed at Oliver Wyman (London, England) in Jan 2019
Interview
Online algorithms coding question - relatively simple, questions on complexity. Slightly messy attitude in that they used an ad-hoc code sharing platform requiring some user set up and got configuration. No video.
On-site coding interview. (Interacting with online API. Unsupervised. ) This was OK, these interviewers had better people skills too!
Technical interview. Very much a compsci knowledge test - so much so that I’d almost say don’t bother without a computer science degree. Three interviewers. Fairly disorganised as members weren’t sure whether they had similar question sheets, who was going to ask what next.
Final interview with management. This one was actively hostile. Bizarrely focussed on the problems of a previous company on my CV rather than the positive changes I’d applied to a poor situation. Did not leave a good impression of the company.
No feedback afterwards. General impression was a fairly arrogant company, although mixed members.
I applied online. The process took 1 day. I interviewed at Oliver Wyman (London, England) in Apr 2018
Interview
Face to face for an hour, technical questions around java and payment systems, business knowledge around money transfer
describe pros and cons of a built in data structure like ArrayList
drawing architecture of a payment system etc
felt over-qualified