Stop writing job requirements for the person you wish you had. Start writing them for the person who can become that and more.
-
-
It doesn't make sense to leave a position open for 3 months looking for someone who can hit the ground running vs training someone in 1 mo.
-
I've passed over dozens of positions that require some specific combo XYZ because I have no confidence that I can sell my skills as related.
-
this is a good point about why the tech stack resume checklist is so toxic. At npm we try to hire for more broad indicators…
-
"familiarity with distributed systems" is applicable whether it was ruby or node or go.…
-
the harder thing, as a founder, is hiring for a skillset I don't have, eg to build a new biz function. Can't train.
-
spending six months to get an experienced leader is way cheaper than having to fix mistakes later. Hiring leaders is hard.
-
Certainly, for startups/smaller businesses this is true. But it shouldn't be true for companies with headcounts 500+.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.