After an initial phone interview, I had a technical interview with a lead engineer.
First half, he described the company and role, second half was technical problem solving questions. I found the problem solving questions to be quite tricky, but doable if you memorise your data structures and when to use them, and their associated time complexities.
The interviewer clearly did not want to be there, and it made me pretty uncomfortable throughout. I could tell that I did not pass the interview pretty quickly.
What does it mean to "index" a database?
Problem-solving questions with arrays (no coding required, just explanation).
Time complexity of hash table and binary tree operations to follow up to the solutions to the problem solving questions.
The following metrics were computed from 6 interview experiences for the Smartsheet Software Engineer role in United Kingdom.
Smartsheet's interview process for their Software Engineer roles in the United Kingdom is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Smartsheet's Software Engineer interview process in United Kingdom.