> Are these tests supposed to reflect real-world programming?
That absolutely is the expectation.
These are not tests for basic coding proficiency.
These are not tests to see whether you can build a single component or widget.
These are tests to check if you can build a full suite of components or widgets including a README, tests.
... and candidates are apparently delivering.
I can get a GraphQL/Express server up and running from a frequently used template I built, in 90 minutes will full support for Query, Mutation and Subscription.
Create new users, tasks, updates, votes?
Check Update users, tasks, updates, votes? Check
Get realtime notification of changes to users, tasks, updates, votes? Check
Apparently there are others who can not only do this but also implement a react frontend that puts the UI support for these as well in just 30 minutes more.
Either candidates are reusing templates they have built in previous projects and not reporting the time it took them to build the template when they report the time
Or, they are grossly under-reporting the time it took for them to complete the assignment.
We are doing this to ourselves. We should not deflect the blame.
If we feed garbage data to companies and then companies base their decisions off that, it's absolutely unfair to blame companies for not being realistic
The company was still advertising the role a few months ago. There could be more than one, or maybe they hired someone who has since left, or maybe they haven't found anyone yet.
Companies are trying to minimize the time/money they spend on each interview.
Clarifications cost money.
Hoping a company will engage in a "what really are your requirements? are you trying to test my basic coding competency or do you want to see the best I have got?" will elicit a very vague response, if any.
That absolutely is the expectation.
These are not tests for basic coding proficiency.
These are not tests to see whether you can build a single component or widget.
These are tests to check if you can build a full suite of components or widgets including a README, tests.
... and candidates are apparently delivering.
I can get a GraphQL/Express server up and running from a frequently used template I built, in 90 minutes will full support for Query, Mutation and Subscription.
Create new users, tasks, updates, votes?
Check Update users, tasks, updates, votes? Check
Get realtime notification of changes to users, tasks, updates, votes? Check
Apparently there are others who can not only do this but also implement a react frontend that puts the UI support for these as well in just 30 minutes more.
Either candidates are reusing templates they have built in previous projects and not reporting the time it took them to build the template when they report the time
Or, they are grossly under-reporting the time it took for them to complete the assignment.
We are doing this to ourselves. We should not deflect the blame.
If we feed garbage data to companies and then companies base their decisions off that, it's absolutely unfair to blame companies for not being realistic