3 ms·
> [...] I'm wondering how much people on HN lie or exaggerate on their CV. Not even the slightiest bit. If anything, I tend to leave things out, the ones that
by dozzie 10y ago
> [...] I'm wondering how much people on HN lie or exaggerate on their CV.
Not even the slightiest bit. If anything, I tend to leave things out, the ones
that are unimportant compared to rest, that are very old, or that I don't want
to admit I know.
> Is this a bad strategy?
It is. It can very easily backfire. You don't know in advance which parts of
the requirements are critical (and thus they'll ask you about them), and if
you'll get caught lying, you're done immediately.
> Some roles seem to ask for experience in technologies that would take a few hours to learn at best.
You either look at the wrong job posts or heavily underestimate what does it
take to be competent with those technologies.
As pixeloution said, if you think it only takes few hours to get proficient
with a tool, try doing so. If it was easy, then you have some justification to
put some knowledge about the tool in CV.
- devhead 10y ago> You either look at the wrong job posts or heavily underestimate what does it take to be competent with those technologies. I disagree, a job "requirement" may not really be one. the people who write the requirements sometimes don't understand them and what the context is to their business. someone just says, they better know python. but when you talk to them, you find out that one dude ten years ago wrote a python script that we need to continue to support. you don't need to be an expert to handle that.
- deleted 10y ago[deleted]