After a recruiter screen/brief, an initial phone screen was scheduled with the manager of the team that I was applying for.
Since that went well, I was provided with a take-home coding assignment that was non-trivial but nothing too crazy (more of a real-world application, not data structures/algorithm-heavy at all).
With a thumbs up from that, I moved forward to the technical/cultural screen, which was 4 interviews (3 with engineers that you may or may not be working with directly, and the manager again).
In between each is a conversation with the recruiter to make sure you're comfortable with everything, things are still going as you're hoping, and if there are any red flags from you about the position.
General code/architectural review of take-home code submission.
Today, the process of setting up and provisioning users in a shared database is a manual task that requires a ticket, validation, and some scripts to execute by the database owners. How would you automate this process?
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.