Solicité el puesto a través de un captador. Acudí a una entrevista en Qodea (Manchester, Inglaterra) en dic 2025
Entrevista
The process was very quick. I applied via an external recruiter.
The technical interview was fun - typical pair programming, with the twist of the thing we were working on being a purposely terrible codebase - debugging it took me most of the interview.
A few days afterwards, I got a call offering me the position. However, the offer was far below my expectations (which they were aware of), and with the requirement of 3 days a week in-office (when applying, I explicitly said I will only consider fully-remote). The benefits offered were also nothing to write home about.
Complete radio silence after I countered with my expectations.
Clearly their recruitment process orbits around bait-and-switch. Not recommended.
Solicité el puesto a través de un captador. El proceso duró 6 días. Acudí a una entrevista en Qodea (Londres, Inglaterra) en dic 2018
Entrevista
3 stage interview, first two stages went well, personal chat and then a technical chat, all seemed to be going fine. Was a bit worried by the age demographic as there was no developers in the company under the age of 35..
The third stage was a technical challenge, it seemed very old fashioned, almost as if the questions were designed to catch you out. Very maths based which was not made clear in two previous interviews.
I didn't want to leave a negative review as the guys seems like nice guys, but I did not hear anything after this interview, no feedback at all. Assuming it was a no.
Preguntas de entrevista [1]
Pregunta 1
A system has a limit of 1GB per database but no limit on the number of databases. An application has a requirement to store around 14GB of data. The application data has unique strings as keys (UUIDs/GUIDs for example). Write some pseudocode to allow the application to store and retrieve data from the database system.
