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

      VIZIO

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur VIZIO | Offres d’emploi chez VIZIO | Salaires chez VIZIO | Avantages sociaux chez VIZIO
      Entretiens chez VIZIOEntretiens d’embauche pour .NET Developer chez VIZIOEntretien chez VIZIO


      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 .NET Developer

      24 juill. 2015
      Candidat à l'entretien anonyme
      Irvine, CA
      Aucune offre
      Expérience négative
      Entretien difficile

      Candidature

      J'ai postulé via un recruteur. Le processus a pris 1 semaine. J'ai passé un entretien chez VIZIO (Irvine, CA) en août 2014

      Entretien

      (From what I remember) Position asked for experience with ASP.NET MVC, C#, SQL, JavaScript, Silverlight, Telerik, WPF. Got interview through recruiter on CyberCoders. First screened over the phone with basic questions like: What is a SPA? What is dependency injection? What are the repository and unit of work patterns? (I knew of these patterns but never used them; I guess my half-baked explanations were good enough.) Receptionist had me fill out form assessing my own skills. (I circled intermediate/advanced for all, but I would probably be more humble next time, since I realize this is probably what these self-assessments actually test. They whiteboard test you anyways.) Interviewed with three devs: the one who phone-screened me, my potential boss (who did most of the talking), and another dev who didn't say a word. We briefly chatted about my resume, then started the whiteboard questions. I got a mix of SQL questions, like how to get certain query results given the schemas for 2-3 tables (joins, CTEs), and C# questions, like how to use interfaces, or the difference between abstract and virtual methods. Did pretty well on the SQL stuff, though I didn't know how to write an imperative loop (I've never needed to, and I only learned later that it's a smell anyway). Did so-so on the C# stuff. They asked how I would write some code so I could easily swap out databases. I knew the boss was asking for DI/Repository/design pattern stuff here; this is where I started to falter. He seemed to be a pattern cultist; I believe patterns are a means to an end, and it depends on the use case. I also told him I tend to program in a simple functional style, and he kind of sneered at that. Interview lasted about 90 min. A few days later the recruiter told me I didn't make the cut for the second round interview with some manager. Based on the interview experience, and the job I got later, I'm kind of glad I got cut.

      Questions d'entretien [1]

      Question 1

      How would you write a class for this model based on the Repository Pattern?
      1 réponse