The interview process was casual, and ranged from specifically technical to largely abstract questions. There were process and collaboration oriented questions, as well as a coding interview. For the coding interview, perhaps because I was in the midst of other interview processes that were more explicit about the parameters of the coding interview, I wound up making assumptions about what was permissible and what was not permissible that impacted my performance.
In hindsight, I should have asked more questions about what is allowed, however, questions such as these can also cast a light on a candidate, so many such as myself will tend to not ask them. Therefore, the coding interview could have had more details provided beforehand about the structure and expectations of the interview (eg, can documentation be consulted during the interview, should the environment be a vanilla dev environment, or should you use all your usual tooling, etc).
How do I view the use of patterns in software design/development.
A collaboration challenge encountered and how I dealt with it
Given a set of requirements for a distributed system, eg IPAM system, what design considerations would I use in putting together an architecture.
The following metrics were computed from 7 interview experiences for the DigitalOcean Senior Software Engineer role in New York, New York.
DigitalOcean's interview process for their Senior Software Engineer roles in New York, New York is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for DigitalOcean's Senior Software Engineer interview process in New York, New York.