Me postulé a través de un reclutador. El proceso tomó 3 semanas. Acudí a una entrevista en Casper (New York, NY) en oct 2016
Entrevista
Fairly straightforward. Personality screen with the recruiter, technical phone screen mostly about my background and current position with an engineer, take-home assignment, and finally an afternoon-long on-site interview. The assignment was specific to their stack which I think is unfortunate as it acts as a background filter more than competence or skill filter.
The people there were friendly and intelligent. It was a pleasant process to go through but I found their focus on their technology stack in the final two stages of the interview to be off-putting.
Preguntas de entrevista [1]
Pregunta 1
Every question was about relational database design.
I applied online then was emailed by recruiter. I had a short call with basic interview questions and then was ghosted. I tried following up but never heard back and then a week letter he got back to me saying they filled the role..why waste my time
Preguntas de entrevista [1]
Pregunta 1
How have I worked with other team members to complete a task or project
Technical and non-technical Interview. The interviewers were very nice and the experience was quite good. I have no complaints about the interview and unlike many coding interviews, you didn't feel like you were being grilled.
Me postulé a través de una agencia de empleos. El proceso tomó 1 semana. Acudí a una entrevista en Casper (New York, NY) en may 2018
Entrevista
Contacted through Vettery.
First call was with HR. They were friendly and asked questions about my experience, why I was leaving my current job, etc...
I was then set up to speak with an engineering manager. It was not technical. We went over my resume, talked about the company culture, and what sort of things my position would work on. It lasted roughly 45 minutes.
I received a boilerplate rejection a couple days later. I'm not sure what more I could have done given the generic reasoning. Perhaps it was lack of experience, culture fit, or something else but it definitely wasn't because of my technical skills since we never tested it.