Underdog logo

Underdog Interview Questions
& Process

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

Based on 51 interview experiences · FREE TO READ

2.6 Rounds average
Average Typical difficulty
41.2% Positive experience

Which role are you interviewing for?

23 roles · 51 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Underdog.

Showing 4 of 51
Underdog logo
Underdog

Software Engineer

Engineering · nearly a year ago

Staff Average Negative experience No offer 2 rounds
Interview process
Technical screen Onsite
Interview formats
Technical System Design

The interview process seemed standard initially, but two parts gave me pause. One involved looking at actual production code from their data ingestion pipeline, which felt less like an interview exercise and more like real work. The other round required designing a whole system based on a lengthy set of requirements that closely mirrored the company's existing roadmap. The interviewer even noted that my proposed solution was unique, making me suspect they might be using interviews to get free technical advice instead of just evaluating candidates. It felt more like unpaid consulting than a fair skills assessment. I'd suggest future candidates ask about the purpose of any take-home or design tasks to ensure they're reasonable and in line with typical industry interviews.

Confirmed questions1 question
  • Can you design a system that aligns with our current roadmap?
Underdog logo
Underdog

Technical Compliance Analyst

Engineering · a year ago

Senior Average Negative experience No offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Technical Other

I applied and they put me through the interview process really fast. All 4 interviews were scheduled in about 2 weeks. It became pretty clear during the interviews that they were unsure about what they were actually hiring for, or maybe they wanted to combine it with a security role when it shouldn't be. I got a bunch of questions about automations and incident response, which wasn't even in the job description. I even asked them during the interview why I was being asked these things, and they couldn't give me a straight answer. If they were considering me for another role, they should have just said so. The part about privacy engineering felt really disorganized, and the way the panel communicated during that section was kind of off-putting.

Confirmed questions1 question
  • Have you worked with internal phishing campaigns before?
Underdog logo
Underdog

Software Engineer

Engineering · a year ago

Mid Average Positive experience No offer 2 rounds
Interview process
Take home Technical screen Onsite
Interview formats
Technical Coding Behavioral

Really great interview experience. They had this awesome take-home test that really checked my ruby and class knowledge. It was pretty easy to medium difficulty and took about 2.5 hours. They even sent a gift card for doing it! The final part was a panel interview, broken into three parts: a technical challenge, a question about databases, and then some behavioral questions.

Confirmed questions1 question
  • Can you design a referral system, covering front-end, back-end, and database aspects?
Underdog logo
Underdog

Fraud and Payments Associate

Finance · a year ago

Entry Average Negative experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen Offer
Interview formats
Behavioral Technical

I had a really bad experience with this company. They made me wait a whole month for an update. The interviewers themselves were nice, but the way they kept me in the dark and never gave updates was frustrating. Then they sent a generic rejection email, saying they can't provide feedback due to internal policies. It felt unprofessional, especially since they told me in the interview that I was a great candidate and exactly what they were looking for. The email even said to keep in touch because they were impressed by my background. Honestly, it left a really bad impression, so I don't think we should keep in touch.

Confirmed questions1 question
  • What makes you want to join Underdog?

Underdog Interview Questions

Quoted word for word from Underdog interview reports.

What distinguishes multi-threading from using the Task Parallel Library?

Read reports

Could you explain the function of the output from a terraform module?

Read reports

Could you explain the distinction between structs and classes?

Read report

Can you write a clone of a very specific piece of the .NET Framework?

Read report

Are you interested in fantasy sports, sports betting, or sports in general?

Read report

Can you find any interesting insights from the provided sample dataset?

Read report

Formats, difficulty and experience

Across all 51 Underdog interview reports.

Interview formats

Behavioral 41.5%
Technical 37.7%
Coding 10.4%
System Design 3.8%
Presentation 2.8%

Interview difficulty

Easy 25.5%
Average 64.7%
Difficult 9.8%

Candidate experience

Positive 41.2%
Negative 41.2%
Neutral 17.6%

Reports by job function

Engineering 29
Design 6
Analytics 3
Marketing 3
Operations 2
Other 2