Stop writing job requirements for the person you wish you had. Start writing them for the person who can become that and more.
-
-
Replying to @EmilyGorcenski
Consider Node, Django, Rails, PHP. Consider Puppet, Chef, Ansible. AWS, Azure. Grouping by rough exclusivity, that's 24 skill combos.
1 reply 1 retweet 2 likes -
Replying to @EmilyGorcenski
Right there, if you require a single combo, you've cut out 95% of skill combinations. That removes a ton of applicants right off the bat.
1 reply 1 retweet 4 likes -
Replying to @EmilyGorcenski
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.
3 replies 37 retweets 60 likes -
Replying to @EmilyGorcenski
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.
2 replies 1 retweet 2 likes -
Replying to @EmilyGorcenski
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…
1 reply 0 retweets 0 likes -
Replying to @izs @EmilyGorcenski
"familiarity with distributed systems" is applicable whether it was ruby or node or go.…
1 reply 0 retweets 0 likes -
Replying to @izs @EmilyGorcenski
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.
1 reply 0 retweets 0 likes -
Replying to @izs @EmilyGorcenski
spending six months to get an experienced leader is way cheaper than having to fix mistakes later. Hiring leaders is hard.
1 reply 0 retweets 1 like
Certainly, for startups/smaller businesses this is true. But it shouldn't be true for companies with headcounts 500+.
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.