4 ms·
I think the huge proposal (after several rounds of questions) was what sunk him. The instructions did not request a proposal, and submitting one, especially one
by ryandrake 2y ago
I think the huge proposal (after several rounds of questions) was what sunk him. The instructions did not request a proposal, and submitting one, especially one that detailed, conveyed “OP cannot take the initiative and proceed with work without seeking approval beforehand.” The project was about asking a few questions, listing a few assumptions, and giving yourself approval to confidently dive in and build something ambiguous. Maybe I’m wrong, but I don’t think the code mattered after that email was sent. The company should have just ended it there without him wasting his time building the assignment.
- lern_too_spel 2y agoThat's the blogger's point. The hiring manager saw the proposal, knew that wasn't what he wanted, and then proceeded to waste an entire week of the candidate's time while he was looking for income.
- roncesvalles 2y agoWhat do you want the HM to say? "Actually, don't bother anymore, you've already failed"?
- yablak 2y agothat's what the OP wanted.
- MeetingsBrowser 2y agoyes. "Please don't spend a week implementing this proposal". Early reject or give some indication that the scope should be much smaller.
- 4b11b4 2y agoI also read that proposal and thought: "it's over".
- Terretta 2y agoThe proposal itself was almost certainly written by an LLM, rather than by someone familiar with the tools that ChatGTP came up with for him.