Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      Twitch

      Fait partie de Amazon

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Twitch | Offres d’emploi chez Twitch | Salaires chez Twitch | Avantages sociaux chez Twitch
      Entretiens chez TwitchEntretiens d’embauche pour Frontend Engineer chez TwitchEntretien chez Twitch


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Frontend Engineer

      19 juil. 2019
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre
      Entretien moyen

      Candidature

      J'ai postulé en ligne. J'ai passé un entretien chez Twitch en mai 2019

      Entretien

      Got a reply next day of application - told to take a test in Codility. Asked to solve 2 tasks within 240 minutes. Scored well, May be missed a few test cases for one task. Filtered to Second round which was a Technical Phone Interview with Coderpad. It was scheduled immediately with no delay after checking my availability. They have changed the schedule twice. Second round was scheduled for an hour. But it lasted for 30-40 mins. Asked few behavioral and a technical question He told recruiter will reach out to you with feedback. Received a mail with no offer after 3 days.

      Questions d'entretien [1]

      Question 1

      Write a function to return if a tic-tac-toe game has a winner or not. Online Codility test : Find and print only if the background color and the text color of a td element in a HTML table are different.
      1 réponse

      Autres retours d’entretien d’embauche pour un poste comme Frontend Engineer chez Twitch

      Entretien pour Frontend Engineer

      27 août 2019
      Candidat à l'entretien anonyme
      San Francisco, CA
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 3 semaines. J'ai passé un entretien chez Twitch (San Francisco, CA) en juil. 2019

      Entretien

      HR call and then a technical with a Senior Engineer. I passed the HR call, and the hiring manager said my technical went well. The senior engineer enjoyed my interview, and provided positive feedback! It was one of the best technical interviews I've experienced, and I enjoyed it too. However, the hiring manager said that they had an offer out for that position before they interviewed me, and it was accepted. He said to let him know if there were any other positions I'd like to apply for, and he would be happy to forward on my profile. He also mentioned that the only positions they had open were junior (SDE1) positions, and asked if I was interested in going that route. Unfortunately, that was the last correspondence I received. I responded saying that I was definitely fine with applying for SDE1 roles, and asked if he could give me a general salary range for that level. I was just concerned about moving to SF on a junior salary, and wanted to make sure I'd be able to keep my head above water. After a few days of no response, I messaged again with a few positions I was interested in, and asked if he could forward my profile for them. A week went by, still no response. I ended up just applying for them. A few days later I sent a follow up email informing him that I had applied for them through the Twitch job board, and asked if he was able to forward my profile. Again, no response. It's been a month, so I've moved on and accepted an offer elsewhere. It's still a bummer because I really like Twitch from a user-standpoint, and was so excited at the prospect of being able to contribute to a product I enjoy using and am a huge fan of. I still like Twitch, and I'll probably apply again after some time. I just wish I knew why they stopped responding to me.

      Questions d'entretien [1]

      Question 1

      Why do you want to work at Twitch?
      2 réponse(s)

      Entretien pour Frontend Engineer

      23 mars 2019
      Employé (anonyme)
      San Francisco, CA
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé via la recommandation d'un employé. Le processus a pris 3 semaines. J'ai passé un entretien chez Twitch (San Francisco, CA) en mars 2019

      Entretien

      Interview was very fast paced, which was a pleasant surprise. After an initial phone call with the HR recruiter, a technical phone screen was set up for the week after. Feedback was provided to come on-site a day after the phone screen, and feedback for the ultimate offer came two days after the on-site. I liked that the on-sites were with my prospective team, and the community felt welcoming. One of my best on-site experiences.

      Questions d'entretien [1]

      Question 1

      Mix of front-end, data structures, and architectural design.
      Répondre à cette question
      2