Loopjet’s engineering teams are based in Germany and Malaysia. People sometimes assume a distributed setup like this is a compromise — something you tolerate for cost reasons and work around with heavy process. For us it’s the opposite: the two locations are a core part of how we deliver for clients in 12 countries.
The day is longer than your office hours
The time offset between our two locations means the team covers most of the clock without anyone working nights. Work handed off at the end of a European day is moving again before that engineer wakes up. For clients, the practical effect is simple: things happen faster, and problems rarely wait long for a pair of eyes.
This is one of the quiet reasons behind our four-hour average issue resolution time. Coverage beats heroics.
One team, not two vendors
The setup only works because we run it as a single team. Same codebase standards, same review process, same tooling, same definition of done — whether the commit comes from Germany or Malaysia. Every project has one responsible lead, so clients never have to figure out “which office” to ask.
A few habits keep this honest:
- Written by default. Decisions, designs, and status live in writing, where every time zone can read them — not in meetings half the team slept through.
- Overlap hours are sacred. The hours when both locations are online are reserved for the conversations that genuinely need to be live.
- Ownership over assignment. Features are owned end to end by one person, so handoffs transfer context, not responsibility.
Different perspectives make better products
Our products are used by more than five million people across very different markets. Having engineers who live in different cultures, infrastructure realities, and user expectations is a quality advantage — assumptions get challenged early, before they’re baked into the product.
A flow that seems obvious in Berlin may confuse users in Kuala Lumpur, and vice versa. We catch a lot of that at the whiteboard instead of in support tickets.
What this means if you work with us
You get a team that responds quickly regardless of where you are, communicates in writing you can actually follow, and brings more than one worldview to your product decisions. The geography is invisible day to day — the responsiveness isn’t.
Curious how we’d staff your project? Tell us what you’re building.