J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez Pleo (Madrid) en déc. 2024
Entretien
The process started pretty well with the introductory call with the recruiter.
Next step is a coding skill challenge through CodeSignal, which was a bit strange. Challenge was challenging due to time constrains + complexity. Even if offline, pressure increases with the addition of the Proctoring add on they included, which makes you fully expose your computer while running the challenge.
But the worst thing during the process if the fact that i've been totally ghosted after submitting this challenge. No feedback nor any kind of comm (even rejection) from their side after it.
J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez Pleo (Manchester, Angleterre) en mars 2025
Entretien
I had the usual intro chat with an internal recruiter, afterwhich I was sent a tech test on the CodeSignal platform. The test they chose matched none of the modern tech from the job description. The test should have been for a frontend React Native mobile role, but the actual test was to manipulate an extened class. There were some confusing instructions made to catch people out/waste their time. I haven't used a class in 8 years. Out of the 4 tasks, I completed 1 and a half and was given a mediocre score, then rejected. If their front-end mobile codebase looks anything like the test I was given, then this is a blessing.
Questions d'entretien [1]
Question 1
Create an in memory database for registering, clocking-in/out, and getting employee information, along with the ability to query and sort results.
J'ai postulé en ligne. Le processus a pris 4 semaines. J'ai passé un entretien chez Pleo (Madrid) en janv. 2025
Entretien
In my case, the expected process as per one of the e-mails I received was, as copy-pasted:
Intro call; CodeSignal test; hiring manager interview; system design interview; final interview
I was rejected after the system design interview.
Questions d'entretien [1]
Question 1
Screening - availability, reason for applying
big O - Leetcode medium, maybe a bit easier than that. It's one of those exercises that has multiple phases where each builds on top of your solution to the previous one. In my case, it had 4 and it was required that I complete 3. I was informed of this beforehand although in an unnecessarily misleading way imho, as I was told 70% was the minimum "grade" to pass, while each step awards you with a score of up to 25%.
Manager interview - Conflict resolution, addressing bringing up process improvements as well as my way of improving others
System design - Design a system where you can show a list of transactions made by a user. The problem statement was a little misleading imho because it turned out that they wanted me to design the API endpoints and not do a client HLD, which is opposite to every other mobile design interview I have ever done, and that includes Meta, as well as what's stated on resources provided by the company themselves ahead of the interview, but maybe you can give them the benefit of the doubt and pin this on me not having clarified a seemingly-already-clear point instead.
