Candidatei-me por meio de uma faculdade ou universidade. O processo levou 4 semanas. Fui entrevistado pela Lime Brokerage LLC (Boston, MA) em nov. de 2016
Entrevista
I made it till the second stage. The first stage was a coding challenge on hackerrank. It consisted of 4 questions. The time provided was inadequate for 4 questions. I was able to complete only 3 questions. Nevertheless, I got selected for second round.
Second stage consisted of a video interview on hackerrank codepair with one engineer. I was asked to implement a queue from scratch. However, my friend who interviewed with a different engineer was asked different questions. He did not seem satisfied with my implementation. They did not get back to me initially, but I followed up and they replied saying I was not selected for next round
Outras avaliações de entrevista de vagas de Software Engineer da empresa Lime Brokerage LLC
Candidatei-me online. O processo levou 3 dias. Fiz uma entrevista na empresa Lime Brokerage LLC (Boston, MA).
Entrevista
After applying online got hackerrank next day.
Simple questions about OOPS.
Next day got email from recruiter asking for interview date
I confirmed recruiter's suggested date then no one shown up on interview date
Worst experience ever
Perguntas de entrevista [1]
Pergunta 1
Basic questions on hackerrank. Anyone with Computer's background can easily clear it.
Candidatei-me online. O processo levou mais de 1 semana. Fui entrevistado pela Lime Brokerage LLC (Boston, MA) em nov. de 2016
Entrevista
Hackerrank test screener, seemed a healthy balance of easy/slightly difficult questions. Great as a screener.
Afterwards I was invited to a wordpair session on Hackerrank. There was a snaffu regarding the phonecall, but after that was sorted out, we went to a session where a few quiz questions were thrown out there followed by the code session. quiz questions were basic (tcpvudp, multithreaded experience, etc.)
Now here is why I am writing this review - I had a very rude and arrogant interviewer. In addition to citing things that were wrong (that really weren't) he had an affinity towards ignoring approach and the caveats I would say. Very absolutist in how you are wrong. For example, why use a struct vs. a class? Well I'm in an interview session, I want to make it quick and dirty. It was overall a terrible experience and I know it was a way for someone to feel good about themselves (the interviewer).
I'm genuinely disappointed because everything I read spoke towards the company being a solid employer.
