Hacker News Reader

Provided you or the arbitrary interviewer have the technical background to evaluate the answers! I once had reason to view the resume of a former colleague who took all credit for a major project I implemented. This project involved parsing and a particular parser generator. He worked on it after I implemented it, but he claimed it all. And he was knowledgeable enough to back that claim up!

View on HN

> And he was knowledgeable enough to back that claim up!

If he worked on it and could convincingly fake it, I - as a recruiter - wouldn't care too much if he embellishes a bit and claims he also did it from the start. Maybe he factually didn't, but if he's good enough to make me think he did, there's a decent chance he would be good enough to actually do it for me. Not a certainty, there's never certainty, but a good chance. Of course, given the choice, I'd prefer the one who actually created it, but one who worked on it and knows it well enough is not bad either.

The point is the hiring method attracts people who are both not genuine , to admit that they just jumped in on an impressive project and insecure enough , that they think they should claim everything as their own ... It doesn't matter if they actually possess the technical skill as there might be behavioural issues between this person and the rest of the team.

Reply on news.ycombinator.com