> Hiring managers acknowledge that nearly all job applicants exaggerate their qualifications, for instance.
Is that an expectation now?
Is that an expectation now?
In that regard, from what I hear on forums and now live from the sister of my wife, us became a low trust society for job applications..
So.. Better safe than sorry?
I'm like you. Unless I have near complete over a subject, I don't list it. I'm thus jobless.
I believe it all depends on how ~structured the industry is. For small gigs for instance, you get direct view of the tasks and problems to fix. You can rapidly tell the customer if you know or not. In highly layered places, you get to talk to many HR that don't know what computing problem solving is, and will react negatively if you're not inside a box.
I just passed some technical tests for a job. The questions were very basic. Compared to this, I should list it as senior skills. Actually that's the only reason I'm interviewing, to get a sense of what people want and how they grade it.
ps: I also wonder how many people get angry at interviews due to that.
Outside of something like nodejs, I'm not even sure 3 years will get you through the experience of a version upgrade with some tech stacks, let alone "senior" qualifications. But it will all come down to how you define "senior".
I know a lot of things I learned in python on my own wouldn't happen in a job because you don't have time to play with everything in the language.
From game theory, the "solution" is to favor cooperation anyway, but not absolutely. So you might miss out on some jobs, but the one you get will be better. Then again, there's a reason it's called game theory. ;)