Status: New Grad, BS CS
YoE: <1 Year (Previous Big N internship)
Location: MTV
Cannot disclose specific questions due to NDA.
Beharioral Round: Standard behavioral questions, taked about previous experience and project. We has a good time.
Grade: 4/5. I could have done better communicating my past internship, but he seemed impressed.
Round 1: Math related question. Felt like if I knew the math ahead of time, I would have been able to code this up in 5 minutes. Instead, I spent 35 mins trying to derive the math needed and the last 10 coding when I finally got it.
Grade: 3/5. Interviewer was not enthusiastic. Could have practiced more math questions, it was either a "you got it or you don't" with this one.
Round 2: Q1: Simple string question (easy), check whether a string is good or not. Did this in 10 mins.
Q2: Determine the number of good strings of a certain length, used backtracking along with my answer to Q1 to solve this.
Grade: 4/5. Could have done this quicker, but got through everything. Interviewer was rolling along with the solution but was reserved at the same time.
Round 3: Q1: DFS related question. What made this difficult was there were so many conditions to check. Code was sloppy at first, but simplified it remembering what I learned from LC. Interviewer explained bugs to me and I quickly corrected.
Grade: 3.5/5. Would have been a 4 if I simplified from the get. Interviewer was enthusiatic and thought I did well in thinking out loud, which helped me relax enough to perservere through this one.
Round 3: Q1: easy array question (randomize placement of numbers in square array)
Q2: return an randomized array such that all numbers are grouped with each other, first I thought of graph traversal used backtracking to generate the combination (placements once again had to be random). Didn't have time to finish this one, so interviewer told me pusedocode was fine.
Grade: 4/5 Felt like I had the fundamentals down. Hard to talk about big-O when dealing with random stuff, so we just thought of the average case or "in expectation".
Thoughts: Very math and graph heavy with some recrusion mixed in, could have done more math related problems. I don't think I'm getting this job, but who knows.