DICE logo

DICE Interview Questions
& Process

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

Based on 88 interview experiences · FREE TO READ

3.1 Rounds average
Average Typical difficulty
65.9% Positive experience

Which role are you interviewing for?

30 roles · 88 reports

Candidate interview experiences

First-hand accounts from people who interviewed at DICE.

Showing 4 of 88
DICE logo
DICE

Data Scientist

Analytics · a year ago

Mid Average Positive experience No offer 3 rounds
Interview process
Recruiter call Take home Technical screen
Interview formats
Technical Coding

It was a usual 3 stage interview process. First, there was a screening, then a chat with a technical member, followed by a take-home assignment. I didn't complete it because I had another offer. The process seemed relaxed and easy, and culture appeared to be important, which I think is a good sign. They covered the basics of my knowledge and shared some insights into their work methods. They also answered my questions openly.

Confirmed questions1 question
  • Using the provided database link, can you predict the demand for the next event as a take-home assignment and detail your methodology?
DICE logo
DICE

HR Generalist

HR · more than a year ago

Entry Average Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Take home Presentation
Interview formats
Behavioral Technical Presentation

It was a pretty standard interview process, starting with a recruiter call. Then I had conversations with the team, followed by a task, and then a presentation. I gotta say, the task was kinda off-putting right from the start, with them saying it 'shouldn't take more than a few of hours to complete.' After the task, there was supposed to be a presentation, but they made it clear you'd only get to that stage if the task was good enough. It's a bit much to ask someone to spend a couple of hours on a task, and then not even guarantee a presentation or offer something like Dice credits. And honestly, sending a generic rejection email after someone puts in the effort for both the task and presentation is pretty inconsiderate.

Confirmed questions1 question
  • Could you share a story about a tough project you handled and felt proud of?
DICE logo
DICE

Senior Software Engineer

Engineering · more than a year ago

Senior Easy Negative experience No offer 3 rounds
Interview process
Recruiter call Technical screen Take home
Interview formats
Behavioral Technical Coding

The interview process started with a chat with the hiring manager about my background and the specifics of the role. It was a pretty chill conversation. Next up, I had a technical discussion with two engineers from the Android team where we went deeper into my experience. They hinted at what they were looking for in the next stage. Then, I was given a take-home assignment. It involved building a search screen and a details screen using a music API. Apparently, the main reason I didn't pass was my failure to modularize the application, which they felt indicated I couldn't handle a large codebase. They didn't specify the expected time commitment for the take-home test, and there was no opportunity to defend my choices or discuss future improvements. I think a live coding session might be a better fit for this type of task, as it requires less effort upfront and at least allows for immediate feedback and clarification.

Confirmed questions3 questions
  • Can you discuss your past experience and the tech stack you're familiar with?
  • Tell me about your experience, focusing on technical details.
  • How would you approach modularizing a two-screen application for a large codebase?
DICE logo
DICE

Head of Brand Partnerships

Marketing · more than a year ago

Executive Average Negative experience No offer 3 rounds
Interview process
Recruiter call Presentation Background check
Interview formats
Behavioral Case Presentation

Applied early September, got told the position was filled, but the hiring manager suggested another Head role I was less experienced for. After a lengthy process including a real case study on go-to-market strategy for new markets, they decided in December not to hire anyone and changed the role's requirements. As of late January, both roles are still open. I asked about the original role but haven't heard back. The decision process is unprofessional and wastes candidate time, though it's not the hiring team's fault.

Confirmed questions3 questions
  • Why are you interested in Dice?
  • What qualifies you for this role?
  • Develop a strategy for expanding into European markets.

DICE Interview Questions

Quoted word for word from DICE interview reports.

Build a simple ticket purchasing system using the Stripe Checkout API.

Read reports

If you could add one event not currently on DICE, which would it be and why?

Read reports

Can you list and describe the five most prevalent design patterns utilized in iOS development?

Read reports

How would you approach modularizing a two-screen application for a large codebase?

Read reports

What is your experience (knowledge level/networking) with concert venues and festivals in Germany?

Read report

Using the provided database link, can you predict the demand for the next event as a take-home assignment and detail your methodology?

Read report

Formats, difficulty and experience

Across all 88 DICE interview reports.

Interview formats

Behavioral 47.7%
Technical 25%
Presentation 10.2%
Other 7.4%
Case 4.5%

Interview difficulty

Easy 21.6%
Average 65.9%
Difficult 12.5%

Candidate experience

Positive 65.9%
Neutral 12.5%
Negative 21.6%

Reports by job function

Sales 18
Operations 15
Engineering 12
Marketing 11
HR 10
Finance 7