4 ms·

My favourite is when the company rejects you with no feedback then asks that you do not post your code for the challenge in your portfolio

• gedrap 12y ago
  Feedback, as discussed a lot, is a dangerous thing. May start endless discussions, trying to see things as racist/sexist/whatnot, and it's meaningless as decision is already made. Most of the challenges take an hour or two, so not sure how that would benefit your portfolio. In case challenge was longer than that, well, that's a different question (accept it or not).
  • jarek 12y ago
    I've seen a YC company give a challenge that took a weekend to complete. (Relatively late in the hiring process.) It was interesting and relevant to career goals. I understand the rejection and the lack of feedback, but the do-not-publish request is infuriating. Supposedly the reason is to not give code to other candidates but the companies should be able to detect that trivially by diffing or talking about the code with the candidate. I've routinely seen coding tasks designed to take a Saturday. edit: sorry to see your post downvoted, I upvoted it