Most questions revolved around the technical exercise (explain your design decisions, what do you like best about your design, what would you improve if you had more time, how about if we wanted to do XYZ?). Particular questions from other parts of hiring process do not stick in my mind since these were more like natural, informal chats rather than rigid Q&A.
Normal - Nothing out of box.
How would to solution for a problem you do not have any expertise in?
During the case study presentation, you will want to justify and have an answer to why you made certain design decisions for the solution.
Given questions based on scenarios, need to be strong in gathering project requirements from customers and have to be well versed in AWS services to provide optimal solutions to customers.
Questions were relative and somewhat difficult to answer. Many were actually bundled together and lengthy spanning different subject matter within the same ask.
What will be the biggest analytical challenges you foresee in the shift from the client-side to the vendor-side of a business engagement?
What were some touchpoints for procurement to other functional areas?
What makes Mavens unique and what do you envisage doing day to day?
What is the methdology you did analysis with?
Viewing 1211 - 1220 interview questions