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

      Stack Overflow

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Stack Overflow | Offres d’emploi chez Stack Overflow | Salaires chez Stack Overflow | Avantages sociaux chez Stack Overflow
      Entretiens chez Stack OverflowEntretiens d’embauche pour Full Stack Software Engineer chez Stack OverflowEntretien chez Stack Overflow


      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 Full Stack Software Engineer

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

      Candidature

      J'ai postulé en ligne. Le processus a pris 3 mois. J'ai passé un entretien chez Stack Overflow en oct. 2018

      Entretien

      Generally: I feel really confused about the whole process. I'm not sure what is happening in StackOverflow right now, but I didn't feel like I was treated as an individual in a recruitment process (more like I was just being thrown at interviewers and one of many being interviewed). I applied online around August and around 1,5 months later got an invitation to phone screen (no information throughout this time, apart from automatic email after applying). I was able to pass all the technical interviews and was only one interview away from being hired (VP of engineering talk), according to StackOverflow procedures. All the interviews (6 total) were really amazing. My interviewers were helpful, professional, made me feel comfortable from the beginning of each talk. Essentially - everything was as in articles about SO interviewing process. Solutions are presented in Google Doc, you start with small talk about your projects to get you comfortable, solve the task and can ask as many questions as you want afterward. The code is written in a language of preference, as long as it is feasible for the task (I used Typescript) All the interviews were boolean-based to my knowledge, so if I failed on any of them, I'd be immediately rejected. I made through all of the "test" interviews, though. On the other hand, all the stuff that happened besides the interviews was ONE BIG MESS. The whole process took nearly 2,5 months (and only partially due to my unavailability - I had holidays in the meantime) and almost never I got feedback immediately (or in following days) after each interview. Even when interviewers told me that I'd be contacted in no more than 24 hours (which happened at least two times), I was contacted in no sooner than 1-1,5 weeks. StackOverflow HR team was not very responsive - I contacted them directly about the process two times, requesting any information when I thought I waited for too long already. I must admit, they were very professional when they finally replied (but still - it's not an excuse, in my opinion). The emails were mostly straightforward and similar to each other - information about my next interviewer, link to Greenhouse availability chart etc. No explanation for delays. All in all, after nearly 2 weeks of not getting any response, just around a week before Christmas 2018, I got an email from HR supervisor (she was always in CC of any correspondence with SO) that I didn't get the position. Again - the email was really professional and well-written, but it didn't cover anything that was really important for me - why I got rejected, what could I improve etc. So, in a follow up email, I directly asked about those (I'm really into self-development) - feedback from my interviewers, information on what could I improve in the future, what direction may I take in order to become a better programmer in their opinion - I did not get any response till moment of writing. A few words on each of the tasks: - Phone screen question and "hard coding" tasks seemed easy for me as I like algorithms and optimizing the code. - HR interview. Mostly about beliefs, skills, and goals for the future. I felt engaged and taken care of. Generally - it felt more like a casual talk than a serious interview but was really well-structured. - The hard-coding task was rather easy (for someone knowing data structures and algorithms), made it to the end before time. The interviewer was really helpful and engaging throughout the whole task. - Architecture interview was the only one based on hard skills (SQL knowledge), so I thought failed, as I haven't used SQL for a long time (I wasn't able to conjure proper selects), but still knowing SQL possibilities and the way one designs database schemas, it seemed I was able to pass - I still designed the whole database model, explained how would I poll the data using pseudocode and wrote a bit of front-end code. This was still the hardest interview for me, though. - Product interview was the one I felt the least stressed about. The interviewer was a really nice guy that guided me through the whole process and signaled if I went too far into details or drifted away from the core concept. - The last interview I had was more of a talk with the engineering manager. Felt like a casual talk, I could ask a lot of questions and tell about my expectations etc.

      Questions d'entretien [5]

      Question 1

      Simple coding task: write a compression algorithm (Run-length encoding)
      Répondre à cette question

      Question 2

      Hard coding task: Write a method that returns a list of permutations of the stringHard coding task: Write a method that returns a list of permutations of the string
      Répondre à cette question

      Question 3

      Architectural task - design DB model and an app that would allow for tracking results of ping pong games. Assume that teams are changing. Design the solution in a way that it will allow for building comprehensive reports (number of total wins and losses for the person and the team, win/loss ratio etc).
      Répondre à cette question

      Question 4

      Product interview: How would you design one-click buy button like the one Amazon has?
      Répondre à cette question

      Question 5

      Engineering manager interview: More of a talk. I was asked what teams I'd like to work with (and given all the openings information), what are my preferences etc.
      Répondre à cette question
      4

      Meilleures entreprises pour « Rémunération et avantages » près de chez vous

      avatar
      Amazon
      3.7★Rémunération et avantages
      avatar
      Google
      4.5★Rémunération et avantages
      avatar
      Amazon Web Services
      3.9★Rémunération et avantages
      avatar
      TikTok
      3.6★Rémunération et avantages