Candidatei-me online. O processo levou 4 semanas. Fui entrevistado pela Streamlabs em abr. de 2019
Entrevista
After a quick phone call with an HR person, I was asked to make a 4-8 hour assignment. After completion, there was a silence for two weeks and after asking what is the status, I got a generic decline message within minutes.
Definitely, don't recommend working on the assignment!!!
Perguntas de entrevista [1]
Pergunta 1
StreamerEventViewer (SEV)
Introduction
In this coding assignment, you will be building a backend web application which will help its audience see their favorite streamer's Twitch events in real-time. Detailed specifications along with some other helpful information is provided below. Goodluck!
How to approach this and logistics
You are not expected to (cumulatively) spend more than 4 hours on this task. These 4 hours can be spread over multiple days within a two week timeframe. You can start whenever you like. Please make reasonable assumptions and design choices where you feel the specification is unclear or falls short. Make sure to document your assumptions and design in the README or other relevant documents you produce (e.g. code comments).
To help you make these decisions, keep in mind that we ask candidates to complete these coding assignments in order to:
Gauge your technical strength and ability to work independently
Ability to navigate third-party interfaces (libraries/apis) where the documentation/spec might not be very detailed
All work you do will be your property; we are not trying to get free work done here. A couple hundred people have done this assignment previously (some are part of our team now!) and this functionality is live in our product(s).
We are expecting two things from you:
Link to live demo (heroku tends to be pretty easy/free and is used by most people)
Link to git repo (Github is a famous choice) consisting your source and README
Specifications
You are required to build an application which exposes two simple pages to the browser
The first/home page lets a user login with Twitch and set their favorite Twitch streamer name. This initiates a backend event listener which listens to all events for given streamer.
The second/streamer page shows an embedded livestream, chat and list of 10 most recent events for your favorite streamer. This page doesn’t poll the backend and rather leverages web sockets and relevant Twitch API.
Additionally please answer following questions at the bottom of your README:
How would you deploy the above on AWS? (ideally a rough architecture diagram will help)
Where do you see bottlenecks in your proposed architecture and how would you approach scaling this app starting from 100 reqs/day to 900MM reqs/day over 6 months?
Goodluck! And please feel free to ping us if you have any questions. We looking forward to having you on-board our team :)
Candidatei-me online. O processo levou 4 semanas. Fui entrevistado pela Streamlabs (Vancouver, BC) em set. de 2023
Entrevista
Applied through the website, got an email for a 4 hour assignment the next day which can be found on the github. Got a technical interview next week and another Panel interview with 6 different people. All of those were really nice and thoughtful in the interview process.
Perguntas de entrevista [1]
Pergunta 1
Technical: Why a query of a database might be slow? What you do to prevent deadlock in database? What you do if a lot of requests are made to website and you have one instance of it?
Candidatei-me online. O processo levou 2 semanas. Fui entrevistado pela Streamlabs em jan. de 2022
Entrevista
The interview process was actually very practical and not filled with the leetcode unnecessary questions.
The stages were:
1. Initial Screening
This is just to make sure individuals are good. Not to waste each other's time. Some generic questions about programming, databases, query and among others.
2. Take home assignment
The take home assignment was very practical. They are a streaming company so the assignment was about streaming statistics. However for this role, the didn't pay much attention to the frontend so even simple html and css suffix. I like this approach as compared to leetcode since you can actually display your programming skills and experience.
3. Main technical Interview
This is the last technical interview if the home assignment goes well. They discuss the home assignment and also some system design questions. No code at this stage, basically system architecture, tools that will be used, etc... It was enjoyable because it touched lots of my experience in real life.
4. Panel Interview.
This is more behavioural. Getting to this stage is very good since you are just a couple of inches away from an offer. Nothing technical at this stage, just chatting with PMs and fellow developers about situational and professional life.
Perguntas de entrevista [1]
Pergunta 1
I can't list actual questions but just hints:
1. No about database indexes especially composite indexes.
2. Be able to explain your take home assignment and why some decisions were taken.
3. Optimizing backend for better performance.