The most difficult questions honestly revolved around my experience as an enterprise staff member, and how ready or willing I was to work in a startup atmosphere. It's not for everyone, and I really appreciate the line of questioning that was open and honest about what to expect.
Q: Is there anyway to construct Dockerfile from running container?
Questões técnicas foram todas respondidas.
I was asked what did I know about the role.
Detalhes Profissionais; Empresas em Quais já Trabalhei
"Tell me about how you used Jenkinsfiles in $previous_employer"
"Talk about the architecture of a service you've worked with"
Do you meet the skill set on this particular job posting?
Case Interview: * What would be your business case to Capital One for moving to the public cloud? * Given a diagram of a basic login service running on-prem, how would you migrate it to the cloud? How would you make it more robust and not prone to errors? What about making this service available on a global scale? * Given the following numbers and usage pattern, what size instance would you use in your autoscaler to optimize the cost of the service during its offtime, while still having enough capacity to handle the peaks.
As an engineering candidate you should have both breadth and depth of knowledge and expertise in your field, so come prepared and be ready to think on your feet and work through whatever they throw at you. Pay attention to the preparation info provided by your recruiter/coordinator. Ask clarifying questions to have a better idea of what topics you should focus on, then put in the time to actually study.
Viewing 841 - 850 interview questions