DEV Community

Discussion on: Assessing technical tasks

Collapse
bretthancox profile image
bretthancox

If you can, categorize your comments. Write "core scope" and "nice to have" sections. Keep it factual, not emotional or opinionated. For accessibility, maybe reference standards. Worst case, they ignore the section.

If you have a deadline, focus on the core scope first, then document nice to haves within the remaining time.

Collapse
adam_cyclones profile image
Adam Crockett Author

Excellent pointers, I have taken issue with something said in the CV that is not reflected in the technical test and it is not actually critical but it makes me worry. Should I shrug it off, after all the time to do this task is short and meant to be incomplete. Overall the candidate has not used X framework before and prefers Y but has done well, that is enough and we could teach him the rest. However the position is higher than my own, feel as if I should give developer a chance to talk it through.

Collapse
bretthancox profile image
bretthancox

I think hearing their logic will help you. I can't imagine anyone you'd want to work with getting annoyed by that. It might allow you to feel more confident about their skills.