McFadyen Digital Interview Questions
& Process

I recently completed the interview process with McFadyen for a Business Analyst role and I'm excited to be joining them in August. The experience was very positive from the start. The recruiter was professional and courteous and promptly shared the detailed job description when I asked, which helped me prepare well for the interviews. I went through two technical interviews and then a meeting with the Hiring Manager. I was particularly impressed by the knowledge and experience of the interview panels, all of whom are senior to me. Their insights and expertise indicate that I'll have great opportunities to learn and grow in this role. After receiving an offer, I eagerly accepted and am now eagerly looking forward to starting with McFadyen in August.

I got through all three technical rounds. After that, HR called and said they'd send over the offer. But then a week went by, and when I asked about it, HR said the budget didn't match what I was expecting. It felt like a waste of my time, especially since we'd talked about salary expectations on the first call.

The interview process started with a 45-MCQ test, including 35 aptitude questions (quantitative, logical, and verbal) and 10 core Java questions from the Oracle SE6 certification, which were moderately easy. This was followed by a personal interview where they asked general questions and puzzles. They mentioned they wouldn't ask technical questions unless something specific was highlighted on the resume, and that knowledge of Java (despite it being their framework language) wasn't expected as training would be provided; they mainly looked for logical thinking and problem-solving ability.

First round was an online test with 45 questions, the last 10 were from Java. I answered 35 easy questions correctly and cleared this round. The second round was an interview with general questions like 'tell me about yourself' and 'where do you see yourself in 5 years'. They asked about my project and 4 puzzles of varying difficulty. C-based questions were also asked, which I couldn't answer. I didn't get through to the next round but it was a nice experience. Coding is very important, which is why I was rejected.