J'ai postulé via la recommandation d'un employé. J'ai passé un entretien chez Hopin en nov. 2023
Entretien moyen
Candidature
Le processus a pris 2 semaines. J'ai passé un entretien chez Hopin en oct. 2023
Entretien
The interview process was smooth and well-organized, reflecting a keen attention to detail in the company's recruitment efforts. The communication and coordination leading up to the interviews were prompt and efficient, creating a positive first impression.
The technical interview, in particular, stood out as a real highlight of the process. The problems presented were not only challenging but also relevant to the role.
I appreciate the time taken to share insights on areas for improvement.
4 Interviews
- With internal recruiter to check basic qualifications and alignment
- Technical interview involving adding a basic feature to a demo app
- Interview with engineering team manager. Typical interview questions about work history and ending with a systems design whiteboard discussion
- Short interview with CTO focusing on work history and work habits.
Questions d'entretien [1]
Question 1
- What was one of the most difficult technical challenges you solved?
- Why do you want to work at StreamYard?
J'ai postulé via la recommandation d'un employé. Le processus a pris plus d'une semaine. J'ai passé un entretien chez Hopin en juin 2023
Entretien
Very transparent and clear communication throughout. I was introduced to Hopin (StreamYard) via referral. After getting some basic info about the company from my former colleagues, they withdrew from the process and I had blind interviews with other members of the company -- I appreciate the deliberate steps taken to reduce bias. Darren, the recruiter, was super helpful in managing the different interview stages throughout, which was especially challenging as I was travelling and often only had one or two hours of availability each day of the week. He would often respond within minutes of my messages. First technical interview was with an Engineering Manager, questions ranged from explaining previous projects I had worked on, and quizzing the technical complexity of those projects. Couple of questions about other competencies such as incident response, working in a team and maintaining a large codebase too. Second interview was with a staff engineer, it was an applied problem to create a message string with various edge cases around user data, pluralization etc. Question was small enough to explore all complexity in an hour, and had good opportunities to discuss approach. No need for knowledge of algorithms or data structures in this interview. Latter half of the interview there was a system design question with a focus on system components, load balancers, database choices, rate limiting etc. Final interview was with Dan, one of the co-founders. Dan is still very close to the engineering work, cares deeply about the product and is keen to hire people that match the culture that has been built so far. We spoke for around 30 mins. Overall the process took about ten days, and did not contain anything I would not have expected.
Questions d'entretien [1]
Question 1
Q1: Ingest a collection of data, check for some conditions, then produce different output strings depending on the state of the data. Q2: design an API for a like/dislike action on a youtube comment