Solicité el puesto a través de un captador. El proceso duró 2 semanas. Acudí a una entrevista en Kareo (Irvine, CA) en ene 2015
Entrevista
After speaking to recruiters, there was a thirty minute technically probing telephone interview, followed by full day on site in Irvine. The onsite was haphazard--junior people were thrown in at the last minute to sub for senior people (without any prep), the person I was supposed to work for (out of SF office) had just been hired and been there for three days, the senior manager backed out of schedule early on, etc. Cab fare to/from airport was not even offered to be paid for, but wasn't much--$30 total. Lunch was bought by two mid-level interviewers who were great. The most technical interview was moderately difficult and delivered by long term senior engineers.
Preguntas de entrevista [1]
Pregunta 1
Q: complex topical question about solving a problem with a data structure and algorithm to transverse it effeciently
Solicité el puesto a través de un captador. El proceso duró 1 semana. Acudí a una entrevista en Kareo (Irvine, CA) en ago 2021
Entrevista
First I had a call with a recruiter, then a interview with a software development manager. We had a General conversation before asking me to solve a programming problem.
Next was 3 interviews broken up by 10 minute breaks (all virtual). At each break they would determine if you did well enough for the next round.
First round: two coding questions
Second round: design question
Third round: was supposed to be cross functional.
I stopped after the design question, I didn’t do well enough. It was not clear what they wanted for this and seemed to be front end heavy even though I was being considered for a back end role. To make matters worse, one of the two interviewers was visibly/loudly trying to solve a Rubik’s cube.