El proceso es largo y tedioso, estuve al rededor de 2 meses entre tiempos de espera y demás. Primero es una entrevista con RRHH para ver expectativas. Luego con el manager para ver experiencias y preguntas de cómo resolverías ciertos casos. Luego te mandan una prueba técnica que tienes que hacer en 72h y luego revisión de la prueba técnica que puede durar hasta 3 h. El feedback que te dan es escaso incluso incierto, ya que en mi caso los temas que me comentan como feedback negativo los hablamos en la entrevista y quedaron resueltos, me sonó a excusas. Después de perder tanto tiempo da la sensación de que por cualquier mínima cosa te van a echar para atrás. No merece la pena.
I applied through a recruiter. I interviewed at Fever in Dec 2025
Interview
The initial screening was a bit unexpected, as it was conducted almost entirely in Spanish without prior confirmation of my language proficiency, and the format felt more like a presentation than a two-way conversation.
Additionally, there were significant scheduling challenges. My technical interview was rescheduled at the last minute due to internal conflicts, and I experienced a period of silence regarding whether the meeting was postponed or canceled. While I appreciate the eventual apology, the process concluded abruptly when I was informed the position had been filled after these delays.
I applied online. The process took 3 days. I interviewed at Fever (Barcelona) in Sept 2025
Interview
There were several processes in the interview, as is typical for Software Engineer positions. One was a technical exercise, and the other involved discussing the technical exercise with a software engineer from the company.
Interview questions [1]
Question 1
I was given three days to complete an entire feature that required the use of various technologies. It included everything: clean code, architecture, performance, my own contributions, etc.
I applied through a recruiter. The process took 4 weeks. I interviewed at Fever in Aug 2025
Interview
The technical assignment was not particularly complex, but it required over 10 hours of work. Combined with the two-hour technical interview, it felt like a significant workload for a recruitment process.
During the technical interview, specifically the system design part, several questions were asked in rapid succession, with very little time to think or structure responses. The questions were quite closed-ended and seemed focused on validating one specific solution, with limited context or opportunity to explore alternatives.
My impression was that the process was more focused on finding someone who had already faced the team's exact challenges, rather than evaluating broader technical reasoning or analytical ability.
Interview questions [1]
Question 1
Como evitar el overbooking
90% eran de base de datos