Pros: I liked to work here.

Cons: There are a lot of people to work with.

Pros: * Talented, motivated people across the engineering org with genuinely smart colleagues who care about quality * The product itself is well-crafted and something you can take pride in working on * Enough autonomy that self-directed engineers can get things done, if given the right environment to do so * Good tooling and engineering practices in place

Cons: * Monzo has a well-deserved reputation for engineering quality and sets a high interview bar to match. But be aware that the day-to-day reality, particularly for mobile engineers, may not live up to expectations. If you're joining for technically challenging work, it's worth going in with a clear picture of what your role will actually involve. * Monzo invests heavily in its culture, which is great, but at times it can tip into something that feels more cult-like than organic. For newer employees especially, the intensity around values, visibility and ways of working can feel overwhelming and somewhat exclusionary rather than welcoming. * Role alignment can be poor - I was hired for a specific specialism but spend the majority of my time on unrelated work. This has never been properly corrected despite being acknowledged internally * The day-to-day work assigned to me is largely routine and doesn't reflect the level of technical challenge I'd expected or want in a senior role. Likely a symptom of the role mismatch rather than the company generally * Mobile engineers on product teams may find the work underwhelming, Much of the UI is server-driven, leaving relatively little meaningful front-end work to do. This creates peaks and troughs, with more troughs than peaks. During quieter periods, engineers are largely left to find their own work, which tends to be ad-hoc and unplanned rather than strategically driven — possibly a reflection of limited product roadmap visibility. * Squads typically have just one iOS and one Android engineer, which can leave mobile engineers feeling isolated. There's limited day-to-day interaction with others in your specialism, which makes collaboration and knowledge sharing harder than it should be * Senior mobile engineers should be aware that they may be assigned to lead projects outside their specialism, including backend work. This is a poor use of specialist skills and can be frustrating for engineers who were hired specifically for their mobile expertise * While there were genuinely warm and authentic people in the team, the broader culture could at times feel performative. Slack interactions in particular sometimes felt more like visibility management than genuine conversation, as though activity was being logged for future reference rather than communicating naturally. * Slack is overwhelming. The culture heavily favours public channel communication in the name of transparency, which in practice means an enormous volume of messages to keep on top of. Missing a thread is easily done, but can reflect poorly on you, creating an unspoken pressure to be constantly monitoring Slack rather than actually getting work done * D&I values are clearly important here, which is admirable in principle. But in practice it can feel overcorrected to the point of creating friction. Automated tooling that polices everyday language in Slack ends up making you second-guess natural communication, which if anything has the opposite of the intended effect * Feedback culture feels retrospective rather than developmental. Issues are surfaced late rather than being addressed in real time * Project cancellations make it difficult to demonstrate impact, compounding the above issues * The end of year review process is substantial. Engineers are expected to write a detailed self-review and provide feedback for multiple colleagues who request it, which can take several days to complete. It reinforces a culture where what you're seen to say and do matters more than the work itself. * Employee tenure is notably short. The majority of people have only been with the company for a few years, with very few being there 4+ years. For a company of Monzo's age, that's worth reflecting on. * Burnout appears to be a genuine issue in my experience. The frequency of people taking sick days was noticeably higher than anywhere else I've worked, which perhaps speaks to the pace and pressure of the environment.

Pros: You get to work on challenging things with a really great team and can end up owning large features/backend services. The company is religiously transparent internally which means you are always aware of the company plans and reasoning behind them.

Cons: The pace of development is very quick and often ends up working long hours.