Turing interview questions

Hands-on, Technical, Very Good. It was proctored. There was a coding challenge, DSA styled. Also, there was an analysis between 2 different codes to determine the more efficient of the 2.

The interview process was structured in three stages. The first round was a screening, followed by a sourcing assessment where I had to demonstrate my skills using LinkedIn Recruiter. The final round was heavily metrics- and numbers-driven — to the point where it felt more like an interrogation than a conversation. Although I was told it would include behavioral questions, none were asked. Instead, the interviewer focused on dissecting every detail of my metrics, even recalculating numbers I mentioned and asking me to explain her results. I also explained that metrics vary across projects, but that didn’t seem to resonate. Overall, the process felt overly rigid and analytical, as if they were looking for someone purely numbers-driven rather than a well-rounded recruiter. It left me with the impression that they value output metrics over collaboration, judgment, or adaptability.