4 ms·
Hi I just looked at your site. I found this very odd. RESPECT YOUR CANDIDATES Strictly timeboxed tasks ensure candidates don't feel pressured to devote silly a
by werty1 9y ago
Hi I just looked at your site. I found this very odd.
RESPECT YOUR CANDIDATES
Strictly timeboxed tasks ensure candidates don't feel pressured to devote silly amounts of time to interview coding exercises.
The biggest issue I've found as an dev looking for work is that, employers often want a full functioning, production grade, api, with tests, and some integration tests. These requirements cause the issues, and timeboxing would surely compound them?
I guess there's a learning curve for the potential employer, but as an employee I wouldn't want to potentially be a guinea pig while they get their act together when understanding how long a task should actually take.
- davidbanham 9y agoThe strictness of the time limit works both ways. They'll be comparing you against other candidates who had the same amount of time. If nobody got a complete solution done, nobody is advantaged or disadvantaged. The employer onboarding is designed to guide them towards the best practices I've discovered. 40 minute time limit and a clear expectation set in the challenge instructions that a "perfect" response is not possible in the time provided, so just do what you can and submit what you've got. That avoids clustering responses near the top of the curve. It also provides talking points for the interview. "So, given unlimited time and budget, where would you go from here to make this code production ready? If you needed to scale it to an OOM more throughout, where would you start optimising?" Etc.