Don't be afraid to experiment, keep the product development teams engaged and productive by shipping new things as often as possible, even if that means tech debt or abandoned projects.
Interview process was long. Started with a phone interview with a recruiter, then moved to a coding interview with another programmer. Coding was language-agnostic. On-site interview was an all-day affair; came in in the morning and went through a se
I did not make it past the technical phone screen, which was really surprising to me. I was asked a simple dynamic programming question, which, go figure, I used dynamic programming to solve. The interviewer was expecting a O(N^2) solution, but I g
I was put in touch with a Docker recruiter by someone I knew, and started the process with a phone screen, which was average difficulty. Then I had a day of (~5) onsite interviews. I was initially talking to teams besides the core (open source) team,
Interview process was long. Started with a phone interview with a recruiter, then moved to a coding interview with another programmer. Coding was language-agnostic. On-site interview was an all-day affair; came in in the morning and went through a se
I did not make it past the technical phone screen, which was really surprising to me. I was asked a simple dynamic programming question, which, go figure, I used dynamic programming to solve. The interviewer was expecting a O(N^2) solution, but I g
I was put in touch with a Docker recruiter by someone I knew, and started the process with a phone screen, which was average difficulty. Then I had a day of (~5) onsite interviews. I was initially talking to teams besides the core (open source) team,