450 Days Remote Only – the Frontastic Experience Report
summary
Henning Emmrich explains Frontastic’s 450-day experiment operating as a fully remote engineering organization, describing why they rejected a central startup office and common reservations about remote work. He outlines concrete remote-native practices and artifacts (written culture, hiring processes, freelancer collaboration), discusses operational issues like international employment contracts and how DevOps, frontend and backend teams stay synchronized, and mentions tools such as Slack and expected future challenges to watch for.
AI-written summary · about
chapters (5)
related talks
48mA 100% Remote Tech Team: It Works! / A 100% Remote Working Tech
36mRemote work is here to stay: and what's next?
42mSustaining Remote – First Teams.
39mRemote
40mBeing a remote developer
29mRemote(ly) Better Than Before
23mYears of fun as remote manager of remote workers
39mPerks and Pitfalls of Building a Remote First Team