April 15, 2026 · 11 min read
We're a 24-person team across 12 countries. Here's what actually works (and what doesn't) for remote engineering.
We use CodeSync for pair programming (obviously), Slack for async comms, Notion for docs, and Loom for recorded walkthroughs. That's it. No fancy "remote collaboration platform" — just tools that work.
We don't use email internally. It's too slow. If you need something, Slack us. If it's urgent, call. Simple.
Weekly all-hands on Tuesdays at 9am Eastern. That's 6am for West Coast, 3pm for Europe, 7:30pm for India. Not perfect for anyone, but the fairest overlap we could find.
Engineering does async standups in Slack. Post what you did, what you're doing, blockers. No video call needed. Saves everyone 4 hours/week.
Over-communicate, then over-communicate again. In an office, if you're stuck, someone sees your face and asks. Remote: silence is ambiguous. If you're blocked, say it. If you're heads-down for 4 hours, say it. Default to more info, not less.
Time zones are real. We don't schedule meetings outside 9am-1pm Eastern. Ever. If someone regularly has to wake up at 6am for meetings, that's on us, not them. We failed at scheduling. For more on this, this guide covers most of what we learned (sometimes the hard way).
Onboarding is harder than you think. Our first remote hire: we sent them a laptop and said "figure it out". They almost quit in week 2. Now we assign a buddy (not their manager) and do a team lunch on their first day. Small things, big difference.
We don't care about degrees or fancy past companies. We care about: (1) can you actually code?, (2) can you explain your thinking without being in the same room?, and (3) are you self-directed? The third one is the killer. If someone needs constant feedback, remote won't work.
Want to join us? Check open positions. We're hiring across engineering and design. Time zone flexible, but you need to be comfortable working async.