Timeline for How to politely decline a take-home test task
Current License: CC BY-SA 4.0
6 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Mar 10, 2023 at 16:47 | history | edited | Joe Strazzere | CC BY-SA 4.0 |
added 54 characters in body
|
Mar 10, 2023 at 14:47 | comment | added | DKNguyen | @JoeStrazzere It costs the OP nothing to mention it. They can only lose nothing or gain, as do future test participants. | |
Mar 10, 2023 at 9:17 | comment | added | BЈовић | Sorry, but this is an awful advice. He spent hours setting up the environment - not working on the task. The way you wrote, they are going to think he is not capable of doing the task. If I would see what you wrote would be automatically "no" | |
Mar 9, 2023 at 22:37 | comment | added | DKNguyen | @Harper-ReinstateMonica Yeah, oh so important. Not sure how this answer missed that to be honest. | |
Mar 9, 2023 at 19:29 | comment | added | Harper - Reinstate Monica | I would mention that the 3 hours was "just trying to setup the virtualization environment; I hadn't even started on the test." Otherwise they'll assume you had no trouble setting up environment and were stumped by the problem. | |
Mar 9, 2023 at 18:20 | history | answered | Joe Strazzere | CC BY-SA 4.0 |