Story of a full-remote culture
summary
Heetch is a mostly remote-first company of nearly 300 people with about 75 engineers working remote by default and hiring largely inside European time zones; the claim is that success depends on trust, autonomy and rigorous asynchronous documentation rather than fancy tooling. Concrete practices include weekly no remote copy machine calls in random triplets, keeping discussions public, moving long threads to video, pair programming by screen share, and primary docs in Notion with synchronous chat on Slack plus periodic on-site retreats.
AI-written summary · about
chapters (34)
- 0:00Intro
- 0:35About Cment Garcia
- 1:17Remote work habits
- 4:00What is remote
- 4:31Remerged friendly companies
- 6:01Remote first companies
- 7:56Full remote companies
- 10:11Why go for remotes
- 10:27Remote work today
- 12:43Work efficiency
- 14:13Worklife balance
- 16:00Environment
- 18:05Flexibility
- 19:30Advantages
- 19:53Trust
- 20:09Trust your employees
- 21:17Be openminded
- 22:30Rituals
- 24:32Synchronism
- 25:26It doesnt have to be crazy
- 25:58Synchronous postrealtime
- 26:21Unreasonable expectations
- 27:08Synchronism rules
- 28:37Tools
- 29:38Slack
- 32:20Tools List
- 33:22Finding the right tools
- 33:55Offsite team retreats
- 35:20Conclusion
- 36:25References
- 36:45The Bank
- 36:59Questions
- 37:36Tips
- 43:15Outro
related talks
46mHome Alone: How working for a fully remote company actually works
41mA Clear-Eyed Look at Distributed Teams
37mThe Effective Remote Developer
36mDistributed & Local: Getting the Best of Both Worlds
56mMental Health and Working Remote
27m"Thriving in a Connected World"
44m450 Days Remote Only – the Frontastic Experience Report
37mAsynchronous Work: The Next Phase of Remote Work