Sportradar logo

Sportradar Software Engineer Interview Questions
& Process

Real candidates share what happened, how many rounds they had,
and how the experience turned out.

Based on 37 interview experiences · FREE TO READ

2.9 Rounds average
Average Typical difficulty
37.8% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Sportradar.

Showing 3 of 37
Sportradar logo
Sportradar

Software Engineer

Engineering · a year ago

Entry Average Neutral experience No offer 2 rounds
Interview process
Recruiter call Take home
Interview formats
Technical Coding

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.

Confirmed questions1 question
  • Can you discuss your experience and philosophy regarding Test-Driven Development (TDD)?
Sportradar logo
Sportradar

Senior Software Engineer

Engineering · a year ago

Senior Average Neutral experience No offer 4 rounds
Interview process
Recruiter call Technical screen Take home Technical screen
Interview formats
Behavioral Technical Coding

The interview process had 4 rounds. First was a meeting with HR. Then, an in-depth discussion about my experience with a Staff Engineer and a Lead. After that, I had a take-home assignment. Finally, there was a review of the assignment along with a technical interview. Overall, it wasn't too difficult. They initially offered me a different Engineer role, citing a lack of scale experience, but then told me they'd found someone else for that position. I'm not sure what happened, but I was ghosted after that.

Confirmed questions3 questions
  • Can you discuss your experience with scalability?
  • Tell me about your software design approaches.
  • How do you approach code reviews?
Sportradar logo
Sportradar

Software Engineer

Engineering

Senior Easy Positive experience No offer 4 rounds
Interview process
Recruiter call Technical screen Take home Onsite
Interview formats
Coding System Design

I had an initial video call with a recruiter, who then set up an interview with the engineering director. After that, I had a few more interviews with engineering team members. The hiring process involved a challenging take-home assessment and about 3.5 hours of interviews with people at different organizational levels. I felt good about the take-home assessment and apparently they were impressed. The company seems well-structured with a positive engineering environment. However, I got nervous in the second round of interviews and struggled with basic syntax, even though I could solve the problems they presented. Nerves can be unpredictable, so practice with mock interviews beforehand. It was a good interview experience overall, and although I didn't get an offer, I understood their decision. It's tough knowing I'd be valuable but also recognizing my interview skills need work, and I wish technical interviewers could overlook interview jitters. Still, they made the best decision with the info they had, and I'd recommend this company.

Confirmed questions2 questions
  • Solve a fundamental JavaScript problem using a coding platform that lacks code completion.
  • Design a system that incorporates an intermediary API, possibly reviewing some case studies.

Sportradar Software Engineer Interview Questions

Quoted word for word from Sportradar interview reports.

Create a function to update the score of a game with absolute home and away scores.

Read reports

Build a function to retrieve a summary of ongoing games, ordered by total score, with ties broken by the most recent start time.

Read reports

Implement a function to start a new game with initial score 0-0, capturing home and away teams.

Read reports

Describe scenarios involving race conditions and deadlocks with channels in Golang.

Read report

Can you explain the differences between a List and a Set?

Read report

Could you build a backend API to simulate football matches?

Read report

What is the ideal number of responsibilities for a method?

Read report

How would you compare two sets of arrays to find additions, deletions, and updates?

Read report

Formats, difficulty and experience

Across all 37 Sportradar interview reports.

Interview formats

Technical 38.8%
Coding 31.8%
Behavioral 25.9%
System Design 2.4%
Presentation 1.2%

Interview difficulty

Easy 21.6%
Average 73%
Difficult 5.4%

Candidate experience

Negative 45.9%
Neutral 16.2%
Positive 37.8%