👋 Hi, I’m Dariusz

Principal-level engineering leadership for the work that’s too important to get wrong.

I’m a Principal Software Engineer at Microsoft, working in the Azure Incubations team within the Azure Office of the CTO. I’m based in Redmond, WA, USA, and I’m a Microsoft Most Valuable Professional (MVP) Alumni.

Over 20+ years I’ve designed and delivered software that scales - from systems used by thousands of people to engagements serving customers among the global top 500. What I value most isn’t depth in any single layer, but the ability to see operations, platforms, and applications as one connected system - with security and identity treated as first-class concerns across the entire software lifecycle, not an afterthought.

In practice, that means helping teams make sharper architectural decisions, align faster, and carry less risk into high-stakes work.

🚀 What I’m working on

I currently focus on Radius - a CNCF Sandbox project. Radius is an open-source, cloud-native application platform that enables developers, and the operators who support them, to define, deploy, and collaborate on cloud-native applications across public clouds and private infrastructure.

🧰 Where I tend to add the most value

  • Architecture & modernization - shaping systems for scale, resilience, and long-term maintainability.
  • Distributed & cloud-native engineering - designing for portability, observability, and operability across environments.
  • Platform engineering & developer experience - paving golden paths so teams ship value instead of fighting their toolchain, CI/CD, or local setup.
  • Engineering fundamentals - quality practices, delivery discipline, design and code reviews, and standards that hold up under pressure.
  • Cross-team technical leadership - aligning people and decisions to move complex, high-stakes initiatives forward.

I’m often most useful where a critical initiative needs clear technical direction and steady execution - whether that’s untangling a hard architecture decision, lifting an engineering team’s operating rhythm, or quietly de-risking delivery before it becomes a problem.

🤝 Let’s connect

I enjoy comparing notes with leaders and engineers navigating tough technical decisions - architecture, platform strategy, developer productivity, and the realities of getting ambitious work shipped. If any of that resonates, I’m glad to talk.

The opinions expressed on this site are my own and do not necessarily reflect the views of my employer.