dunnhumby Analyst Interview Questions
& Process

The interview process started with an online test on HackerEarth which had 22-25 MCQs, 3 simple programming questions, and 2 data manipulation questions using Pandas with Python, all within a 1-hour time limit. I managed to solve most of the MCQs, 2 programming questions, and 1 Pandas question to advance to the next stage. After that, there were two technical interviews scheduled onsite. Although there was a significant wait (over 2 hours), the interviews themselves went as planned. The first F2F round involved a basic introduction, followed by questions related to my resume. I was asked to write a SQL query for cross multiplication and a code snippet for a simple array summation problem. Other topics covered included avoiding overfitting, L1 and L2 regularization, and using the RFM model for customer segmentation. The interviewer was very approachable. The second F2F round, with a Director, also began after a short wait and was characterized by politeness. This round focused heavily on my previous work experience. I was given a bakery dataset and asked to extract insights and visualize them effectively. The role itself was then discussed. After this, I was told to wait for the final decision. An HR representative contacted me shortly after, confirming I had cleared the technical rounds and that I would receive an email on Monday for document submission. I received the email on Monday requesting my current job letter, salary slips, and other necessary documents. I sent my documents the same day but haven't heard back in over 25 days, even after a follow-up email, which turned a good interview experience into a frustrating one.

So, it started with a basic HR screening, then a phone interview with HR was set up. But literally the day before, they emailed saying oops, it's actually an onsite with the manager and a senior analyst. Super last minute and totally different prep needed, but I went along with it. At the onsite, they asked about my background and CV, and then hit me with an SQL test. This was annoying because after the initial mix-up, I'd specifically asked what the interview would be like, and they never mentioned a test. Then, in the next stage, I was told I'd do an SQL test, which didn't make sense since I'd already done one. The actual interview (it was 2 hours long) involved: another chat with the manager and a different team member, a presentation (10-15 mins) I had to prep beforehand, a 30-minute data analysis task where I had to give my opinion on a question, and finally, a part where they asked how I'd tackle some past client issues they'd had (high-level stuff). I didn't get the job, and honestly, the constant miscommunication really put me off. Plus, HR was super slow to respond, making scheduling and getting info a hassle.

I first got contacted by the company through my university's career services. Then, I went to two "pre" nights. One was a meeting at a bar, and the other involved a presentation and an activity where we were put into groups. We were given different receipts and had to analyze trends or draw conclusions from them. It felt like our answers were only half right. About 3 weeks later, I had the interview, which was with two recruiters who asked a lot of behavioral questions. They used confusing language to try and steer me toward their predetermined answers. Again, my ideas felt only half right. It was good practice though, so be ready to talk about your past experiences.