Remote Work Success at Maincode
Our team is distributed across continents and time zones, allowing us to investigate, build, and ship around the clock. Our globally distributed team relies on our principles to drive decisions forward, even when the team isn’t all available. Whether our main medium is Slack, Notion, or a video call, our principles create the shared foundation from which we collaborate, allowing us to make decisions quickly and independently across time zones. Here’s how some of our teammates in our broader distributed team apply our principles to remote work.
Distributed, but Never Disconnected
Whether it’s early-morning Notion edits or late-night pull requests, our team spans oceans but feels like one room. We’re thoughtful about our onboarding and collaboration, ensuring that teammates can onboard in the HQ in Melbourne and get to know and influence team culture before working remotely.
Move Humans Forward
We design meetings, tools, and docs to reduce friction for teammates, not add to it. We ruthlessly evaluate our communication and meeting cadence to ensure that each person at each meeting feels that it’s the best possible use of their time. We advocate for timezone fairness and inclusive collaboration practices.
Do The Hard Thing
At Maincode, we choose ambitious goals and pursue projects worth doing. Our mission pushes us to confront complex problems and demands our best thinking. In practice, remote work means disciplined, purposeful effort: diving deeply into code, carefully shaping new products, or crafting bold ideas. But deep work alone isn’t enough. After periods of intense focus, we surface to reconnect, share discoveries, and refine our thinking together. This cycle of independent depth and collaborative clarity allows us to build meaningful things, even from afar.
Take Point
Maincoders are builders — which means we take initiative, volunteer visibly, and don’t wait for work to be assigned. When something seems ambiguous or broken, we step in. We signal ownership and follow through, async or not.
It’s 2AM in the Lab
We prioritize time for deep focus and protect our flow states—whether it’s 2AM or 2PM. We’re intentional about balancing connection with concentration, keeping meetings meaningful while preserving space for uninterrupted, heads-down work. We respect the creative process and make it a habit to share both breakthroughs and roadblocks openly, so the whole team learns and moves forward together.
Stay Foolish
We use async tools to stay curious, ask questions, and spark ideas. We create low-stakes prototypes and test scripts without waiting for consensus. And we encourage others by validating naive-sounding but thoughtful questions.
Are High Voltage
We bring energy and presence to our remote rituals, maintain high craft and clarity in our artifacts, and notice and amplify teammates who raise the bar, especially quietly.
Ship
At Maincode, shipping is sacred. Not just code, but ideas, processes, prototypes, and documentation. Share the first draft, the internal memo, the raw insight. Maincoders use async tools to move work forward.