The interview went well overall. The recruiters were very understanding and approachable. However, the technical question was particularly challenging, especially when it came to writing the code in Python, which is my preferred language for interviews. They acknowledged this and focused primarily on evaluating my approach to data structures.
The process was unfortunately disorganized. The team repeatedly lost my contact information, and despite confirming details several times, the internship was unexpectedly canceled just a month before the planned start date.
I was asked a LeetCode question about string manipulation. A '$' means a number, '+' means a letter, and '*' means that the next three letters should be identical. That was the homework task.
Home assignment (hard LeetCode), then on-site interview. The on-site included a 1.5-hour technical interview, with a question about optimizing an NP-hard problem by reducing the input size, followed by a 30-minute HR interview. The overall process
HR phone call. Team lead interview on LeetCode and JS Promises. Architect interview on system design. They asked me to design a notification service for a digital library. Users can turn on notifications for books they want to borrow. When the boo
I was asked a LeetCode question about string manipulation. A '$' means a number, '+' means a letter, and '*' means that the next three letters should be identical. That was the homework task.
Home assignment (hard LeetCode), then on-site interview. The on-site included a 1.5-hour technical interview, with a question about optimizing an NP-hard problem by reducing the input size, followed by a 30-minute HR interview. The overall process
HR phone call. Team lead interview on LeetCode and JS Promises. Architect interview on system design. They asked me to design a notification service for a digital library. Users can turn on notifications for books they want to borrow. When the boo