Round 1: Phone Screening
Questions:
- Leetcode Medium question based on merge intervals. The task was to figure out its relation with intervals as it was just a real number range.
Candidate's Approach
- Explained the approach and defined input/output as a range of floats.
- Discussed edge cases and attempted to draw on a whiteboard.
- Was unable to complete the code, only wrote half, but explained time complexity (TC) and space complexity (SC).
Interviewer's Feedback
- Positive feedback received after 2 weeks.
- Suggested working on time management.
Round 2: Technical Round 1
Questions:
- Leetcode Medium question based on graphs/trees.
Candidate's Approach
- Solved and coded before time.
- Addressed one follow-up question and explained the approach.
- Conducted a dry run and identified missing edge cases, which were added with hints from the interviewer.
Interviewer's Feedback
- No feedback provided.
Round 3: Technical Round 2
Questions:
- Leetcode Medium question based on trees.
Candidate's Approach
- Initially confused about the question due to lack of sample input.
- Tried to clarify by taking multiple inputs and asking the interviewer.
- Coded incorrectly at first but did a dry run to understand the mistake and then coded correctly under time pressure.
Interviewer's Feedback
- No feedback provided.
Round 4: Technical Round 3
Questions:
- Question related to prime numbers (Medium/Hard difficulty).
Candidate's Approach
- Explained the initial brute force approach and then improved it.
- Coded an optimized version but may have messed up the time complexity for the optimal solution.
- The interviewer found the approach interesting and had a light conversation afterward.
Interviewer's Feedback
- No feedback provided.
Round 5: Googliness
Questions:
- Behavioral situational questions.
Candidate's Approach
- The interviewer did not join initially, leading to a reschedule.
- Answered straightforward behavioral questions and engaged in light chit chat.
Interviewer's Feedback
- Feedback was not positive; described as borderline performance.
- Technical rounds did not meet expectations.
- A 12-month cool-off period was suggested.
Learnings
- Need to work on speed and data structures and algorithms (DSA).
- Improve coding logic to achieve optimal solutions in a timely manner.