Docker logo

Docker Software Engineer Interview Questions
& Process

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

Based on 22 interview experiences · FREE TO READ

3.2 Rounds average
Average Typical difficulty
36.4% Positive experience

Candidate interview experiences

First-hand accounts from people who interviewed at Docker.

Showing 3 of 22
Docker logo
Docker

Software Engineer

Engineering · more than a year ago

Mid Average Negative experience No offer 4 rounds
Interview process
Recruiter call Technical screen Technical screen Onsite
Interview formats
Behavioral Technical Coding

It started with a quick 30-minute recruiter screen, which went fine and covered basic questions and company info. The recruiter also explained the rest of the interview process: three technical interviews with coding exercises, followed by a final non-technical interview with a senior leader. They really emphasized that the coding exercises would be practical, not algorithm or data-structure focused. However, the first technical interview with the hiring manager gave me an algorithm challenge, which was not practical at all. I didn't pass because I don't practice LeetCode. It's a bit disappointing that the recruiter's description of the technical interviews didn't match the actual content, which is something they should probably fix as candidates generally don't like being misled.

Confirmed questions2 questions
  • Tell me about your ideal team.
  • What kind of company do you envision yourself thriving in?
Docker logo
Docker

Software Engineer

Engineering · more than a year ago

Senior Easy Negative experience No offer 2 rounds
Interview process
Recruiter call Phone screen Background check
Interview formats
Behavioral

I applied online and a recruiter reached out saying my CV was a good match for an intro call. We scheduled it, and during the call, we discussed my reasons for applying to Docker, my current job search, and salary expectations. The recruiter said it was a good match and I'd move to a technical interview. After a few days with no response to my follow-up emails, I assumed the process was over. A month later, I got an automated email stating they couldn't reach me and would consider me not interested. I replied, pointing out they hadn't actually contacted me, but again, received no response.

Confirmed questions1 question
  • What motivated your application to Docker?
Docker logo
Docker

Senior Software Engineer

Engineering

Senior Average Positive experience Accept offer 4 rounds
Interview process
Recruiter call Phone screen Technical screen Technical screen
Interview formats
Coding Technical

There was a recruiter call first. Then a hiring manager call with a simple coding task. After that, a coding task that was related to the team's actual work but without algorithms. Lastly, a coding/debugging task where I was given a GitHub project to debug, fix, or optimize.

Confirmed questions4 questions
  • What are different isPalindrome implementations?
  • Do you have experience with simple coding tasks?
  • Can you complete a coding task related to the team's actual work without using algorithms?

Docker Software Engineer Interview Questions

Quoted word for word from Docker interview reports.

Design a key-value store that is safe for concurrent access.

Read reports

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

Read reports

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

Formats, difficulty and experience

Across all 22 Docker interview reports.

Interview formats

Technical 37.3%
Behavioral 31.4%
Coding 27.5%
System Design 3.9%

Interview difficulty

Easy 9.1%
Average 77.3%
Difficult 13.6%

Candidate experience

Neutral 22.7%
Positive 36.4%
Negative 40.9%