Monzo Bank logo

Monzo Bank Ios Engineer Interview Questions
& Process

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

Based on 15 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
13.3% Positive experience

Candidate interview experiences

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

Showing 3 of 15
Monzo Bank logo
Monzo Bank

Senior iOS Developer

Engineering · half a year ago

Senior Average Negative experience No offer 1 round
Interview process
Technical screen
Interview formats
Coding Technical

So the interview was basically a technical one. I had to work on some existing iOS code and add a new feature. The goal was to show news articles, but organized by year, in a table view. This meant structuring the ViewModel to handle the data grouping and then making the UI layer support sections. It was pretty collaborative for the most part; the interviewer was nice and we chatted about how to do things while I was coding. We explored different ways and refined the code together. But then, near the end, with just a tiny bit left to finish, the interviewer just abruptly hung up. No goodbyes, no final chat, just gone. It was around the scheduled end time, so maybe they were just rushed, but it felt a bit off, not very professional. The actual coding task was good though, pretty relevant to real iOS dev work, but the ending was kinda weird.

Confirmed questions2 questions
  • In an existing iOS sample project, implement a feature to display news items that are grouped into sections.
  • The task involved modifying the TableView to support sections and updating the ViewModel to group news items by year before presenting them in the UI.
Monzo Bank logo
Monzo Bank

iOS Engineer

Engineering

Entry Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Take home Presentation
Interview formats
Coding Technical Presentation

The company's website has a good outline of their hiring process, and my experience followed that scheme pretty closely. It started with an initial call, then a take-home task. The take-home involved debugging an app and getting it ready for release within a time limit. After that, there was a discussion about the take-home task where they wanted to know about my approach and the decisions I made. I didn't advance further because my refactoring wasn't up to par.

Confirmed questions2 questions
  • Regarding the take-home task, could you elaborate on the trade-offs you decided to make?
  • What were the trade-offs you made while working on the task?
Monzo Bank logo
Monzo Bank

IOS Engineer

Engineering

Senior Difficult Positive experience No offer 6 rounds
Interview process
Recruiter call Technical screen Take home Technical screen Onsite Panel Background check Offer
Interview formats
Behavioral Technical Coding System Design

It was a pretty long process: first, a recruiter call, then an engineer interview where I had to discuss a project I fully developed. After that, there was a take-home assignment (or live coding, but I chose the take-home). The take-home was supposed to be done in 4 hours and included items for a future iteration, with evaluation based on prioritization. The project was a small legacy app with two UIKit/storyboard screens, and I could refactor as needed. I decided to switch everything to SwiftUI and adopted MVVM for testable architecture, while keeping the minimum iOS version requirement. Next, I reviewed my solution with an engineer. Finally, there were two interviews: System Design, where I had to design a Spotify screen with songs and folders, and a Behavioral interview. In the behavioral part, I had to elaborate on 4 questions/situations using the STAR method, including topics like mentoring and driving initiatives. The people were really nice, and I got detailed feedback at every stage.

Confirmed questions2 questions
  • Tell me about your mentoring experiences.
  • What projects have you worked on in the past?

Monzo Bank Ios Engineer Interview Questions

Quoted word for word from Monzo Bank interview reports.

When defining JSON properties, what considerations do you take into account?

Read reports

How would you approach implementing a new feature within a codebase that contains both Swift concurrency and non-concurrency code?

Read report

What would be the steps to complete this project for release?

Read report

How do you approach incorporating suggestions and feedback from others during the design process?

Read report

Formats, difficulty and experience

Across all 15 Monzo Bank interview reports.

Interview formats

Technical 36.6%
Behavioral 26.8%
Coding 24.4%
System Design 7.3%
Presentation 4.9%

Interview difficulty

Easy 33.3%
Average 46.7%
Difficult 20%

Candidate experience

Negative 60%
Positive 13.3%
Neutral 26.7%