Screening Round
Questions:
- Discussed the project I worked on, including schema and API it exposes.
- Coding question: Variation of Group Anagrams where we have to handle any symbol.
Candidate's Approach
I provided a solution that the interviewer found convincing.
Interviewer's Feedback
Feedback was positive, leading to scheduling of four more rounds.
First Round
Questions:
- Coding question: Next Greater Element I.
- General questions:
- How do you handle production issues?
- How do you ensure production issues don't impact clients for a longer time?
- Coding question: Search a 2D Matrix II.
Candidate's Approach
I initially provided an O(n^2) approach for the first coding question and then a stack-based approach. For the second question, I started with O(m*n), then O(n log(m)), and added filtering logic but didn't have enough time to present the optimized solution.
Interviewer's Feedback
The interviewer was convinced with my responses, although I regretted not asking for more time to present my optimized solution.
Second Round
Questions:
- Coding question: Shortest Path in Binary Matrix.
- System design: Low-Level Design (LLD) of Cricbuzz, focusing on schema.
Candidate's Approach
No approach provided.
Interviewer's Feedback
The interviewer was supportive throughout the round.
Third Round
Questions:
- Scenario-based questions:
- Any colleague inspires you?
- Any tech challenge you faced?
- Any scenario when your boss changed and how you handled it?
- Any scenario when you missed a deadline?
- How do you handle priority changes?
- Why are you switching jobs?
- Coding question: Variation of Merge Intervals.
Candidate's Approach
I provided a brute force solution followed by the most optimized solution for the coding question.
Interviewer's Feedback
The interviewer provided feedback that I should have asked more relevant questions, as my question about the stage of Oracle Cloud was not well received.
Fourth Round
Questions:
- In-depth resume grilling.
- Scenario-based questions.
- Asked to write code for Merge Sort and replicate a deadlock using threads.
Candidate's Approach
No approach provided.
Interviewer's Feedback
The interviewer noted that I was good at coding but suggested I learn beyond day-to-day work, particularly in DevOps.
Tips
- Always ask relevant questions at the end or inquire about work culture.
- Practice starting with brute force solutions and gradually moving towards optimized solutions.
- Be confident in your abilities.