Me postulé en línea. El proceso tomó 2 semanas. Acudí a una entrevista en 15Five (Remote, OR) en mar 2019
Entrevista
This interview process was thought out extremely well. 15Five chose to forego the typical "whiteboard" interview process, a decision which I would 100% agree with, as those types of interviews leave the applicant with the first impression of the company as one of contention. The process here was extremely simple and I was able to do it all from my house! 4 Video calls, two with current engineers, one with the CTO, and a final call with the Chief Culture Officer. This final call was impressive to me, as a good work culture was important to me in selecting my next job at the time.
Preguntas de entrevista [1]
Pregunta 1
In lieu of whiteboard programming questions, I was asked about Python in a broad sense. The interviewers were skilled enough to know whether I was competent enough for the position by the level of detail that I provided in the answers.
Me postulé en línea. El proceso tomó 3 semanas. Acudí a una entrevista en 15Five en jul 2022
Entrevista
You are first given a skills test through a third party site that consists of both architectural and programming parts.
A recruiter will contact you after to set up a phone interview with the director of engineering. Most of the questions he asked aren't even behavioral, but rather if you fit logistically at the company.
Me postulé en línea. El proceso tomó 3 semanas. Acudí a una entrevista en 15Five en mar 2019
Entrevista
About a week after applying I had a scheduled call with an internal recruiter and a lead engineer (two separate but back to back calls). Everyone was nice and asked the typical questions HR questions and basic phone screen stuff. Mostly just talked shop with the lead engineer for half an hour.
The following week I spoke with the CTO in a very similar fashion I had with the lead engineer.
Preguntas de entrevista [1]
Pregunta 1
Just talked about frontend web stuff. Mostly frontend infrastructure.
