Me postulé en línea. El proceso tomó 1 semana. Acudí a una entrevista en Top Hat en jun 2018
Entrevista
I had read on Glassdoor that 42% of interviewees had a negative experience with the interview process at Top Hat, but tried to not pay attention to that and experience it myself. And it was exactly what I had read. It was a very rushed phone screen interview. She started the interview with the question "Why Top Hat?" without any introduction about the company and the position. It was like the interviewer was forced to interview me. They were very cliché interview questions such as "Tell me about your previous job?" She asked no follow up questions after I answered her questions. They are focusing that what is important for them is fundamental of computer science. But, when I told her I am very interested in honing my skills in the fundamentals of computer science, she responded that is not important as they do web development. When she asked me if I have any questions, she was answering me with less than a sentence. I felt like she wanted to hang up as soon as she can. When I asked her what made them consider me as a candidate, she mentioned something that was completely false. She clearly did not read my CV.
Overall it was a very bad experience and I felt like they were completely unprepared.
Me postulé a través de una recomendación de un empleado. El proceso tomó 2 meses. Acudí a una entrevista en Top Hat (Remote) en nov 2021
Entrevista
Started with a screening interview where I met with a recruiter, Kelly. She provided a lot of great information and was very transparent throughout the whole process. Went into the two coding interviews feeling very prepared. After the two coding interviews I moved on to a panel-style interview with two managers.
Preguntas de entrevista [1]
Pregunta 1
Three leet-code style problems, front-end pairing interview retrieving info from an API, and a meeting with managers going over employment history.
Me postulé en línea. El proceso tomó 2 semanas. Acudí a una entrevista en Top Hat (Toronto, ON) en ene 2021
Entrevista
I got scheduled an initial phone screen after getting contacted by Top Hats HR. It was a pretty typical phone call, a brief chat about the role and company followed by talking about resume & past experiences and why Top Hat. Scheduled a technical screen by receiving a follow-up email, few days after the first call. The interviewer was helpful but I wasn't ready enough hence I failed at the search algorithm question and did not proceed to backend/frontend challenge. Everyone was responsive and kind throughout the interview process.
Preguntas de entrevista [3]
Pregunta 1
Tell me about yourself? Why do you want to work at Top Hat?
Me postulé en línea. El proceso tomó 1 semana. Acudí a una entrevista en Top Hat (Toronto, ON) en ago 2018
Entrevista
The HR Screening was pretty standard. Was asked basic things such as why I want to join the company, what is my history with software technologies and etc. Just be enthusiastic and honest about wanting to join the company, you'll be able to make through this stage.
The next step was to come onsite for a standard Data Structures and Algorithms session, followed by a backend/front-end pairing session (you can choose between the two). The data structure/algorithm questions were fairly straightforward and I would say at worst leet-code medium. I finished it with ease and they seemed impressed. The engineers were really helpful for this segment and very encouraging. The pairing session was a different story. I managed to complete the task but with little to no help. Every time I engaged them to ask for feedback while I was doing it, they just nodded and said yeah sure. I have no idea what they wanted but in my opinion I feel like I was able to complete the task. A day later I was emailed saying I wasn't a good fit and they were moving forward with other candidates. All in all, I would say the HR process was very smooth and quick, data structures and algorithms portion was also handled well. Perhaps they should move towards a more industry standard of conducting System design questions rather than get people to code up an API in less than an hour.