There is a particular kind of pressure that comes with owning the “glue” layer of a system used by millions of people.
Not the pressure of a looming deadline — that is manageable. The pressure I mean is quieter: the knowledge that any architectural decision you make today will either compound cleanly into the future or generate a tax that slows every engineer who touches the codebase for years to come. Getting that right, consistently, across teams and competing product priorities — that is the real craft of software architecture.
I have been working in that space for most of my career.
The enterprise years
Since 2017, I have built and led engineering across the full software lifecycle — from macOS desktop tools at appsolute (MAMP/MAMP PRO) to high-security health-tech platforms at Vivy GmbH, an Allianz startup, where my work on the MVP directly contributed to the company securing its final investment tranche. Most recently, I have been the lead engineer for the Core Horizontal Team at Bedrock Streaming GmbH in Cologne — a team responsible for the seamless integration of video, audio, and live content across a major European streaming platform, initially only for RTL+ in Germany, later added to Videoland in the Netherlands, M6 in France, and RTL+ in Hungary.
That last role shaped how I think about systems. The Core Team is not a product team. It does not necessarily ship features visible to end users. It ships mainly the invisible infrastructure that makes features possible: the architectural contracts between vertical squads, the shared frameworks, the Snapshot Testing Foundation that I built and rolled out to every internal developer, the technical RFCs that keep long-term code quality from being sacrificed for short-term velocity. When that foundation is solid, product teams move fast. When it is not, they slow to a crawl — and nobody can easily explain why.
I am also a member of the company’s AI Champions Community, spearheading the strategic transition to an AI-First engineering mindset with a focus on LLM integration and internal development agent tooling.
Why I also build my own software
Binaries Lab exists for two reasons.
The first is craft. Enterprise work is deeply satisfying, but it moves at enterprise pace. Building and shipping your own product — from concept to the App Store, handling everything from the Swift codebase to the Go backend to the IAP validation layer to the marketing page — compresses the full lifecycle into a span of weeks. It keeps skills sharp and perspective honest.
The second reason is proof. Transcriber, Migrate, and e.Vernetzt are not side projects - not to mention Gratehatch and ClockFeed. They are the output of applying the same architectural standards I use at scale — CLEAN architecture, SOLID principles, modular design, privacy-first data handling — to products I own end to end. Every decision has a consequence I live with directly. That accountability produces better software.
What this combination means in practice
iSAQB-certified software architecture gives you the vocabulary and frameworks to reason about systems. A decade of professional experience across iOS, macOS, Angular, Kotlin, Go, AWS, and full-stack development gives you the tools. What enterprise leadership teaches you — running recruiting cycles, conducting performance reviews, managing stakeholders at board level, acting as Security Champion through threat modeling and risk assessment — is that the hardest problems in software engineering are rarely purely technical.
The teams that ship great products understand both sides. They have engineers who can reason rigorously about architecture and communicate that reasoning clearly to people who care about business outcomes. They have leaders who set standards without becoming bottlenecks.
I specialize in being that bridge.
What this blog is
This is where I write about real engineering problems — the kind that surface when you are trying to maintain architectural integrity across a large codebase, integrate AI tooling into an existing development workflow, or build a production-grade iOS app that respects the people using it.
No padding. No trend-chasing. Engineering that earns its complexity.
If any of this resonates with a challenge your team is working through, I am always open to a conversation. You can reach me at marcelo@binarieslab.com - coffee is on me.