I was asked to do 6 hours of interview during the whole process.
After passing the multiple steps and waiting 1 week with no response for feedback I was send a generic rejection email and when I asked them about more feedback I got no response from multiple people from the team.
Perguntas de entrevista [1]
Pergunta 1
System design interview about building an ecommerce
Candidatei-me por meio de recrutador(a). Fiz uma entrevista na empresa MoonPay (Portugal).
Entrevista
1st interview - screen call with recruiter, align on experience and technologies
2nd interview - live coding call, exercise simulating exchange behaviours
3rd interview - follow up to code written in 2nd interview, analyse how it would scale in production, and how it could be optimised
4rd interview - system design interview
Perguntas de entrevista [1]
Pergunta 1
- Past experience
- Distributed caches
- How to handle 2 users accessing the same balance
Candidatei-me por meio de recrutador(a). O processo levou 3 semanas. Fui entrevistado pela MoonPay em jun. de 2025
Entrevista
After going through six interviews with MoonPay, my overall experience was disappointing. Up to that point, the process had been demanding but engaging, which I could understand given the industry and the seniority of the role. However, in the final interview, something was made very clear that hadn’t been communicated before: the company expects long working hours on a regular basis and only hires “A players,” meaning people who are willing to prioritize work above everything else.
This kind of corporate culture is not compatible with a healthy work-life balance. While it’s legitimate to strive for excellence, using that as a reason to normalize constant overwork and exclude those who aren’t willing to operate at that pace reflects a very narrow view of talent.
I would not recommend MoonPay to those who value a sustainable or inclusive work environment that respects different lifestyles and productivity rhythms.
Perguntas de entrevista [1]
Pergunta 1
The system design portion was mostly filler without much depth. During the technical exercise (done as a pair programming session), the task was very simple: read from two JSON files and check which one had sufficient stock. The rest of the process felt like it was just filling time, without adding meaningful insight into the role or challenges.
