Summary
I interviewed for an SDE2 role at Sumo Logic. The interview consisted of project discussions, theoretical questions, and a coding problem, a variation of Course Schedule 2. Despite solving the problem, I was ultimately rejected, with feedback citing the time I took and vague comments about my project experience. I believe the rejection was unfair.
Full Experience
My interview at Sumo Logic for the SDE2 position began with a discussion about my past projects, followed by a few theoretical questions which I felt I answered well. During the coding round, I was presented with a problem that was a variation of the 'Course Schedule 2' problem. I managed to implement a solution, though it did take me a bit longer than I would have liked, as I had to debug some issues. Unfortunately, I later received a rejection. The feedback mentioned that I took too much time and provided some vague comments about my project experience, which I found quite unhelpful and felt was an unjust reason for rejection. I even questioned if there was an underlying bias. Ultimately, I feel that interviewers are often a reflection of the company's culture, so perhaps it was for the best that I dodged this bullet. I am currently employed at one of the top three stock brokers in India.
Interview Questions (1)
I was given a coding problem that was a variation of the well-known LeetCode problem 'Course Schedule 2'. The core concept revolved around task scheduling with prerequisites, similar to the original problem but with an unspecified twist.