Real, anonymous reports from people who interviewed for Software Engineer at Turing, newest first and distilled into what to expect across the loop.
I started with an HR conversation that was mostly motivational and personality-focused, with general questions meant to get a sense of how I think and how I work. After that, I moved into the technical part where I had to complete coding exercises.
I didn’t get much detail beyond the high-level structure of the hiring process. What I was told matched a fairly standard pattern: they focused on my skills and background, including experience and education, and then they moved toward a decision that resulted in either a shortlist or a rejection.
The interview process typically starts with an HR conversation followed by technical assessments, often progressing from basic questions to more complex coding challenges. Candidates noted a clear structure that transitions from screening to technical depth, with a mix of coding and conceptual discussions throughout.
Candidates experienced a variety of coding challenges, often including LeetCode-style questions and live coding sessions that escalated in difficulty. The coding assessments were designed to evaluate both problem-solving skills and coding proficiency in chosen programming languages.
Interviews often included questions related to full-stack development, particularly with Java and Angular, as well as system design discussions that emphasized trade-offs and architectural thinking. Candidates were expected to demonstrate their approach to real-world scenarios and system-level considerations.
Behavioral interviews assessed candidates' motivations, experiences, and cultural fit within the company. These discussions often followed technical rounds and focused on how candidates handle challenges and work collaboratively.
Candidates noted that communication about their progress was sometimes lacking, especially if they were not shortlisted. However, those who progressed received timely feedback and insights into the next steps, contributing to a more transparent experience.
Interviewers often applied time pressure during coding sessions, which some candidates found challenging. The overall difficulty varied, with many reporting a gradual increase in complexity throughout the interview process.