After the live coding, I was congratulated on its success and asked for references to proceed with an offer. However, a few days later, I was contacted again stating that the live coding was not actually successful and I would not receive an offer.
The recruiter emphasized that the most important aspects of the interview were demonstrating collaboration, receptiveness to feedback, and adherence to Test-Driven Development (TDD). The engineers advised me not to worry about completing all three questions but instead to focus on listening to their feedback and solving the problems appropriately.
I received some vague oral feedback from the recruiter, stating that I failed because I appeared unsure about React's functionality, requiring me to search for information during the live coding session. Additionally, I did not complete all three exercises.
I can only assume that a better or more cost-effective candidate emerged later. Regardless, it was highly unprofessional to be informed that I had passed the interview and would receive an offer, only to have that statement withdrawn.
In general, the interview process exhibited signs of disorganization. Some of my questions regarding the role remained unanswered, and I was contacted about the same matters by multiple individuals who seemed unaware of each other's communications.
How do you ensure your code is maintainable and readable?
How do you test your applications?
What do you consider your strengths and weaknesses?
The following metrics were computed from 1 interview experience for the Typeform Software Engineer role in Italy.
Typeform's interview process for their Software Engineer roles in Italy is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Typeform's Software Engineer interview process in Italy.