1 recruiter phone call, then 1 tech phone screen, very Java specific. Afterwards, a take home challenge that took several hours. Then, a 4 hour onsite. Everyone I met seemed super friendly and the atmosphere was nice and casual.
Got good feedback from most people I assume. Afterwards, the recruiter literally sent me an email saying I got a verbal offer. The next day, I got a call saying my GPA wasn't up to their standards. This was super disappointing, and a huge waste of time. Why not screen for GPA first, before having a candidate go through that entire process?
Overall, everyone was really nice on the outside, but it turned out to be a waste.
Perguntas de entrevista [1]
Pergunta 1
build a CRUD application in Node, Java specific questions, resume digging.
O processo levou 4 semanas. Fiz uma entrevista na empresa Kinsa (San Francisco, CA).
Entrevista
The interview consisted of a group interview and five one-on-one interviews. The group interview focused on technical questions, but it was at a high level and centered on software design. The one-on-one interviews were more focused on getting to know me as a candidate and assessing my fit for the company culture.
Perguntas de entrevista [1]
Pergunta 1
How to deal with large amounts of complicated data. What data structures or strategies would you use.
HR phone call (usual questions), engineer phone screen (mostly questions about background, nothing much on the technical side), assignment to build a CRUD application, onsite 3 interviews - mostly questions about background and design questions. Not much on the coding questions.
