Fun fact: I joined Fujitsu in 2019 thanks to a call from a former colleague at LOYSTBOYS. They needed help resolving a major infrastructure outage for one of their clients — and, well, I do love a good puzzle.
After helping them get everything back on track, I was invited to chat with Fujitsu about joining their team. Ironically (or perhaps perfectly), the very environment I had helped restore would later become the client I'd work with for years: Gemeente Almere.
My journey at Fujitsu started the way many good IT stories do: with an outage.
I was asked to assist with a major infrastructure incident at one of Fujitsu's client environments. Together with the team, we stabilized the situation and restored services — and that moment sparked a deeper conversation. Not long after, I officially joined Fujitsu.
Sometimes solving the right problem at the right time opens unexpected doors.
Once on board, I stepped into the role of Client Lead Engineer, acting as the technical bridge between Fujitsu and client organizations.
In practice, this meant: Being the primary technical point of contact for complex client environments Translating business needs into clear, actionable technical solutions Supporting architects, service managers, and engineering teams with hands-on expertise
One of my main client environments during this period was Gemeente Almere, where I helped modernize infrastructure and establish a stable technical foundation.Then came the year that changed how everyone worked.
When remote access suddenly became critical, I worked within Fujitsu teams to rapidly scale and improve: Virtualization platforms Network capacity Citrix and remote access solutions What started as emergency scaling turned into a durable, production-ready remote working environment, supporting thousands of concurrent users without compromising performance or stability.
As environments matured, the focus shifted from “make it work” to make it work well.
During this phase, I contributed to: Improving change and request workflows between Fujitsu and client teams Clarifying technical ownership and responsibilities Strengthening documentation and operational clarity The goal was simple: fewer surprises, smoother collaboration, and systems that could be maintained confidently by any engineer stepping in.
In the later stages of my time at Fujitsu, I supported complex transition and migration activities as client engagements evolved.
This included: Preparing environments for vendor transitions Consolidating and validating technical documentation Supporting hybrid operations during handover phases Ensuring privacy, data integrity, and continuity until the very end There's something satisfying about leaving an environment in a clean, well-documented state — no loose ends, no mysteries.
My time at Fujitsu was defined by trust, responsibility, and collaboration. I worked across incidents, long-term projects, modernization efforts, and final transitions — always with the same mindset: build solutions that last, and leave things better than you found them.
