Initial phone screen with an internal recruiter described the following process, which would take about 3 weeks:
* 1st problem statement: PR review
* What would stop me from giving the green light to merge this?
* "a few key issues in this PR, the red-flaggy showstopper type. a couple of code smells wafting around - not looking for nitpick fluff"
* 1 on 1 with another engineering manager
* Node API, so I need a working knowledge of node
* Not a timed exercise (~2 hours, but can be done in multiple sittings)
* No arbitrary deadline to return it
* 2nd problem statement: technical design
* What is the bar for quality before merging this?
* "Here's our rating scale - where would you put this on it?"
* Trey Griffith - Head of Eng
* No behavioral-style "tell me a time when" questions
* Bo Liu - CTO/co-founder
I was given the first problem statement through a platform called Hatchways, which consisted of a pull request to review. The pull request was terrible quality code, and it was hard to know where to start - it missed 2 of 4 requirements, and of the 2 that it did attempt to implement, the likely result would be a complete rewrite, which doesn't make a lot of sense in the context of a line-by-line PR review, but I made an attempt at it, and left as much feedback as seemed reasonable without being "nit-picky."
After submitting, it took about 2 weeks, and then I got a rejection with the explanation "We know the exercise took a lot of time, and we just wanted you to know that we don't take the time you've spent working on it lightly. While overall you provided a thoughtful response, there are a handful of important technical issues, and your work did not meet the bar we have set for success on that end. As discussed in our call, very deep technical insight and acuity, combined with customer focused thinking, is central to the role of Engineering Manager at Clipboard Health."