El proceso tomó 5 semanas. Acudí a una entrevista en Helix (Ciudad de México) en oct 2023
Entrevista
The interview was divided in three phases, first round is the typical HR interview, second a tiny code challenge, and finally a virtual on-site round with three interviews, one about architecture, another for programming logic and the final one with the managers of the team to verify matching I have to say that the onsite is all in the same day and it's kinda exhausting.
Preguntas de entrevista [1]
Pregunta 1
They present you a problem and ask you to create an architecture ti fullfil the requirements, then the interviewer add more requisites and you need to make the corresponding modifications.
Me postulé a través de un reclutador. El proceso tomó 2 meses. Acudí a una entrevista en Helix (Ciudad de México) en oct 2023
Entrevista
Más de 4 rondas de entrevistas, con RH, técnicas, diseño de sistemas, más RH para que al final digan que no se aprobó la expectativa salarial, ofrecen la mitad pero no hay puestos con ese perfil. Totalmente contradictorio e ilógico,
Me postulé en línea. El proceso tomó 3 semanas. Acudí a una entrevista en Helix (San Carlos, CA) en sep 2019
Entrevista
Application
I applied online and soon after was sent a link to Hackerrank challenge. It was a two-hour challenge with three problems (two easy level leetcode and one medium). I did not have much trouble with them as I do lots of leetcode practice regularly (I solved over 300 easy and medium problems on leetcode by then). A few days later I was asked to schedule a call with the hiring manager. He was pretty nice, except he kept pushing me to schedule the onsite within three days even though my schedule for this week was already pretty packed and I asked him to move it to a later date. He really insisted.
Interview
The onsite was one lunch interview with two people asking all sorts of questions from education- and experience-related ones to hobbies and favorite apps. Then there were three technical interviews - two problem solving (they were leetcode easy level on strings) and one system design. I did really well on all three. The system design felt like it was a pretty awesome collaborative discussion. The problem solving ones not as much - they were on a laptop, not white board, which made it more isolated. Also both of these two interviewers seemed a bit condescending and maybe even slightly aggressive for no apparent reason (I am a very friendly and soft kind of person). Both of them also were ladies, which was intentional as was later explained to me by the hiring manager (because I am a female, too). The last interview was with the hiring manager, who asked me to do a puzzle on the white board. It was an open-ended problem and I had to ask a lot of clarifying questions, but arrived at a pretty optimal answer in the end.
I felt that it went quite well and I was very happy with my performance - both in demonstrating my technical knowledge and problem-solving skills, as well in the first behavioral interview. Surprisingly enough, I got a standard rejection (when I emailed for an update) a week and a half later. It was sent by the hiring manager from some no-reply email address, even though all our previous conversations went though his regular email. I wish they gave at least some feedback, because I was really puzzled and surprised by this rejection. Out of many interviews I went through I never felt as good about my answers as I did this time. I guess, someone just really disliked me for some reason. I wish I had some insight into why.
Preguntas de entrevista [1]
Pregunta 1
leetcode easy for onsite, leetcode easy + medium for the online challenge