5 ms·
> I understand the frustration here. I assume Kagi has a lot of candidates and is trying to identify the best ones for handling ambiguity. While I can appreciat
by stephen_g 1y ago
> I understand the frustration here. I assume Kagi has a lot of candidates and is trying to identify the best ones for handling ambiguity. While I can appreciate the interviewee’s desire for more information or a rubric, it might potentially hurt the effectiveness of the take-home assignment.
I mean, potentially they failed the real test by asking all the questions - Kagi specifically say they're looking for people who can deal with an open-ended project, and instead of just deciding to do something cool, they seem to spend a lot of time demonstrating that they can't deal with open-endedness by asking a lot of questions and coming up with a detailed spec and asking for approval before starting.
That's not to say what Kagi is doing is good, but it's probably for the best for the candidate that they didn't get the job because it sounds like they wouldn't flourish in that kind of environment (which is better to know before starting a job, instead of starting a job you're going to hate and then burning out or failing probation)
- krackers 1y ago* Ask clarifying questions: Get failed for not being able to handle ambiguity * Don't ask clarifying questions: Get failed for making assumptions and not identifying business requirements before implementation
- theamk 1y agonope, they asked the clarifying question, and got the response that there are no business requirements: "That is part of the assessment itself, see what kind of extra features you can come up if any." They were failed because they could not deal with the answer, they were not failed for act of asking the question itself. Actually happens sometimes in my work... Q: "Are there any requirements on the database used?" A: "Nope, just make sure the final system will be able to handle the required load"