The coffee machine sputtered as if it really didn’t feel like it. It was 06:50 in the morning. Outside, a heavy, gray rain blew hard against the large office windows. I stood in the semi-darkness, quietly waiting for an espresso that always tastes like scorched earth from this machine. Absolutely no one else was present. Only the deep hum of a server rack down the hall broke the silence. In the past, this extreme silence would have immediately made me nervous. An approaching project deadline, rows of empty desks, a towering stack of unresolved tickets. Now, I looked unconcerned at the sliding drops on the window. The concept of hiring remote software developers was probably the best thing we did last year. No more blind panic in the early morning. Just the lonely sound of a slow coffee machine and the realization that the heavy lifting has already been done elsewhere.

On the project manager’s empty desk lay a dried-up apple. It had been lying there quietly since Tuesday. I mindlessly threw it in the trash can. The trash can was otherwise empty, because the regular cleaner only comes by on Thursdays nowadays. It’s those strikingly small details that suddenly stand out clearly when the constant noise has disappeared from your workday. For years, we were blindly chasing the facts. Vacancies that stood lonely and open for months on the well-known job boards. Applicants who didn’t show up without any notice. A local labor market that had completely dried up to the bottom. You slowly get used to always being in survival mode. To unintentionally making concessions on the final quality, purely because there simply wasn’t anyone else available to write the code.

Just last week, I read an extensive report about that persistent shortage. The Labor Market Dashboard of Statistics Netherlands (CBS) shows relentless graphs that all mercilessly point in the same direction. Shortages. Mismatches. An endless red line of unfillable IT positions. It is the inevitable reality that everyone always talks about at those mandatory, lukewarm networking drinks. They complain bitterly about sky-high salary demands and external recruiters laughingly asking for top dollar. I often just nod understandingly and quietly drink my beer. I rarely tell them exactly how we solved it. People somehow don’t believe it anyway if the solution sounds too simple. Apparently they want to hold on to that struggle, I sometimes think. They subconsciously believe that true value must always hurt first.

When we finally took the plunge last year, it was purely out of absolute necessity. We urgently needed to scale up flexible IT capacity for a loyal client who suddenly wanted to become three times as large in the market. It was a stunningly beautiful, extremely complex project, but we simply didn’t have the technical people to lay down the necessary building blocks. The backend was still completely wide open on the drawing board. The frontend even had to be designed from scratch. Evening after evening, I sat shuffling together complicated schedules that never added up in the end. You can stare for hours at a spreadsheet full of colors, but empty cells don’t spontaneously turn into experienced programmers. We immediately needed a reliable outer layer. People who could step in right away without us locking ourselves financially into stranglehold contracts and structurally high fixed labor costs.

The first serious conversation with Mantab One was surprisingly and refreshingly down-to-earth. No slick, hollow talk about synergy, no smooth presentations about so-called disruption. Just a highly solid conversation about pure code, about available hours, about what concretely was and absolutely wasn’t possible. They very consciously focused on IT outstaffing for SMEs in the Netherlands. That initially sounded like a dry bureaucratic term, but in practice, it simply meant that they took care of all the administrative red tape. We got the necessary developers directly on our team, they did the rest unseen. I was naturally quite skeptical in the beginning. You sometimes read wild stories online about terribly difficult communication or completely unreadable scripts from abroad. But the promise of zero overhead and no continued payment during sick leave was simply too tempting from a business perspective to just ignore.

We deliberately started very small with exactly one strictly defined project. The cautious thought of seriously considering outsourcing software development to Indonesia really felt like a leap into the dark unknown at first. The country is a whopping twelve thousand kilometers away. You obviously can’t just quickly hop in the car if the production server unexpectedly crashes. But physical distance has nowadays become a completely relative, almost meaningless concept in modern technology. We were soon sent extensive profiles of exceptionally talented developers. No insecure juniors who still had to figure out exactly how a repository works on a daily basis, but mature professionals with deep, irrefutably proven experience. Furthermore, they had already gone thoroughly through an extremely heavy technical screening. We really only had to nod in agreement.

The quiet morning and hiring remote software developers

During those first awkward weeks, I secretly paid attention to absolutely everything. Unconsciously, you search all day for small cracks in the presented system. You wrongly expect the daily communication to run extremely poorly or that the time differences will sooner or later clash mercilessly with our office hours. The strange thing in the end is that this apparent distance actually brought us enormous, lasting peace. When I open my laptop early in the morning at a quarter to seven, the team on the other side of the world has already put in a solid workday. The agreed-upon pull requests are ready, neatly documented. The tickets have been seamlessly and controllably moved to the testing phase. While the city still sleeps and the very first trains here are picking up their usual delays, the silent engine of our production smoothly runs at full speed.

I poured my dark coffee into an old mug with a small, ugly crack in the handle. The coffee was unfortunately still slightly too bitter, but it was warming at least. Outside, a heavy garbage truck drove backward into the narrow street, squeaking and groaning ominously. The shrill sound cut sharply through the otherwise deserted room. Inside on my illuminated screen, I scrolled through last night’s fresh code in deep silence. It immediately looked remarkably clean. Clear and highly logically structured. The fundamental architecture of the application stood as solid as a rock. It is exactly that high, rare stability that you hope to find as an agency. They apparently have an impressive, deep pool of talent over there in Southeast Asia, and you really feel that immediately in every written line.

Of course, things occasionally rub during a complex project. An unexpected misunderstanding about a very specific feature, or a task that, in hindsight, was described just a bit too vaguely on our end. But the daily, mandatory integration goes surprisingly smoothly at the bottom line. During the regular short video stand-up, I see serious faces staring at the screen just as focused and driven as we are. They truly function effortlessly as synchronous, full-fledged members of our own permanent team. Internally, it hasn’t felt like speaking with an external, cold supplier for a long time. They have simply become our colleagues. Only, in these dark months, they don’t wear thick, wet winter coats in the hallway, and they simply never complain about the cold Dutch wind.

Setting up a dedicated development team without the noise

Somewhere in the continuous, chilly rain of early November, we decided to push through definitively and on a large scale. Setting up a dedicated development team ultimately turned out to be procedurally much easier than the sluggish process of arranging that tiresome municipal parking permit that took me months locally. No endless legal contract negotiations at round tables. No worried internal HR department stressing for weeks about adapted secondary employment conditions, complicated pension schemes, or broken ergonomic office chairs. At the end of the day, you only pay for the actually registered productive hours. It is a completely transparent, clear model that perfectly matches an agency that wants to remain light, modern, and extremely agile. The hard guarantee of available backup capacity concretely means that we never unwillingly grind to a halt again. There is virtually always someone ready to take over the abandoned keyboard.

The office now very slowly started to trickle a bit fuller with people. My partner walked in remarkably hurried, shook out his soaking wet, black umbrella over the doormat, and muttered under his breath for a moment about an unexpected local road diversion. He then casually asked if the large database had already been successfully migrated to the new environment. I nodded to him extremely calmly. The migration was completed on time, the very last persistent bugs from the previous sprint were fixed, and the completely new beta module was safe and sound, ready on the testing environment. He just looked at me briefly in surprise, grabbed a tea towel from the top kitchen cabinet, and walked silently to his regular spot. We really didn’t need to waste any more words on it. That flawless morning is quite simply worth its weight in gold to us.

The level-headed decision around hiring remote software developers

For just a moment, I briefly thought back to that dented, heavy saucepan in my own modest kitchen at home. That heavy, inconspicuous black thing faithfully does its job every early morning, without noise, absolutely without drawing unnecessary attention. Something like that doesn’t need to step into the foreground with an extraordinary amount of racket. In our view, technology doesn’t need to scream for constant recognition. It all just needs to always work flawlessly when you turn it on. That is the fundamental reason why hiring remote software developers has proven to be our ultimate salvation in this tight market. Ultimately, it’s not at all about frantically celebrating trendy, fleeting disruptive concepts on LinkedIn. For us, it’s about rock-solid, predictable continuity. About the reassuring daily certainty that the project safely and steadily continues behind the scenes.

Fortunately, we have now found a very pleasant, steady cadence in almost all our ongoing projects. The sudden spike in assignments that used to immediately give us a severe stomachache, we now handle almost carelessly in practice. We finally possess the scalability we so desperately sought. Thankfully, our own local people are once again focusing on the big picture, on direct customer contact, and on the architecture of the distant future. The daily execution, the hours of mouse-quiet and concentrated typing, is in extremely safe hands on the completely opposite side of the ocean. It is a simple, elegant division of roles that has completely saved the overall atmosphere in our organization. When we brought in external talents, the constant, grueling breathlessness disappeared immediately.

With my mug, I slowly walked back to the large, cold window. The hard, boisterous rain had meanwhile turned into a very soft, gray, misty drizzle. The bright yellow streetlights blinked out silently one by one on the street below. A new, undoubtedly busy workday was now officially beginning, but in fact, the hardest part behind the scenes had already been successfully completed. That abstract realization gives a peculiar kind of quiet, deep satisfaction on these kinds of mornings. As a commercial company, you really don’t have to frantically bring everything into your own physical house to be lastingly successful. Sometimes the absolute best solution is the one you simply cannot physically touch. Often, the biggest step forward is purely a matter of rational letting go and fully trusting the processes and systems you have sensibly set up.

The coffee machine’s bean grinder gave a loud, final click. It was high time for a second, hopefully slightly better cup of coffee. My laptop’s large screen lit up softly with a brand new, extremely short message from distant Jakarta. A friendly, simple good morning, immediately followed by a clean, working link to the new live environment. Absolutely everything was running exactly as it contractually should. The decision around hiring remote software developers once began somewhere in the past as a blind emergency measure, a desperate, expensive way to plug a painful gap that we locally could not possibly fill anymore. Today, however, it is the silent, rock-solid foundation beneath absolutely everything we build. No grand, hollow words. Only clean, working code, and calmness.