Monzo Bank logo

Monzo Bank Data Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 14 interview experiences · FREE TO READ

3.1 Rounds average
Average Typical difficulty
57.1% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Monzo Bank.

Showing 3 of 14
Monzo Bank logo
Monzo Bank

Analytics Engineer

Analytics · nearly a year ago

Mid Average Positive experience No offer 4 rounds
Interview process
Recruiter call Technical screen Take home Technical screen
Interview formats
Behavioral Technical Coding

It started with a recruiter call, then a deeper dive into my experience with an engineer. After that, I had a take-home test. The take-home was in BigQuery, focused on writing readable, maintainable SQL that follows data modeling best practices. The technical round involved looking at a relational model you'd expect from a backend service and figuring out the changes needed to create KPIs and metrics from it.

Confirmed questions5 questions
  • Tell me about your experience with stakeholder management.
  • How do you approach project management?
  • What technical best practices do you follow?
Monzo Bank logo
Monzo Bank

Analytics Engineer

Analytics · more than a year ago

Senior Difficult Positive experience No offer 4 rounds
Interview process
Recruiter call Technical screen Take home Onsite
Interview formats
Behavioral Technical Coding Case

The talent team and process was great. I really appreciated them throughout. The interview process felt pretty standard with an exception at the end. It started with a phone screen, then a background interview with two team members, followed by a take-home challenge, and finally, some final interviews. Everything was pretty standard and I really enjoyed meeting members of the team. They all gave great impressions of the company. However, one of the final stages I was expecting to be a review of the coding challenge. Instead, it was a really odd interview with a couple of scenarios put in front of you: 'This query isn't working' and a financial fraud data science problem. I didn't give them what they were after on these, but the scope of what you could do was very confusing. There is very little sympathy regarding it being an interview environment. Don't go on to try and solve the problem, my advice would be to clarify as much as you can. When I would ask 'Do you have any idea what is wrong regarding the output?' it was met with 'I don't know it just isn't giving me what I want'. Similarly, in the second scenario, you could suggest 'going to the back end engineering team and changing how this data is generated'. This wasn't ever a clearly an option. Either way, I have little doubt it is a good company to work for and everyone I met gave very good impressions. A shame on that last stage.

Confirmed questions4 questions
  • Can you tell me about your experience with dbt?
  • Could you describe some data problems you've tackled with dbt and your approach?
  • Given a situation where 'this query isn't working', what is the issue with the output?
Monzo Bank logo
Monzo Bank

Analytics Engineer

Analytics · more than a year ago

Mid Average Negative experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Technical Coding

I sent in my application online. A recruiter got back to me in a couple of days, and then it took another couple of days to set up an initial 30-minute screening call. This went fine and was a good chat. After that, I was told about the rest of the process: a 4-hour take-home task, followed by another 3 hours of interviews. At this point, I decided to stop the process. This would have been almost an 8-hour commitment, which is way too much and doesn't respect my time. It's more than double what I've experienced at other tech companies.

Confirmed questions2 questions
  • What are the characteristics of a good data warehouse?
  • Complete a take-home assessment where you'll create data models to address fundamental growth accounting questions, providing documentation and test cases.

Monzo Bank Data Engineer Interview Questions

Quoted word for word from Monzo Bank interview reports.

What is the difference between SUM OVER and SUM, and can you provide an example to illustrate why and what we would get from a given query?

Read reports

Given a situation where 'this query isn't working', what is the issue with the output?

Read reports

Can you explain the difference between a left join and a full join, providing an example?

Read report

Can you write readable and maintainable SQL in BigQuery following data modeling best practices?

Read report

In the context of the complex SQL query, how would you go about correcting it?

Read report

Can you describe the characteristics of an effective data warehouse?

Read report

Formats, difficulty and experience

Across all 14 Monzo Bank interview reports.

Interview formats

Technical 36.4%
Behavioral 30.3%
Coding 21.2%
Case 9.1%
System Design 3%

Interview difficulty

Easy 0%
Average 85.7%
Difficult 14.3%

Candidate experience

Positive 57.1%
Neutral 21.4%
Negative 21.4%