You are right that you can only await in an async function, but you can call an async function anywhere and get back a Promise.
await-ing that promise is often what you want to do but there are other ways to do work once the promise has resolved.
28 karma · joined November 8, 2014
await-ing that promise is often what you want to do but there are other ways to do work once the promise has resolved.
For ascertaining whether someone meets a technical bar -- the gold standard has to be facilitating some way where they can do some actual work with you. That might be v difficult depending on nature of stack, tech debt, etc. But the closer you can make that sort of process to what would really be happening, the better. Coding exercises really only prove someone is good at coding exercises -- that may or may not have any relevancy to what you do I think.
Being "good at hiring" -- and hence having better people -- is such an advantage for an organisation, it always surprises me that too often we fall back on seemingly default hiring processes, and we don't look at the sorts of optimisations we could do to help surface the best candidates for a role.
It had been a while since I'd had this sort of negative experience, and what I would say is it's re-reminded me to make sure my hiring in the future caters for this sort of thing. Particularly for less experienced devs.