4 ms·
> we never get told what we're being scored on in advance I make a point of not telling you. I want you to demonstrate that you're able to work out the require
by koala_man 9y ago
> we never get told what we're being scored on in advance
I make a point of not telling you. I want you to demonstrate that you're able to work out the requirements when you're given a task.
Some people will take a task, go off for a few weeks, develop ill-fitting solutions, and then say "well, you didn't say you wanted unit tests" or "you didn't tell me it had to support files that can't fit in memory".
Others will try to find out what's needed, with simple questions like "Roughly how big are these files?" and "Does this actually need to run in line with the front page? What if we load it asynchronously?"
I'm looking for the latter.
- jnordwick 9y agoI generally give all the important parts of the question up front. Having to fish for requirement isn't the point.
- heartbreak 9y agoI like to leave at least something small ambiguous to see if clarification is requested. My clients rarely give unambiguous requirements, so I feel it’s pertinent to the job.
- nnd 9y agoDepends on the role, if it requires high levels of autonomy and working with highly ambiguous product definitions (e.g. most freelancing jobs) - then it's a part of your role to constantly fish for requirements or even suggest your own requirements.