Candidatei-me por meio de uma agência de recrutamento. O processo levou 2 semanas. Fui entrevistado pela Ginkgo (South Lake Tahoe, CA) em mar. de 2018
Entrevista
I was found by a headhunter. No phone interviews, just the 3 hour coding test. I got everything right, according to their instruction, but was told insufficient. I'm very upset by their ways of judging your coding solutions because in the instruction they say they will evaluate your result by 1,2,3,4 rules. But even if you satisfy them, they still say insufficient. I have no idea how they judge, very very bad experience and such a waste of time.
I'm sorry you feel you passed the exam but didn't receive thorough feedback. If you message me directly I can review the report and let you know more details about their decision.
Outras avaliações de entrevista de vagas de Quantitative Researcher da empresa Ginkgo
Candidatei-me online. O processo levou 4 semanas. Fiz uma entrevista na empresa Ginkgo.
Entrevista
I was first assigned a data exercise. After that, I was invited for a phone interview, half HR and half technical. The HR part was standard enough, with a few weird comments about how I wasn't from a target school. During the technical part, I was repeatedly asked trivia questions about topics I didn't claim knowledge of on my resume, and a statistics brainteaser. Questions were poorly communicated, and after asking for clarification, the interviewer raised his voice at me so I ended the call.
Candidatei-me online. O processo levou 2 semanas. Fui entrevistado pela Ginkgo (New York, NY) em abr. de 2017
Entrevista
After applied online, I was scheduled a 3 hour coding test. I signed a NDA and all I can say is that I wouldn’t recommend anyone with less than good-CS-student level programming skills to apply.
I was rejected due to OOP design efficiency and they didn’t bother sending me a rejection until I emailed them.
