
Turing Frontend Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 15 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Turing.
Front End Developer
I found out about Turing from an email and thought it was a great place for remote jobs. There are tons of US jobs on Turing, so you're really likely to find something. The automated vetting process has a few parts. After you sign up, you pick the technologies you want to be tested on. I went with Python, React, Node, Rust, and some soft skills. The first part has a bunch of MCQs, they're pretty tough but as an experienced dev, I found them pretty straightforward. What's cool is they cover a lot within each tech you choose: data structures, algorithms, problem-solving, testing, debugging, and how the tech works internally.
- Questions about problem solving
- Questions about React
- Questions about JavaScript
Frontend Developer
During the hiring process, the company's portal is used, which you must keep updated, and complete some tests. You keep your data there for months and don't get any response for a long time. After that, they conduct an interview, which is not related to any specific opportunity, just to talk about the process, and when you get to interview with a client, there's no feedback. Exhausting process with no results. The whole process is done in English.
- Introductory interview phase: questions about experience, projects, and workflow.
- Client interview: specific questions about project scope and technical questions about the chosen programming language.
Frontend Developer
They have a pretty long process, but if you get past the initial stages, there are fewer rounds. It starts with contact through LinkedIn, then an initial interview with a headhunter that lasts about 20-30 minutes. After that, you register on their platform, which is quick. Then comes a technical interview with a live coding challenge that lasts for an hour. That was the toughest part for me; I had to deal with someone who was not a native English speaker and had a really bad accent, plus their microphone was terrible. Not only was their voice muffled, but I could barely understand anything they said, even though I'm used to working with international teams. To make things worse, the person sounded annoyed that I couldn't understand them. It's like, if you're going to work remotely, at least invest in decent equipment. There were also some tricky challenges with gotchas. If you somehow get through that whole ordeal, there are still client interviews and other things afterward.
- Can you tell me about your current skills, your experience, and your previous jobs?
- Could you explain the differences between the virtual DOM and the DOM?
- We have a live coding challenge for you: please reverse a string, but only its alphanumeric characters, leaving special characters as they are.
Turing Frontend Engineer Interview Questions
Quoted word for word from Turing interview reports.
“What is the minimum path of a BST?”
Read reports →“Could you explain the differences between the virtual DOM and the DOM?”
Read reports →“How would you create a counter component in React?”
Read reports →“What are React states and how are they used?”
Read reports →“How to create functions in TypeScript using pre-designed HTML code provided by them.”
Read report →“Can you explain React hooks?”
Read report →“Did you pass the React hooks test?”
Read report →“Are you worried about the React class test?”
Read report →“What is your desired monthly salary?”
Read report →Formats, difficulty and experience
Across all 15 Turing interview reports.