Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I have a pretty good career counselor. She said don't get too bogged down if you're not 100% qualified for a position. If you're 80% or more qualified, it's worth applying to. I realized what a difference that made in the range of jobs I was willing to apply to. I haven't been hired yet, but my prospects have improved tremendously.
-
Ignore that BS. make sure you want tobwork there first. Behave as though they need to sell themself to you, and not the other way around.
Keep asking: why should I work for you? what new tech are you working with? That review on glass door was.... they will concentrate on trying to sound good.
it is the way to turn the tables.... -
I spoke to an Intel team leader recently and asked him about the hiring process, I asked him exactly that.
He told me most HR departments recycle hiring templates and don't necessarily adapt them to the actual job description, that if I found a general match I should apply and polish the details at the interview.
As my contractor job ends and my beginning the process of looking for new work the sudden feeling of imposter syndrome starts washing over me.
"I'm not qualified for any of these positions...", I say to myself, but then I think to myself, I wonder how devRanters deal with this.
So let me ask you, devRant, how have you dealt the *Experience Required* section of most jobs when job hunting?
rant
experienced required
i bet hr is fun
∞+ years of experience