Typeform Backend Engineer Interview Questions
& Process

Common steps. Test case, infra design. People were very nice even that they left the company. Common whiteboard with multiple improvements to be made while talking. It was just to know your thinking.

The process started with a recruiter call, followed by a technical interview. This technical part had two phases: first, a 60-minute system design session, and second, a pair programming exercise. The entire journey from the initial LinkedIn contact to the end of the pair programming took 76 days. This duration included holidays like Christmas and New Year, but the candidate felt it was excessively long. Communication with the recruiter was problematic, with slow feedback and the need to constantly follow up for updates, indicating a lack of transparency and respect. Ultimately, the application was not moved forward. The feedback mentioned insufficient knowledge in data structures, time/space complexity, and not being quick enough with solutions. While feedback was appreciated, the comment about speed was disliked due to the absence of defined expectations for solution pace. The candidate opted to solve the problem incrementally, demonstrating TDD, which seemed to be undervalued. The interviewers in both technical stages were noted as friendly and the discussions flowed well.

I went through a 3-phase interview process. The first round was a System Design interview, the second was a Live Coding session, and the third was a Behavioral Interview. Before the first interview, I was sent some videos about Google system design interviews, but they weren't really relevant to the actual interview question. After the live coding round, I was told to read the 'Cracking the Coding Interview' book, and then I didn't hear back from them.