Feedback about Intergalactic Thunderstorm (the interviewee)

## Areas of Strength - Strong ability to handle complex, multi-part questions without getting intimidated - Good at clarifying the problem before diving in — asked the right questions to understand direction - Communicated well throughout — able to talk through the problem line by line - Showed awareness of efficient data structures — was moving in the right direction with hash sets and hash maps - Noticeably stronger on the second question — shows the ability to ramp up mid-interview --- ## Room for Improvement - Got bogged down on the first question — made assumptions instead of asking clarifying questions upfront, particularly around duplicates - If a question is unclear, keep asking until it fully makes sense — diving in without understanding the problem will hurt more than the time spent clarifying - For a senior role, always lead with the most efficient solution rather than defaulting to brute force — before writing anything, ask yourself if there is a more optimal approach available. Only walk through brute force if it is a necessary stepping stone to get to the efficient solution - Problem decomposition needs work — break the question into smaller pieces before jumping to code. A consecutive sequence has a start and an end — working backwards from that insight leads naturally to the right data structure - Do not overcomplicate the data structure choice early on — in most cases a set or hash map is the right starting point before reaching for graphs or more complex structures - Do not run the code until you are 95% confident it will work — at the senior level the expectation is that you trace through the solution line by line mentally before executing. Running it to see what happens signals a lack of confidence and interviewers do take note of it --- ## Things to Do Differently in the Next Interview - Always ask clarifying questions upfront — especially about edge cases like duplicates - If you do not understand the question, keep asking until you do. It is completely acceptable and expected - Before diving into code, check in with the interviewer — say something like "I think I am ready to go, am I heading in the right direction?" Read the room and adjust based on their tone and body language - If you feel the interviewer nudging you in a direction, follow it. You can even ask directly — "It seems like I may not be going the right way, should I rethink this?" Most interviewers will guide you - Treat it as a collaborative technical conversation, not a one-way test - Always ask yourself before coding — what is the most efficient solution here, and what is the right data structure to use - Be clock aware — in the first 20 minutes, push to finish the problem as fast as possible while keeping correctness and efficiency in mind. Having that time awareness in the back of your head will help with pacing across the full interview --- ## Open Notes One month of prep is a solid start. The main recommendation going forward is a structured daily practice routine: - Do three to four LeetCode questions per day from NeetCode 75 or NeetCode 150, focusing on the problem types you are weakest in - Spend no more than five to eight minutes attempting a question before looking at the solution if stuck — the goal is pattern recognition, not grinding through every problem cold - Come back to any unsolved question three days later and attempt it again - At the end of every week, redo all the questions from that week — if you did three questions a day for six days, that is 18 questions to review on Sunday - For a senior role, system design is also on the table — do one system design question per day alongside two to three LeetCode questions - Do not get burnt out. Consistency over intensity. The instincts are there. The gap right now is execution speed, confidence in the solution before running it, and leading with optimal approaches from the start. That closes with deliberate practice.

Feedback about Stealthy Elephant (the interviewer)