3 ms·
Total BS! People are willing to learn anything and everything to land and keep a job. The problem is the HR/Recruiting process using buzzwords/jargons/fads to
by rramadass 3y ago
Total BS!
People are willing to learn anything and everything to land and keep a job. The problem is the HR/Recruiting process using buzzwords/jargons/fads to screen applicants in a all or nothing manner.
- tracker1 3y agoThis... Especially recruits who don't understand what they're looking for... You have to sell through the recruiter, then the amount manager before anyone with a clue sees your resume. And those first two states you pretty much need to be as arrogant as possible... If you're honest and say you're a 7 at something, they drop you for not being a 9... May as well lie. And by 7 vs 9, to me a 9 or 10 is someone who literally someone who works on the language or platform... I've used JS since 1996 and know it far better than most, I still don't feel comfortable calling myself a 10 with it...
- ahallock 3y agoI've had similar experiences. One recruiter within the company said they had an offer ready for me and then asked about my React experience at the last second. I was completely honest that I was still getting up to speed on React but had used similar frameworks and done front-end since the late 90s. I got ghosted.
- gymbeaux 3y agoI condone cheating on interviews. Don’t lie on your resume, but check GlassDoor for interview reviews- more often than not you see exactly what they’re going to ask you about. One interview I saw they ask candidates about SOLID principles and the three dependency injection lifetimes in C#. I made sure I had those on lockdown (and by lockdown I mean up on my computer screen during the phone call). It’s absurd that you’re expected to know things like SOLID like we say a pledge of allegiance every morning about it… I, like most, follow SOLID (more or less) without realizing it.
- tracker1 3y agoSolid as a religion bugs me... Not as much as "Clean Code" patterns in the .Net space. You usually don't need half the level of separation in practice especially for micro services. Write similar code. Have classes that represent the concern from a feature perspective instead of a technology perspective. Etc.