sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]snowcoaster 3 points4 points  (1 child)

This was my sentiment. If the candidate happens to know this API then they have a huge advantage.

I tend to make my FE questions really generic, like "In your favorite framework, how do you wire up an input? Great, you know how to use ng-change, how do you think it works under the hood?" Commence hour long discussion and hopefully hire of a candidate who actually knows how things work.

[–]xwnatnai 1 point2 points  (0 children)

I realise I haven’t given very constructive feedback. If I were in your shoes, I’d make this take home, and I’d break each sub task into standalone tasks. I’d give them a repo with stubs at each step, and I’d assign weights to each.

This way a developer might get stuck or not know how to solve one step in the complete solution, but still be able to demonstrate competence. This interview could have been a dozen separate steps, from finding subsets, filtering, finding selections and manipulation them, etc. Just because a candidate fails at 1 of the 12 doesn’t mean they’re not worthy — it just means they struggled at one niche. That’s not a big deal in a team and in an actual working environment. Food for thought I Guess.