How to build a kick-ass remote Scala team
summary
Argues remote hiring multiplies the talent pool (New York is ~0.9% of global engineers), cuts turnover and sick days, and boosts productivity; recommends posting on AngelList and Stack Overflow and using remote boards, and choosing tools like Twist or Basecamp instead of noisy Slack defaults. Prioritizes can-do attitude, trust and explicit communication over raw algorithmic skill, decides compensation policy up front, starts onboarding before day one with hardware and buddy rotations, and treats timezone overlap and synchronous vs asynchronous tradeoffs as concrete constraints.
AI-written summary · about
chapters (9)
- 0:00Start
- 6:41Employees Are HAPPIER
- 9:16Good Remote SUPPORT
- 12:44What's Your PROCESS
- 15:28What About COMPENSATION
- 17:59WHAT is Important for You
- 21:54How do You EVALUATE Candidates
- 31:57FORGET About the Office
- 35:02Over COMMUNICATE
