Question d’entretien chez Streamlabs

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 :)