ESPN Software Engineer Interview Questions
& Process

First I spoke with a recruiter and then had a screening with them. After that, they mentioned I would have a call with a senior software engineer to discuss my projects. However, the call turned out to be a technical interview, which was unexpected and I felt unprepared. If I had known it wasn't just a discussion about my work, I would have prepared differently. It felt like they intentionally tried to surprise me.

Applied online and got contacted for a phone screen by a technical recruiter after about three weeks (mostly due to being out of the country for work, which I'd told them about). Then I got a coding project, involving CSS/HTML and hitting an endpoint to get and parse data, which I had 48 hours to complete. The onsite interview was at the Bristol, CT campus. It involved meeting four team members across two two-hour sessions, each with two interviewers. Even though I have 3-4 years of experience and am finishing my master's, I didn't have much experience with their specific tech stack. The first panel focused on my background, past projects, and some high-level technical questions about languages, usage, and technology choices. The second panel also delved into my background but mixed personality and technical questions. This included coding exercises like debugging/improving code, writing a small program for GUI tasks based on input, and updating a table with JSON data. They also asked about team dynamics when someone isn't pulling their weight, how I select new technologies, repository experience, and other questions probing my personality or problem-solving approach. If I got stuck, especially on unfamiliar topics, they'd guide me without giving the answer directly, seeing if I could reach it myself using my existing knowledge. The whole process, managed by the recruiter and hiring manager, felt organized and the team was really friendly. It was a positive and low-stress experience; they weren't looking for someone who knew everything but rather to see how I could apply basic knowledge to figure out new things. The interview really seemed geared towards assessing my problem-solving thought process.

My interview experience at ESPN for a mobile software engineer role was quite drawn out, taking about one to two months, possibly due to the holiday season or the team's pace. After clearing initial recruiter calls and technical/behavioral phone screens with higher-ups, HR arranged the flyout. Be aware that ESPN has specific policies for flyouts: they don't reimburse travel to/from your home airport or GPS charges for rental cars, and they cover only two meals and one night of hotel stay. The hotel provided was undergoing renovations. Navigating the campus requires specific directions to find the correct 'South' gate entrance, leading to Building 9 for check-in. Security is very visible and strict, requiring ID checks multiple times. You'll need to request a temporary WiFi password from the hiring manager if you need internet access. An unusual instruction was to wear a business suit for the engineering interview, which turned out to be unnecessarily formal for the on-site team's attire. It's advisable to research the company's products and incorporate sports-related anecdotes into your conversation, especially given the younger age demographic of the engineering team and the company's attractive benefits like pensions.