gakonst
@gakonst
we've hired 100% of our team from our github contributors: 1. can they scope a good issue? 2. can they code a good pr? 3. can they go through a good code review? 4. can they repeat the above a few times? https://t.co/J7UoQcaB5n
9 replies
195 recasts
171 reactions
Samuel
@samuellhuber.eth
Action >>> words. It just makes too much sense to hire that way. Though it also requires a commitment to opensource that for some companies is hard to quantify and therefore gets thrown out
0 reply
0 recast
4 reactions
Roberto Bayardo 🎩
@bayardo.eth
Not everyone's contributions are in a public source repo though. I interviewed a bunch of entitled RS applicants while at Google who had this kind of attitude about coding interviews; usually these types you don't want to hire anyway. We still hired many brilliant theoriticians who never wrote "real" code prior.
0 reply
0 recast
0 reaction
Vladyslav Dalechyn
@dalechyn.eth
also hitting the same requirements but noticed the next: - some devs "download" others projects, hit the "initial commit" and pin that in their profiles; - some are purposefully rewriting git history to replace commit authors;
0 reply
0 recast
0 reaction
Joaquim Verges
@joaquim
Best hiring pipeline by far. https://warpcast.com/joaquim/0x8b375d9b
0 reply
0 recast
0 reaction
alvaro delgado
@imalvarodelgado
How would you translate this to non-technical / marketing / ops? Curious to know how you value portfolio.
0 reply
0 recast
0 reaction
Wise
@wise-eth
@askgina.eth what does it mean to scope a good issue?
0 reply
0 recast
0 reaction
Robotandkid
@robotandkid
There's trade offs for sure. Like there's a whole swath of devs that are good for your team but maybe haven't had a chance to contribute to your project. On the plus side, the peeps you hire have already done the equivalent of a job interview.
0 reply
0 recast
0 reaction
