It was a few generic job interview questions, such as "Tell me a little bit about yourself" and "What was your biggest challenge in your career?" But the main point was the analysis of a simulation of a real scenario, where we had a discussion about some architectural points to cover for a new hypothetical requirement.
What is infrastructure-as-code? Can you describe it?
What is Git? What are common Git commands you would use?
Why choosing Collibra ?
Describe a difficult technical problem that I solved
Do you know how to use ansible.
HireVue was STAR Qs and Games. Technical for cloud engineer had recognizing recursive problem, and asking cloud architect question.
For the technical interview Mainly basic Linux and AWS related questions. I would say if you have an RHCSA level understanding of Linux and an AWS Associate level understanding of AWS these should be fairly straightforward with little curveballs. For non-technical interviews, really express your style of work, how you work within a team environment, why you want to work at Mission and the role you are pursuing.
Company outlook and expections from new hires
Experience with AWS core services. A lot of scenario based questions as you should expect from a consulting role
Viewing 1951 - 1960 interview questions