This is a 55 min automated QA based on an AI engine. It does a good job of doing a basic check on gauging if you have played the role by asking about typical scenarios u would have faced but the choices are ambiguous and without context open to interpretation.
For example a couple of decision making questions have: ẗalk to others before deciding" as a choice. Now if you don't talk to anyone u can be viewed as autocratic and not taking in inputs from others. But u can also view this as your uncertainty/lack of expertise/independence. So to really judge decision making the context of these talks and how they are used in your decision making need to be understood. The questions dont address this at all
How many code reviews to you do in a week? Why is this number high/low? What do u do if there is a problem with the process? Do u interact with other teams? How do u prioritize tasks? How do u make decisions? (ask seniors, talk to others, on your own, etc)
The following metrics were computed from 1 interview experience for the Turing Technical Lead role.
Turing's interview process for their Technical Lead roles is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Turing's Technical Lead interview process.