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 AWS Cloud 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 AWS Cloud Engineer

      1 ago 2018
      Candidato anonimo a colloquio
      Wilmington, DE
      Nessuna offerta
      Esperienza positiva
      Colloquio difficile

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto una settimana. Ho sostenuto un colloquio presso Capital One (Wilmington, DE) nel mese di apr 2018

      Colloquio

      I applied directly online at capitalone.com. Heard back from a recruiter about a week later and he setup a phone screen with one of the managers. Had a 30 minute phone call with the IT manager. We went over my resume and he asked questions about my experience, things I've done in AWS, how I would monitor resources in AWS, and then explained the situation their department was in and what they needed. He was very friendly and personable. Call ended and he let me know that the recruiter would get back to me. A day later I got a call from the recruiter and he let me know that they wanted to fly me into Delaware for an interview. He referred me to their travel agency and I got my flights and hotel booked. I flew out on a Sunday and stayed Sunday night in the hotel. The interview was all day Monday, and I flew out Monday evening. For the onsite interview, I met with 5 people, each for one hour. 9-10, 11-12, then lunch from 12-1. More interviews from 1-2, 2-3 and then 330-430. First interview was a personality test with the interviewer in the room and they asked me about how I would react in certain situations, e.g. what is your typical way of dealing with conflict. Second interview was over skype with somebody in Dallas. This was a technical interview. We went over my resume and talked tech. He explained what his day to day schedule was like, and then we wrapped things up. Lunch was at the cafeteria downstairs, and somebody from HR paid for me. Third interview was over skype again, and another technical interview. Interviewer asked me things about RDS, how I would deploy web applications, if its better to give IAM user credentials or use IAM roles for AWS resources, etc... Fourth interview was in person with one of the Developer managers, and he talked about how the Cloud Engineers worked closely with his team. We went over my resume and talked more tech. Fifth interview was in person, and the person gave me a code sample on paper, and I had to analyze the sample and write a flow chart diagram based on each decision in the code. I think it was a code sample that decided how certain people were selected for a mailing campaign, and I had to explain which people would get which offers by mail. Afterwards I went to the airport and flew home. I got an email from the recruiting office asking me to list all expenses and submit them. I submitted the next day and got a direct deposit credit back within a few days. Two days after I got home, the recruiter called me up and let me know that I was not selected. I was a little sad, I was impressed with the Company and what they are doing in AWS, and everybody that I met seemed really friendly and knowledgeable. Overall a great experience! Everything was taken care of for me and clearly laid out. Very clear instructions on how to get to the office from the hotel, somebody from HR was waiting for me and let me up. There was never any confusion on where I was supposed to go or with whom I was supposed to meet.

      Domande di colloquio [1]

      Domanda 1

      Tell me about a situation in which you had to deal with a very upset co-worker.
      Rispondi alla domanda
      1

      Altre recensioni di colloqui per AWS Cloud Engineer presso Capital One

      Colloquio per AWS Cloud Engineer

      22 set 2018
      Candidato anonimo a colloquio
      Wilmington, DE
      Nessuna offerta
      Esperienza neutra
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura tramite segnalazione di un dipendente. La procedura ha richiesto 2 settimane. Ho sostenuto un colloquio presso Capital One (Wilmington, DE) nel mese di set 2018

      Colloquio

      Had an internal referral for the AWS Cloud Engineer position. Talked with the recruiter quickly just to see if I’d be interested in the position. From there, I had a phone screen with the hiring manager and his boss asking me some basic technical questions (difference between while loop vs. for loop). After passing that, I was invited for an on-site interview. Had 4 rounds of interviews, 2 Job Fit interviews, 1 Behavioral interview and 1 Case interview. The job fit and behavioral interviews had 2 interviewers in the room while the case interview just had one. Job fit just went over my technical skills, coding problem, troubleshooting problem, do I understand what an Ansible role is doing, etc. The behavioral is more communication ability and based off STAR (Situation/Task, Action, Result) pattern. The case interview can really be anything, from a math problem to a coding problem or something in between. I stumbled quite a bit in the case interview, and even though I figured it out in the end I needed a lot of guidance to get through it. Next day, I get a call from the recruiter saying they are passing. I struggled a bit with the troubleshooting portion of the interview (guess the role requires a lot of troubleshooting) as well as the case interview I mentioned above. All-in-all, I’m not upset, but realize that Capital One just isn’t the company for me after not getting an offer 3 times.

      Domande di colloquio [1]

      Domanda 1

      Code the algorithm for figuring out an anagram between two strings
      1 risposta

      Colloquio per AWS Cloud Engineer

      22 mar 2018
      Candidato anonimo a colloquio
      Wilmington, DE
      Nessuna offerta
      Esperienza neutra
      Colloquio nella media

      Candidatura

      Ho presentato la mia candidatura online. La procedura ha richiesto 2 settimane. Ho sostenuto un colloquio presso Capital One (Wilmington, DE) nel mese di mar 2018

      Colloquio

      1. Call with the recruiter to ask about my background. 2. Call with a few hiring managers about my skills for about 30 mins and to see what technologies I worked with 3. On-site interview. There were 4 interviews that were 1 hour each. 3 of them were technical and 1 was behavioral.

      Domande di colloquio [1]

      Domanda 1

      1. There are customers in PA, NJ, and DE. How would I toubleshoot if NJ was complaining about issues. The architecture was the web tier to ELB to application to rds database and we white boarded different problem scenarios. There was also some basic Linux questions 2. interview based on talking about monitoring with New Relic, and Datadog. Nothing really technical was asked except what would I like to be doing on the job. 3. Behavioral interview with basic how did you resolve an issue with another person or with a problem at work. 4. The last technical interview was with 3 people. One guy was on the phone since he had to run some family errand. I started off with my background and they asked me question about my walkthrough process for a database migration and how could I do it with 0 downtime. This was the worst interview out of all. I got cut off by the guy on the phone a couple times when I was answering another interviewers question. One guy even asked if I knew the job required relocation and worried about where i would live. I’m thinking to myself seriously? I obviously know this isn’t remote and yes I’m willing to move close I’m not here for fun.
      Rispondi alla domanda
      1