There was a 45 minute talk with the hiring manager on cultural/behavioral questions.
There was a 45 minute talk with the team's lead engineer, on technical topics, but more from a cultural perspective as opposed to a purely technical one.
There was a 45 minute talk with the team's UX designer on working with designs (still quite cultural/behavioral).
There was a 45 minute talk with the team's product manager on collaborating with the product team (again, cultural/behavioral).
There was a 45 minute talk with an engineer on the team during which I was asked technical questions.
There was a 45 minute talk with another engineer on the team during which we reviewed some code I had written in preparation for the interview (I had been told not to spend more than an hour on the code sample, and I was given the option to write the code during the interview, instead of preparing it beforehand).
I found the cultural/behavioral questions to be fairly standard and what I expected (based on past interviews and some Googling), but I found the technical questions difficult and I didn't believe I had done very well on those. It just goes to show that you never know exactly what they're looking for, so if you're interested in the role and the company, you should go for it!
Tell me about a time you failed.
The following metrics were computed from 33 interview experiences for the DigitalOcean Software Engineer role in United States.
DigitalOcean's interview process for their Software Engineer roles in the United States is on the easier side as most engineers get an offer after going through it.
Candidates reported having very good feelings for DigitalOcean's Software Engineer interview process in United States.