Sumo Logic Interview Questions
& Process

Throughout the hiring journey, communication was clear and steady, mostly through emails. Scheduling interviews was easy with a user-friendly system. Each interview stage clearly stated who would be interviewing, their role, and what they'd be discussing. Everyone involved – interviewers, recruiters, and HR – was really nice, easy to talk to, and professional. They also have great public resources and documentation which helped me prepare and learn about the company. Honestly, it was a really good experience compared to other companies; I have no complaints.

So, the first part was this coderpad online test that lasted for an hour and a half. After I passed that, they set up three more interviews for me. These were: Coding, System Design, and then another Javascript Coding one. They mentioned all three would be done back-to-back and each would be an hour long. The coding interview itself was pretty tough; I got a problem about finding a subset of an array of strings. I really struggled with it, and the interviewer wasn't much help, not even when I asked if I was on the right track. I spent the whole hour on it and ran out of time. Then, for the design round, the interviewer was a no-show for the first 10 minutes. I pinged the recruiter, and they said the interviewer was tied up and suggested rescheduling the remaining interviews for the next week. They apologized for the mix-up and the short notice. About 30 minutes later, the recruiter called back to say I hadn't actually cleared the first round and they wouldn't be continuing with the other interviews. I just said okay and thanked them for letting me know. Honestly, the communication and coordination within the recruiting team seemed pretty shaky throughout. But hey, I did get to see some of the coderpad questions, which was useful for learning.

I went through 4 interview stages. It started with a half-hour chat with a recruiter, then a 1-hour technical test, followed by a 1-hour meeting with the team lead, and another 1-hour technical test. I had a fourth 1-hour technical challenge lined up, but the coordinator let me know a few hours beforehand that they were canceling it and the recruiter would be in touch with an update. They mentioned I was interviewing well, but someone else had accepted an offer the previous day. It's worth noting that the recruiter did share specific feedback from my interviewers, which was a first for me after over 150 applications, so I do appreciate that.

So initially, I was told the interview process would be: Recruiter Screen, Manager Screen, Coding Interview, System Design Interview, and then a Culture/Behavioral/Resume Interview. Then, during the recruiter screen, they mentioned they might combine a technical interview with the culture fit to speed things up. The actual process I went through was: Recruiter Screen, Manager Screen, Coding Interview/Culture Fit (split between coding and culture/resume questions), System Design Interview, and then an extra Coding Interview. I thought it was a bit weird to add another coding interview after they had already set expectations. But, I was still interested in the company, so I kept going. During the rescheduled second coding round (the first interviewer no-showed), the new interviewer just dropped a problem into Coderpad without any intro or trying to get to know me. When I asked for clarification on details or edge cases, they were kind of condescending, but I managed to solve the problem and discuss its complexities and improvements. Even so, I got rejected because I hesitated for a moment at the start, looking up if a Python constructor was `_init_` or `__init__`. It felt like a waste of time, especially if that was going to be the deciding factor. If I didn't have another offer, I'd be really upset about how much time this took. It started well but the quality dropped off.