Sportradar Interview Questions
& Process

After you apply, there's an initial chat about your sports background and yourself, and they'll outline what's next. If that goes well, you'll do an online training for your sport, which includes quizzes, reading, and practice tasks. You might not pass some parts, but keep at it and learn. Completing the training leads to a final interview or test where getting the questions right means you're in. Reviewing the training materials and what you've done is the best way to prep.

So, after the initial screening, I had to do a take-home assessment, which I finished within a couple of days. They gave me feedback saying there were 3 issues (2 were pretty minor), but overall the feedback was positive and they invited me for a technical interview. We talked about my take-home task, and they said it was really good and asked me to improve it with some live coding, which was quite straightforward. However, it took them two weeks and two follow-up emails from me to eventually send a rejection. In the rejection email, they claimed there were 'TOO MANY issues with home task' and that they were looking for someone with TDD experience, even though they mentioned it wasn't required during the screening (I actually used TDD for my assessment). Seriously, don't bother applying!

The company left a disappointing impression due to the way they communicated and organized the process. HR was initially responsive and helped guide the process professionally—up until the final stage of the interview. The process consisted of a screening video call, an interview with the hiring manager, and finally a presentation task in front of the hiring manager and Group Product Manager. There was a 1.5-month gap between the first and second stages. For the final stage—a product discovery task—they only gave two days to complete it (over the weekend), which is unrealistic for someone who works full-time and may already have weekend commitments. The interview stages could definitely be better structured with designated timelines. A negative decision was communicated 10 days after the final interview, without any meaningful feedback. The recruiter merely said, "another candidate demonstrated a better understanding of the domain," and no further feedback was provided upon request. The process felt unfair, as it’s likely the other candidate had more time to prepare for the final task. This not only raises concerns about their organizational processes but also calls into question the transparency of Sportradar’s hiring practices. I would recommend abstaining from applying to Sportradar.

The interview process was pretty straightforward. It started with a brief 30-minute call with a recruiter, which then led to a take-home coding assignment that I had a week to complete. They were quite accommodating about when I could start and submit the task. I finished the assignment within the week and received a rejection email after they reviewed it. The feedback provided was somewhat helpful, pointing out specific parts of my submission. However, I noticed that some of the feedback quoted function names and logic that I hadn't used in my code. They even suggested a fix using a Java library, but my project was in TypeScript, which made me suspect the feedback might have been for a different candidate's submission. When I reached out for clarification, I was ignored.