Passa al contenutoPassa al piè di pagina
  • Lavori
  • Aziende
  • Stipendi
  • Per le aziende

      Migliora la tua carriera

      Scopri le tue potenzialità di guadagno, trova lavori da sogno e condividi approfondimenti su lavoro e vita privata in forma anonima.

      employer cover photo
      employer logo
      employer logo

      Capital One

      Azienda coinvolta

      Circa
      Recensioni
      Stipendi e benefit
      Lavori
      Colloqui
      Colloqui
      Ricerche correlate: Recensioni su Capital One | Offerte di lavoro di Capital One | Stipendi di Capital One | Benefit di Capital One
      Colloqui di Capital OneColloqui per Lead DevOps Engineer presso Capital OneColloquio di Capital One


      Glassdoor

      • Chi siamo
      • Contattaci

      Aziende

      • Account Business gratuito
      • Spazio per le aziende
      • Blog per le aziende

      Informazioni

      • Aiuto
      • Linee guida
      • Condizioni d'uso
      • Privacy e scelte pubblicitarie
      • Non vendere né condividere le mie informazioni
      • Strumento per l'accettazione dei cookie

      Lavora con noi

      • Inserzionisti
      • Carriere
      Scarica l'app

      • Cerca:
      • Aziende
      • Lavori
      • Località

      Copyright © 2008-2026. Glassdoor LLC. "Glassdoor," "Worklife Pro," "Bowls" e il relativo logo sono marchi registrati di Glassdoor LLC.

      Aziende seguite

      Non lasciarti sfuggire opportunità e informazioni privilegiate seguendo le aziende dove vorresti lavorare.

      Ricerche di lavoro

      Ricevi suggerimenti e aggiornamenti personalizzati avviando le tue ricerche.

      Colloquio per Lead DevOps Engineer

      10 ott 2024
      Dipendente anonimo
      Ciudad de Mexico
      Offerta accettata
      Esperienza positiva
      Colloquio facile

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso Capital One (Ciudad de Mexico) nel mese di set 2024

      Colloquio

      Proceso con varias entrevistas: la inicial con IT recruiter en español e inglés hay que compartir la experiencia laboral, al igual que cuales son tus expectativas y salario. Después se mencionan los beneficios que da la empresa y el proceso a continuar puede tomar entre 2 a 4 semanas, Hay una prueba tecnica como leet code y entrevista tecnica.

      Domande di colloquio [1]

      Domanda 1

      ¿Cuentas con la experiencia buscada según la descripción del puesto?
      Rispondi alla domanda

      Altre recensioni di colloqui per Lead DevOps Engineer presso Capital One

      Colloquio per DevOps Lead Engineer

      23 gen 2025
      Candidato anonimo a colloquio
      Ciudad de Mexico
      Offerta rifiutata
      Esperienza positiva
      Colloquio difficile

      Candidatura

      Ho sostenuto un colloquio presso Capital One (Ciudad de Mexico)

      Colloquio

      Un proceso muy largo, ellos lo llaman como PowerDay, era en esquema Hibrido, sin embargo los reclutadores lo hacen muy ameno. Estan atentos a todas tus dudas, así como también a poder agilizar procesos.

      Domande di colloquio [1]

      Domanda 1

      Proyectos mas importantes con AWS. Como se gestiona el personal en remoto
      Rispondi alla domanda
      1

      Colloquio per Lead DevOps Engineer

      11 mag 2023
      Candidato anonimo a colloquio
      Arlington, VA
      Nessuna offerta
      Esperienza neutra
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura tramite un selezionatore. La procedura ha richiesto 4 settimane. Ho sostenuto un colloquio presso Capital One (Arlington, VA) nel mese di mag 2023

      Colloquio

      Recruiter reached out through LinkedIn. Had a phone conversation and then referred me to another recruiter to continue with the process. Second (became main) recruiter, had a call with me about the process and sent me the CodeSignal assessment information. Both recruiters were very kind, helpful, and respectful people. After passing the CodeSignal assessment (I believe you need like 700/1200 to pass) they set up a grueling session of back to back interviews in what they call "Power Day." That's a full day of interviews over Zoom one after the other. They switched the last interviewer at last minute to somebody in the position that I was interviewing for. The PowerDay was horrible. Clearly, none of the interviewers read my resume. They had no idea of what I had done before, they didn't know the programming and scripting languages that I was familiar with. They mainly care about Python and JavaScript frameworks like Angular, React. They really should do away with PowerDay. First Interviewer (Principal level - Technical) was kind and respectful. The interview was pretty much a good one except for the fact that it was referencing programming languages and tools that I told them throughout the process that I didn't use before. Second Interview (Behavioral - Sr. Manager and Manager) was your typical interview on "what would you do" or "have you faced" questions. Overall good interview and people were very kind and respectful. Third interview (Case - 1 Manager), was the part where I actually felt like I had fun. It was more of measuring how you process things and your logic and math. Good interview, very kind and respectful. Fourth Interview (Technical - person at position level) was horrendous. Very disrespectful, constantly interrupting, rolling their eyes, raising their voice. I honestly don't know how this person is a leader. It is clear that this person is very familiar with doing the same thing over and over again; however, had no patience when somebody with a more diverse background needed to explain why things were done differently, or used different tools or a combination of them. Came to a point where the person even raised their hands and literally asked: "Are you making stuff up? Why are you bringing up, X tool or Y programming language? That's not how things are done! That company is garbage." At this point, I knew that even if I received an offer, I would not take it. If this is the type of person that I would be dealing with every day, it would be very toxic. By the end of the day I was emotionally and physically drained. With knee and back pain from all the straight sitting in front of the computer. I hope this level of details can help others get through this absurdity of a process. In the end, was told by the recruiter that even though the Hiring Manager liked me, they were going for other candidates with experiences that match their processes more.

      Domande di colloquio [5]

      Domanda 1

      Code Signal 2 easy 2 medium - 70 minutes
      1 risposta

      Domanda 2

      PowerDay: 1. First Interview: a. Find errors in Dockerfile, suggest changes b. Write code to get data from logs file: ..1. Amount of logs ..2. Errors and what can be learned from them ..3. All prices for a specific month
      1 risposta

      Domanda 3

      Power Day: 2. Second Interview: a. Example when you challenged the way things are done b. How you overcame an obstacle at work c. What did you do when work tried to assign you more work than you can handle.
      1 risposta

      Domanda 4

      Power Day: 3. Third Interview: a. Calculate if the budget for performing tests is enough based on some tables b. What would you recommend as an improvement to their testing process. Especially if you have more budget than needed for their current plan.
      1 risposta

      Domanda 5

      Power Day: 4. Fourth Interview A plethora of in depth (very specific details) technical questions related to Software Development and DevOps Pipelines like: a. How to use Git b. How to create pipelines c. How do you test software in the pipelines (how do you configure it) d. How do you set pipeline and repository permissions (how do you configure it) e. How do you create repositories (how do you configure it) f. How do you set up Jenkins jobs (how do you configure it) g. How do you do performance testing (how do you configure it) h. How do you solve conflicts between developers and their codes (how do you configure it) i. How do you process and consume logs (how do you configure it). Which tools have you used? j. Have you had a P1 (production emergency) and are you used or OK with working late (past midnight) k. How do you troubleshoot network issues or even switch to disaster recovery or another region l. etc.
      1 risposta
      4