[siamakfr]

At every company I've been part of the interview design process, I always insist on having practical tasks with real tools because how quickly someone can parse documentation and code context are not trivial aspects of the job. It does take a lot of time to set up sandbox projects however which a platform like this does away with. Looking forward to the day when no candidate sees Leetcode or HackerRank as part of a tech interview again.

[garyjlin]

Thank you, and love that you promote great interviewing practices! What were some examples of prompts you routinely used for interviewing? And any learnings on great (or not so great) interview design?

[siamakfr]

This was my process: built a sandbox/simplified version of the app and hosted on a separate repo. Told the candidate to either set up their laptop with the libraries installed (friction) or to come onsite an use one of out computers (not possible in remote any longer). Built a 2-3 hour onsite task plus a half-day take home extension that were features already in the production app. Did this for hiring iOS, Unity, React and Python devs and it worked pretty well for all these roles.