Docker logo

Docker Interview Questions
& Process

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

Based on 105 interview experiences · FREE TO READ

3 Rounds average
Average Typical difficulty
33.3% Positive experience

Which role are you interviewing for?

30 roles · 105 reports

Candidate interview experiences

First-hand accounts from people who interviewed at Docker.

Showing 4 of 105
Docker logo
Docker

Account Executive

Sales · half a year ago

Mid Average Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical

Started with a recruiter screening call that was pretty conversational and focused on getting to know me. Then had a hiring manager interview. Honestly, I was kinda shocked the manager was in a management role because they had extremely low energy on the call. They wanted very specific info and metrics but didn't ask good questions to get that information. They kept saying they were confused or not understanding. There were zero behavioral or situational questions, and no questions related to the company or values. Overall, there seemed to be a general lack of care and empathy for the individual. I got the sense this is the type of place that is going to churn and burn reps. The manager wasn't truthful when asked why the role was open, as the last person was obviously fired or at minimum put on a PIP. There was a heavy emphasis on needing technical skills. The pay is well below market value for the experience they require. Wouldn't recommend.

Confirmed questions1 question
  • What sales methodologies or frameworks do you utilize?
Docker logo
Docker

UX Researcher

Design · nearly a year ago

Entry Average Positive experience No offer 2 rounds
Interview process
Recruiter call Phone screen
Interview formats
Behavioral Technical

So first there was like a screener, who was really nice and friendly, asking me about my background and the role. They asked a couple of questions about the role itself, but not super in-depth. Then, a few days later, they emailed to set up the interview with the hiring manager. That interview, the questions got more detailed about the role, how I work, and my experience.

Confirmed questions6 questions
  • What is your motivation for joining Docker?
  • Describe a project in which you made a significant contribution.
  • Have you collaborated with developers in your previous roles?
Docker logo
Docker

DevOps Engineer

Engineering · a year ago

Mid Average Negative experience No offer 5 rounds
Interview process
Recruiter call Phone screen Take home Technical screen Onsite
Interview formats
Technical Coding Behavioral

It began with a quick screening chat, then a technical call that lasted about 30 minutes. After that, I got a coding project. I finished the assignment, shared my git repo, and even deployed the app live on my own cloud setup to show it off. Then there were 3 more technical interviews where we talked about the code. The last interviewer wasn't happy with one part of the code; I admit, it wasn't the best way to do it, and I'd even put comments in explaining it was a bit fragile and not my top-tier work, but it *did* work as required, and it was the first thing I'd fix with more time. He seemed to think the code didn't work, even though I'd deployed it as a working web app. He ended my candidacy right there, even though the hiring manager was keen, everyone else liked it, and I'd proven my skills.

Confirmed questions1 question
  • Could you build a Python web API app? It needs a POST endpoint for a list of movie titles. This app should use the IMDB API to fetch basic movie details, calling the API concurrently for all films, and then return the gathered info. Make sure the app can run inside a Docker container.
Docker logo
Docker

Product Manager

Product · more than a year ago

Mid Difficult Positive experience No offer 6 rounds
Interview process
Recruiter call Phone screen Technical screen Onsite
Interview formats
Behavioral Case Presentation

I had a phone screening call with a recruiter, then a video call with a current Product Manager. After that, there was a series of four interviews with various key team members. They preferred to do all the interviews on one day, but my schedule didn't allow for that, so they were able to accommodate me and spread the interviews across multiple days. I received a rejection email afterwards, but they were willing to follow up to discuss their reasoning. This interview process happened in Spring 2021 and the team was amazing. I felt more and more hopeful about the chance to work with everyone with each interview. Unfortunately, after going through the whole process, they found stronger candidates, but it was a good growth experience for me overall.

Confirmed questions1 question
  • Describe how you would gather requirements for a new feature related to an office space.

Docker Interview Questions

Quoted word for word from Docker interview reports.

Can you explain the distinction between a container and a virtual machine?

Read reports

Could you build a Python web API app? It needs a POST endpoint for a list of movie titles. This app should use the IMDB API to fetch basic movie details, calling the API concurrently for all films, and then return the gathered info. Make sure the app can run inside a Docker container.

Read reports

Could you describe the resources that Linux cgroups are responsible for managing?

Read reports

How would you go about designing a system to find duplicate URLs?

Read report

Could you identify the integers from a given list that add up to a specific sum?

Read report

Can you write a program to simulate a CLI application?

Read report

When you're designing, do you start with the final designs or do you use wireframes first?

Read report

What's your approach to solving this simple dynamic programming question?

Read report

Formats, difficulty and experience

Across all 105 Docker interview reports.

Interview formats

Behavioral 44.3%
Technical 34.3%
Coding 10%
Presentation 6.7%
Other 1.9%

Interview difficulty

Easy 21.9%
Average 67.6%
Difficult 10.5%

Candidate experience

Negative 47.6%
Positive 33.3%
Neutral 19%

Reports by job function

Engineering 46
Sales 15
Operations 10
Design 9
Marketing 6
HR 5