Taro Logo

Software Engineer, Backend Interview Experience - United States

November 1, 2018
Negative ExperienceNo Offer

Process

I got the phone interview just like a week back. The interview went really well as the interviewer asked a couple of questions related to my previous work experience, then asked about Eureka, advantages and disadvantages of micro services, Spring Boot experience, personal experience about using Docker and why do I want to work for Docker. This took for about 20 minutes and then we moved to the coding round(40 min). The coding round was easy for me and later I found that it was a Medium Level LeetCode question. I discussed with the interviewer three different solutions - first using a priority queue, second using a Hashmap(sorting map by values) and third using a List(as suggested by the interviewer). I was not able to discuss the complexity of the solution as time was up.

The sad part here is that I never got a reply back from the HR/Recruiter and I emailed them back to follow up but received none. I think I was too nervous which they might have mistaken as not confident. Nevertheless, a reply would always be good for a candidate.

Questions

Share personal experience of working on Docker.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Docker Software Engineer, Backend role in United States.

Success Rate

0%
Pass Rate

Docker's interview process for their Software Engineer, Backend roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive0%
Neutral0%
Negative100%

Candidates reported having very negative feelings for Docker's Software Engineer, Backend interview process in United States.

Docker Work Experiences