Timeline for How to handle interview technical tests that are absurd (e.g. an unreasonably large task with a short time limit)?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Dec 5 at 20:27 | history | suggested | MisterMiyagi | CC BY-SA 4.0 |
Link to referenced answer to stay future proof
|
| Dec 5 at 4:41 | review | Suggested edits | |||
| S Dec 5 at 20:27 | |||||
| Aug 7, 2018 at 12:27 | comment | added | CJ Dennis | @VolkerSiegel This is one reason why I don't like referring to other answers. The one that starts "By walking away from them." | |
| Aug 7, 2018 at 10:46 | comment | added | Volker Siegel | Which top rated answer exactly? | |
| S Aug 6, 2018 at 11:22 | history | suggested | doppelgreener | CC BY-SA 4.0 |
removed EDIT / ANSWER / EDIT headings. answers should ideally be presented as a final version at any given stage -- imagine reading a wikipedia article that said "EDIT" "ORIGINAL ARTICLE" "EDIT".
|
| Aug 6, 2018 at 10:05 | review | Suggested edits | |||
| S Aug 6, 2018 at 11:22 | |||||
| Aug 3, 2018 at 4:47 | comment | added | Wildcard | While I do think the OP was probably better off not working there, I think it's great you give actionable suggestions he can actually use for improvement. +1; I do this type of communication every day, and it's one of the most important parts of my job in actual fact. Correct estimation of effort and setting accurate expectations (which doesn't mean "lowering expectations" either, by the way; sometimes people estimate 4 months when it can be done in 2 days). | |
| Aug 3, 2018 at 1:06 | history | edited | CJ Dennis | CC BY-SA 4.0 |
Feedback due to downvotes
|
| Aug 2, 2018 at 1:42 | history | answered | CJ Dennis | CC BY-SA 4.0 |