Recruiter reached out via LinkedIn. We scheduled a first round “behavioral” interview, and that was followed up with a live-coding “technical” interview, where I was apparently expected to read the mind of the interviewer. He would act annoyed when I didn’t do exactly what he wanted or expected to see. His coding challenge was full of weird peculiarities, some of which are absolutely bad practice for good coding standards. They ghosted me for 2 weeks and then finally let me know they didn’t want to move forward. Total waste of time, but it’s a blessing in disguise. Just look at their employee reviews. Not good, and that’s an understatement.
Perguntas de entrevista [1]
Pergunta 1
The coding “challenge” involved a “Joint” class (for rotating robotic arms?), and he derived the example class from std::vector. This is horrible practice, and shouldn’t be done. You should favor composition over inheritance. I pointed that out and he didn’t like it I guess.
