Had an initial call with recruiter to go over background and process.
Initial tech screen had to be rescheduled and then later was assigned a different interviewer.
The tech screen was building a game (algorithm, not UI) and heard no feedback for a week.
Later was told it went "well" but that I needed to interview with someone on the frontend team.
The next tech screen was very bizarre.
I was asked to develop an algorithm in a very specific way, which introduced difficulties as I wasn't aligned with his implementation strategy and didn't truly understand why it was needed.
Apparently, he was looking for an abstract syntax tree and recursion.
Apparently, the abstract syntax tree example was from an "introduction to programming" book which is laughable.
Build an email for filtering email using a data structure to represent commands
Build an algorithm for the game Mastermind
The following metrics were computed from 1 interview experience for the Docker Front End Engineer role in San Francisco, California.
Docker's interview process for their Front End Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Docker's Front End Engineer interview process in San Francisco, California.