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

      CitizenNet

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur CitizenNet | Offres d’emploi chez CitizenNet | Salaires chez CitizenNet | Avantages sociaux chez CitizenNet
      Entretiens chez CitizenNetEntretiens d’embauche pour Backend Engineer chez CitizenNetEntretien chez CitizenNet


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

      5 févr. 2020
      Employé (anonyme)
      Los Angeles, CA

      Autres retours d’entretien d’embauche pour un poste comme Backend Engineer chez CitizenNet

      Entretien pour Backend Engineer

      16 oct. 2019
      Candidat à l'entretien anonyme
      Los Angeles, CA
      Aucune offre
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez CitizenNet (Los Angeles, CA) en oct. 2019

      Entretien

      There was a timed, online skills evaluation that was fairly challenging. Then a short, informal phone "screen" which I put in quotes because it was not with an HR person but another engineer, which was nice. During the phone call, we scheduled a 3 hour on-site interview, which seemed intimidating at first. However, when I got there the mood was generally easy-going. I met with the CEO first, then had 2 or 3 separate group interviews. There was some live coding during the interview with the team that the position was for. It felt almost a little more like pair programming (of course with less input from them than the usual pair programming) because it was conversational rather than them giving me a task and just watching and judging me in silence. The people were great, which is why I did take the offer.

      Questions d'entretien [1]

      Question 1

      (something like) What is your debugging process?/What are some tools you use? [job was Python specific]
      1 réponse
      Expérience négative
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 1 semaine. J'ai passé un entretien chez CitizenNet (Los Angeles, CA) en août 2019

      Entretien

      Was initially contacted through Linkedin after submitting my resume to a job posting. They responded immediately with a coding challenge. Passed the coding challenge and they immediately invited me in for a 3 hour interview in person. Was told only 5 out of 100+ people passed the test. 4 engineers from the team interviewed me at the same time. 2 of the interviewees were there via web conference but thought it was pretty important to talk over the two people who were actually in the room with me. They were basically trying to impress each other with their ability to find issues in my code instead of giving me time to look it over. Then they said I didn't know enough about python coding for the job about 20 minutes in. Could have easily done the prompt they were asking for in about 15 minutes if they just let me code instead of breathing down my neck. Generally it seemed as though everyone at this company is overworked but well compensated. They are looking for robots to code, not employees that they will spend 8 hrs/day with 5 days a week for the rest of their career. Every mistake I made in the interview could have been taught and absorbed in 10 minutes. Sociability unfortunately cannot be taught in 10 minutes, but is paid no mind in the interview process here. The relationships between employees seemed pretty strangely strained as well. While chatting about LACMA being around the corner an employee who went to school in India said he had never been there and another jokingly said "I will pay for you to go there so that we can culture you." Yikes.

      Questions d'entretien [1]

      Question 1

      They wanted me to take a function I had written in python in the coding challenge and make it run in the command line with variables inputted in command line. Then wanted to see how I would handle bad status codes and bad requests to the API in the code.
      1 réponse