Dribbble logo

Dribbble Interview Questions
& Process

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

Based on 15 interview experiences · FREE TO READ

2.7 Rounds average
Average Typical difficulty
33.3% Positive experience

Which role are you interviewing for?

10 roles · 15 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Dribbble.

Showing 4 of 15
Dribbble logo
Dribbble

Account Executive

Sales · nearly a year ago

Mid Average Neutral experience No offer 3 rounds
Interview process
Recruiter call Phone screen Technical screen
Interview formats
Behavioral Other

I went through three rounds of interviews for a role, and everyone I spoke with was perfectly pleasant. Each conversation was polite and positive, and I appreciated the team’s professionalism during the process. That said, the structure of the interviews felt misaligned with the eventual outcome. The conversations were almost entirely focused on culture fit, communication style, and cross-functional collaboration. There were no targeted questions about the core skills required for the role or the specific expertise they said they were evaluating. After completing all three rounds, I was told the team decided “the fit wasn’t ideal for the business right now,” but no concrete feedback was offered. It’s disappointing to invest significant time, prepare thoroughly, and have multiple conversations without receiving any specific insight into what was missing or what led to the decision. Overall, everyone was kind, but the process could be improved by providing candidates with clearer expectations about what each interview will assess and offering meaningful feedback after multiple rounds.

Confirmed questions1 question
  • Tell me about your experience with remote work.
Dribbble logo
Dribbble

Software Engineer

Engineering · more than a year ago

Senior Average Negative experience No offer 4 rounds
Interview process
Technical screen Onsite Offer
Interview formats
Technical Presentation

The interview process was alright. After completing all four interviews, I was told I was an "excellent candidate" and that they were "looking forward to continuing the conversation" in the final interview, but then I got a rejection email. I'm fine with not getting the offer, sometimes it's just not a fit, but it felt like the rug was pulled out from under me after what was said in my last interview. Also, I spent all this time interviewing and wasn't given a clear reason for what felt like a sudden change. Even if you don't get an offer, candidates should at least learn something from the experience, and this wasn't it.

Confirmed questions1 question
  • Given a set of wireframes, walk me through the implementation process.
Dribbble logo
Dribbble

Product Designer

Design · more than a year ago

Mid Easy Negative experience No offer 5 rounds
Interview process
Recruiter call Phone screen Technical screen Presentation Take home
Interview formats
Behavioral Technical Presentation

The interview process began with a recruiter call to assess basic fit. Following that, I had several interviews with the design director, the design team, and the VP of product. Then I met with the CEO. Although the initial interviews were good, they became fatiguing because they all felt introductory and repetitive. It was unclear how far along I was in the process. After the initial interviews, I was given a design exercise. The brief was very specific to business needs and asked me to propose a solution for increasing site engagement using the 'bucket' or 'save' feature, and to pose questions to analysts and engineers. I prepared my response but during the presentation, the three interviewers were disengaged and provided brief answers. I presented a low-fidelity solution, but they suggested I create a more in-depth visual solution live, which was beyond the brief and too specific to their needs. The interview ended without much positive feedback, and despite the solution being implemented later, the experience felt like spec work disguised as a challenge.

Confirmed questions1 question
  • Can you tell me more about your background?
Dribbble logo
Dribbble

QA Specialist

Engineering

Entry Average Positive experience Accept offer 3 rounds
Interview process
Recruiter call Technical screen Onsite
Interview formats
Technical Behavioral

The interview process was really great, the people involved were super professional and made me feel valued. They went out of their way to keep me engaged even after I accepted the job. The onboarding was awesome, keeping me involved even before my start date. They sent over documents about the process and the company before I even started, which made me feel really welcome. They clearly trust their new hires; they sent me my work laptop over a week before I began. They really do care.

Confirmed questions3 questions
  • The questions were straightforward, technical, and behavioral.
  • Candidates with domain experience will enjoy the interview, as it's more of a discussion than a one-way conversation.
  • They also welcome suggestions for process changes from candidates, which makes you feel appreciated.

Dribbble Interview Questions

Quoted word for word from Dribbble interview reports.

How would you go about implementing the Dribbble homepage?

Read reports

Given a set of wireframes, walk me through the implementation process.

Read reports

Is there anything that you were hoping I would ask about that we haven't touched on yet?

Read report

What are the day-to-day responsibilities of this role?

Read report

Formats, difficulty and experience

Across all 15 Dribbble interview reports.

Interview formats

Behavioral 43.8%
Technical 28.1%
Presentation 12.5%
Other 6.2%
System Design 3.1%

Interview difficulty

Easy 33.3%
Average 66.7%
Difficult 0%

Candidate experience

Neutral 33.3%
Positive 33.3%
Negative 33.3%

Reports by job function

Sales 6
Engineering 6
Consulting 1
Operations 1
Design 1