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

      Capital One

      Employeur impliqué

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Capital One | Offres d’emploi chez Capital One | Salaires chez Capital One | Avantages sociaux chez Capital One
      Entretiens chez Capital OneEntretiens d’embauche pour Data Engineer chez Capital OneEntretien chez Capital One


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

      18 août 2016
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience négative

      Autres retours d’entretien d’embauche pour un poste comme Data Engineer chez Capital One

      Entretien pour Data Engineer

      1 juin 2026
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre
      Entretien difficile

      Candidature

      J'ai passé un entretien chez Capital One

      Entretien

      Having completed the entire process yet, but the recruiter and coordinator have been pleasant to work with. They give you tips and tricks to complete for OA and their powerday.

      Questions d'entretien [1]

      Question 1

      2 leetcode easy/medium, 1 lc hard, 1 lc hard, 2d matrix
      Répondre à cette question
      Entretien moyen

      Candidature

      J'ai postulé en ligne. Le processus a pris 2 semaines. J'ai passé un entretien chez Capital One en août 2016

      Entretien

      I applied late at night a few weeks ago, and was woken up next morning by a very enthusiastic recruiter. I told her to call me back in 30 minutes as she had just woken me up, and I needed to think straight. She called me back promptly, and we spoke for about an hour. She explained the process and said that she'd be submitting my resume to some panel and one of the teams might select my resume to move ahead. Next day comes around, and the AML (Anti Money Laundering) team has selected my resume. We decide on availability and a date and time is set. 3 PM EST. And I'm in CA, so it's noon for me. Noon comes and goes and no call. I email them to find out that the Software Engineer got pulled into a meeting and would call me at 4 PM PST. I already had a bad feeling, but could do nothing, because I was going on vacation and wouldn't be back till next week. The risk of a 4 PM interview was obvious. It's the time when work is winding down and people wanna go home. Rather than postpone, since I was all prepped and ready, I said 4 PM is fine. An Indian guy calls, and without really asking about my resume, dives into the first (and only) technical question: If I have a table with columns a, b and c, how can I get the following counts: count of all a's where a is null, b's where b is null and so on for c, a and b, b and c, a and c and a, b and c, in a single scan of a table. I immediately think of the CASE statement. I mess it up a bit by not quite remembering that we can do a COUNT(CASE(... )), but I get there, and he's like, "No". I'm trying to think aloud and give him answers, but he said it wouldn't work, and just kept quiet. In fact, after telling him my solution, he was quiet for so long that I thought the line had gotten disconnected. He then asked me stuff about my resume, and what I'd done. But that question kept gnawing at me because I knew I was at least half-right, if not more, and I knew I was losing him, and so I said, "Can we go back to the question?". He said okay, and then I told him that we could do a COUNT(CASE()) and get his results. He still said nothing more than, "It won't work". Then he said, "Okay, what if there were many columns, and they kept changing. You wouldn't change your query right? How would you do this programmatically?". So I said, I would query the metadata to get the basic row count information, and the number of columns. Once you have the number of columns, you can form your query for each column and run that to get your counts. Silence. I said, "Uhm.. Hello?". He said, "It's okay. Do you have any questions for me?". By this time, I'd lost all interest in the interview myself, but asked him, "Sure! What does you team do?" Typically, this would involve telling the candidate what the team does at a high level and then drill down in the technicalities, if need be. He said, "We perform aggregations on Hive and we use Java and Python, but mostly Java." Not quite what I was expecting, but I was like, "Whatever". The call ended and so did my misery. I had very serious thoughts of emailing the recruiter and withdrawing from consideration. I wouldn't have wanted this kind of team/team mate. However, since I was going on vacation, I just waited instead for the rejection email to come. It duly arrived on Monday, and yesterday, the very friendly recruiter called me to give more feedback and after she was done, I unloaded on her and told her pretty much whatever I've typed here, and said that I don't think I'd want to apply to Capital One again given this experience. Once bitten, twice shy and all. She apologized for the negative experience and thanked me to bring it to her attention. Not sure if she'll actually tell the team, but I couldn't care less. I'm done with this company.

      Questions d'entretien [1]

      Question 1

      If I have a table with columns a, b and c, how can I get the following counts: count of all a's where a is null, b's where b is null and so on for c, a and b, b and c, a and c and a, b and c, in a single scan of a table.
      Répondre à cette question
      10

      Entretien pour Data Engineer

      26 mars 2026
      Employé (anonyme)
      McLean, VA
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Capital One (McLean, VA)

      Entretien

      too technical but covered all grounds, enjoyed the process. It kinda boosted my expectations, which is rare. Was stuck at a point and the hiring manager was kind enough to help me a bit, was nervous but hopefully everything went amazing.

      Questions d'entretien [1]

      Question 1

      AWS lambda, Glue related questions. some on SQL, python
      Répondre à cette question
      1

      Entretien pour Data Engineer

      10 janv. 2026
      Employé (anonyme)
      Plano, TX
      Offre acceptée
      Expérience positive
      Entretien facile

      Candidature

      J'ai passé un entretien chez Capital One (Plano, TX)

      Entretien

      The interview was pretty straight forward, completely on aws , snowflake, python, pyspark, databricks, agile. two rounds, one round with manager and one round with director. With manager techincal and director - about role and behavioural

      Questions d'entretien [1]

      Question 1

      Technical side , aws and snowflake
      Répondre à cette question