For me , what matters is how they think, how they interact with others and
how they solve problems. The candidate's mindset and drive is more
important than the technological wizardry they might possess. Not knowing
our technology is not a deal-breaker. I've hired people who didn't know
ruby and rails before, and it turned out to be a very good decision.
For Viki, the process is a 30-60 minutes talk and a 2-3 hours programming
task, working together with one or more of the existing team members. (Pair
Anyone can veto the hire.
We work as a team, interact all the time, solving problems and getting
things done. If I see any signs that anyone is uncomfortable, I probably
pass on the candidate, even if he is very strong technically.
On Thu, Mar 15, 2012 at 4:26 PM, Pete Kim <raingr...
> +1 for looking at open source contributions in github
> You received this message because you are subscribed to the Google Groups
> "Singapore Ruby Brigade" group.
> To post to this group, send email to email@example.com.
> To unsubscribe from this group, send email to
> For more options, visit this group at