ESPN Software Engineer II interview questions

Applied online and was contacted within three weeks for a phone screen with a technical recruiter (took this long mostly because I was out of the country for work and informed them of that). I was given a coding project (creating something in CSS/HTML, and contacting an endpoint to get data and parsing it) for 48 hours. I interviewed at the Bristol, CT campus where I met with four team members (two hour long sessions with two interviewers). I have between three to four years of software engineering experience, and am completing my master's in software engineering, however did not have as much experience in the technology they were using. The first panel asked questions about my background, interesting projects I worked on/was working on, and asked some high level technical questions (regarding programming languages, how I used them, how do I decide what technology to use, etc). The second panel too went into my background, but was a combination of personality/technical questions. I was asked to perform some coding exercises (debugging/improving code, writing a small program to take certain inputs and perform a GUI task related to them, update a table based on JSON inputs, etc). I was asked about times where someone in a group may not have pulled their weight and what we did as a team to overcome it, how do I choose new technologies, my experience with repositories, and other probing questions relating to my personality or how I solve technical problems. If I got stuck on a question (since it wasn’t really part of my background), they would talk me through it until it clicked in my head what to do (they never gave an exact answer, they wanted to see if nudged could I come to it myself using other knowledge that I had). The interview process was very organized between the technical recruiter and hiring manager, and the team was very friendly and it was a good interview. It wasn’t stressful, and they didn’t expect you to know everything (they expected the basics and to see if you could piece those together to figure out something you may not know already). I would say the interview was more to test your thought process in regards to problem solving rather than already knowing how to solve the problem.