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

      Spokeo

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Spokeo | Offres d’emploi chez Spokeo | Salaires chez Spokeo | Avantages sociaux chez Spokeo
      Entretiens chez SpokeoEntretiens d’embauche pour Software Engineer chez SpokeoEntretien chez Spokeo


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

      2 nov. 2023
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Spokeo

      Entretien

      Recruiter Round Hiring manager round technical round CTO Basic Javascript let vs var, closure, Basic react question hooks Coding exercise for figma to Html css Coding exercise for Image slider in react Code editor was not working properly

      Questions d'entretien [1]

      Question 1

      Coding exercise for figma to Html css Coding exercise for Image slider in react
      Répondre à cette question
      3

      Autres retours d’entretien d’embauche pour un poste comme Software Engineer chez Spokeo

      Entretien pour Software Engineer

      2 avr. 2021
      Candidat à l'entretien anonyme
      Los Angeles, CA
      Aucune offre
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé via un recruteur. J'ai passé un entretien chez Spokeo (Los Angeles, CA) en mars 2021

      Entretien

      Pathetic Interview process. Recruiter reached out to me via email for an introduction call. I confirmed the interview date and time. 1 minutes before the interview she email me to confirm again. I replied immediately. She did not call me that day. I followed up got no reply from her. After 20 days she reached out to me again. We again confirmed the date and time for a call. Again 1 minute before the interview she changed the meeting date and time to next day without even asking me if I am free. Anyways I was free so I accepted the change. She called and asked egenral questions about my current role and some techincal questions. After few days I received an email for 1st technical interview. On the day of interview the person that joined the call was not the one I was told I will be interviewing with. Even he did not know that this is 1st round of the interview. Then he realized that there has been a miscommunication and started the interview. He asked me about 40 theoretical questions from google in 1 hr and expects you to know everything. What a mess of a company.

      Questions d'entretien [1]

      Question 1

      Difference between var and let. how will you fetch phone number from am text file. what is difference between sql and no sql what happens when you hit google.com on a browser what can you do to load page faster on browser and 40 such questions
      Répondre à cette question
      3
      avatar
      Réponse de Spokeo
      5y
      Thanks for your feedback. We’re sorry you did not have a positive experience. We have taken your comments into consideration and will continue to improve our interview process. At Spokeo, we are constantly reviewing our interview structure, and our goal is to make sure we provide a very positive candidate experience. Again, we appreciate your feedback.

      Entretien pour Software Developer

      17 juil. 2020
      Candidat à l'entretien anonyme
      Los Angeles, 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 Spokeo (Los Angeles, CA) en juil. 2020

      Entretien

      Overall their communication was horrendous: it was a challenge to schedule, the recruiting team was not forthcoming with what I should expect at any stage, I had barely any time to ask questions of them, I was never clear what I would be working on or who I would be working with, and they did not keep their word to get back to me with feedback the day after the onsite - they sent me a form rejection email a week later! I applied for a Senior Software Development role. A recruiter contacted me asking if I would be open to a mid-level position instead. I agreed that would be acceptable and provided a few dates and times when I was available to talk to her about it. It took her several days to get back to me - I had to ping her to ask if any progress had been made because I was booking other interviews during that time. When she scheduled it, I asked what I should expect with no answer. That first phone screen was exclusively her asking me questions most other companies ask in their application ("will you need relocation assistance?", "will you require sponsorship to work in the US?") followed by a barrage of CS and Web development trivia quiz questions (runtimes of different algorithms, differences in types of data structures, to explain closures in JavaScript, etc.) and then asking me to tell her my years of experience with a list of different technologies. She also didn't send me the job description for the mid-level role after I asked for it at least three times. When they scheduled my "tech screen", I was provided a coderpad link, so I assumed I would be doing a coding challenge. I explicitly asked so I could confirm that but received no answer. The developer who interviewed me was nearly 10 minutes late for our call. But he spent nearly the rest of our one hour scheduled time asking me more of those quiz-style trivia questions. It was exhausting. They certainly seemed to care more about what I knew than how I would approach problems. Nearly immediately after that call, I was informed they wanted to move me forward to the "onsite". At no point in either of those calls was there any time to ask them any questions about the company or team I would be working with! The onsite was scheduled and I asked no fewer than 3 times what I should expect to speak about with each of my interviewers so that I could prepare appropriately. I did not get an answer from them until the day before. And then the recruiter told me what turned out to be incorrect information and it was terribly vague: in this order, they were meant to be "algorithms", "coding", "frontend", "get to know more about you" but also "technical" and "hands-on". She also asked me to send her a copy of my resume at this point - the day before the onsite! When I spoke with the recruiter the following day during the interview, I asked her if any of the people I was going to interview with were the manager for this role. She said no, that it was for a new team and the manager hadn't been hired yet, but to ask the next interviewer about it. In that next interview, the person told me they never put new engineering hires on brand new teams. So much miscommunication! My algorithms challenges went well and I felt like I had a good rapport with the interviewer. The frontend challenge wound up being next (not what I had been told - and they also didn't tell me I would be expected to implement a frontend project. I thought it would be more general frontend questions). I couldn't remember anything! After an hour of me struggling through the frontend, I had to move on to a coding challenge with a Developer. The challenge itself wasn't too bad, but I was flustered after the previous interview, and using CodeSandbox was also new to me. I didn't take as much time as I should have to read the requirements and write out pseudocode to approach the problem. The code I wrote was sloppy and I was not proud of it. Finally, I talked with a C-level executive for a non-technical round. Our conversation was genial, but he did ask me a couple of high-level technical questions (how I would address a complaint about the site being slow, where I would look to optimize code, etc.). I was also exhausted by the time I got to him.

      Questions d'entretien [5]

      Question 1

      Two rounds of quiz-style CS and web development trivia questions (see above).
      Répondre à cette question

      Question 2

      In round 1, I got through three algorithm questions: one about traversing a tree, one about reversing the order of words in a string, and one finding a target sum in an array of integers. We did not run the code - I just had to write an algorithm to solve it in the language of my choice. (I chose Ruby because its short syntax and built-in methods make it clean for coding challenges and they are a Ruby shop. He seemed pleased by this choice.)
      Répondre à cette question

      Question 3

      Round 2, create an image carousel in CoderPad using any front-end frameworks I wanted to.
      Répondre à cette question

      Question 4

      Round 3, code up a DeepEqual function using JavaScript in CodeSandbox and it had to pass the provided tests.
      Répondre à cette question

      Question 5

      High-level questions: "What might you do if someone tells you the site is slow?", "How might you optimize code at the application level?"
      Répondre à cette question
      3
      avatar
      Réponse de Spokeo
      5y
      Thank you for taking the time to share your experience in detail. Your experience was not representative of what we think the ideal candidate experience should be. To ensure we consistently deliver a high-quality candidate experience, we have begun taking several steps. First, we are aligning the content of our emails to candidates with our internal interview agendas to ensure that our interviewers and candidates are on the same page as to what topics will be covered during standard scheduled conference call interviews. It is very important to us that all candidates have an accurate understanding of what will be covered (e.g., areas of focus, exercises, case studies) . We are also requiring all of our hiring managers, interviewers, and recruiters to attend an internally-developed Interview Training Workshop. This is not only to help us all align on what each person’s role in the interview process is, but also how candidates are walked through Spokeo’s selection process. The Interview Training Workshop also teaches our hiring managers, interviewers, and recruiters how to internally communicate new information that comes out of the interview process to ensure that both sides (candidate and company) stay informed and are able to keep discussions moving forward toward a decision point. Candidate experience at Spokeo remains an area of continuous improvement, and we’re committed to ensuring we create the best and most consistent experience possible. Again, we appreciate your feedback.