The process started off with an initial conversion with an engineering manager, mostly questions about background and experience with a few simple technical questions. Then there was a technical screening with an engineer going over basic data parsing problems.
After that, I was invited for a virtual "on-site", consisting of 5 or so interviews, some being technical and some being more behavioral. For the technical ones, they seemed very grounded and relevant, and were not just LeetCode problems you have to memorize. I was given the option of either doing them all in one day or spreading them out over multiple days, which I thought was incredibly accommodating.
I was also sent a very detailed agenda letting me exactly what each interview would consist of which really helped me in preparing.
Overall this was a very great interview process! Only complaint would be the whole process was a little long with 7+ interviews, but that is not that unheard of nowadays.
What is the best-case time complexity of getting an element from a hash table?
The following metrics were computed from 12 interview experiences for the Greenhouse Software Engineer role in United States.
Greenhouse's interview process for their Software Engineer roles in the United States is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Greenhouse's Software Engineer interview process in United States.