Me postulé a través de un reclutador. El proceso tomó 3 semanas. Acudí a una entrevista en OutSystems en nov 2025
Entrevista
I went through 3 rounds of interviews. The first round was a behavioral interview that also included a coding assessment. The second round was a take-home project that took me about 20 hours to complete. The final round was me presenting the code I wrote, which I also spent a lot of time preparing. It felt like a lot of work to get an automated rejection e-mail over a week later.
Preguntas de entrevista [1]
Pregunta 1
There was a take home project to create a booking service.
Me postulé en línea. El proceso tomó 6 semanas. Acudí a una entrevista en OutSystems en mar 2025
Entrevista
The interview process was very straightforward.
I applied for the position through LinkedIn, and two weeks later, I was contacted by a member of OutSystem's recruiting team for an initial interview.
The first interview was a non-technical "getting to know you" kind of discussion. They asked about my background and college history. The recruiter was very kind.
After the first interview, I was then scheduled to meet with the hiring manager. This was a pretty standard discussion about my job history and experience.
Next was a technical interview with one of their "Lead Software Engineers." In this interview, I went through two "DSA" style questions using a shared session via HackerRank. The interviewer was very kind and patient.
The final interview was with an "architect" in which we discussed some application architecture. This was by far the longest interview, but it was an enjoyable conversation.
Preguntas de entrevista [1]
Pregunta 1
Describe a project that you worked on that didn't work out so well.
Me postulé a través de una recomendación de un empleado. El proceso tomó 6 semanas. Acudí a una entrevista en OutSystems
Entrevista
The interview process was made very clear in the first interview. 1 HR interview, 1 manager interview and 3 technical interviews. The technical ones were based on live coding and focused on problem solving and performance.
Preguntas de entrevista [1]
Pregunta 1
Many times I was asked about the complexity of whatever algorithm I was writing