Clipboard Engineering Manager interview questions

I was reached out to by a recruiter directly about this role at the end of April. I had an initial interview in early May, which went fantastic. I was told the next step was an assessment to review a PR, which I completed and returned within that initial week. After that, I heard absolutely nothing in response. I reached out to the recruiter, and they said they'd look into where it was in the process. Again, I heard no response back. I reached out again, and the response was that the role had been closed after this long wait, so no progress on the assessment I had returned, and no interview after the entire process. Today, at the end of May, I received an email from Clipboard saying that after reviewing my assessment, that they would not be moving on with me with the role. This conflicts with the statement I heard from the recruiter that told me that the role had been closed earlier in the month and that they were no longer hiring for the position. For these reasons, and several others (including a negative perception in the healthcare space per other reviews and social media from healthcare workers), I would personally avoid pursuing interviewing here again. I would put the actual interview and assessment itself as easy to average, but the difficulty in getting anyone to respond adequately to candidates as the most challenging hurdle.

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."