Oppulence
Oppulence
Back to company

About

Yoan is the co-founder responsible for Oppulence’s event-driven core—the mesh that keeps Canvas recoveries, Billing reconciliations, and Workspace decisions on the same timeline. Before Oppulence, he built and operated global-scale systems at Salesforce and Microsoft, shipping production fixes that cut Azure Storage outages by 75% and designing HDFS surfaces that power petabyte workloads. He brings that reliability-first mindset to CashOps, ensuring every recovered dollar and reconciled ledger entry has a verifiable trail.

Experience

Oppulence

Co-founder & Engineering Lead • 2024 - Present

Owns the CashOps control plane architecture—designing the multi-tenant event mesh, idempotent pipelines, and evidence store that keep Canvas, Billing, and Workspace data in lockstep. Leads distributed systems, security, and reliability initiatives so operators and auditors can trust the timeline.

Salesforce

Senior Software Engineer • Jul 2021 - Present

Senior Software Engineer on the APM & Distributed Tracing Team. Building observability infrastructure that helps teams understand and optimize their distributed systems. Led initiatives to improve system reliability and performance across Salesforce's cloud platform.

Microsoft

Software Engineer (SD2) | Azure Cloud & AI Group • Jul 2019 - Jun 2021

Built core services for Azure Storage, including the Paxos consensus engine that keeps global metadata consistent. Shipped fixes that cut outage incidents by 75% and contributed to Azure’s HDFS-compatible storage layer.

Education

Drexel University Master of Science, Computer Engineering & Applied Mathematics • Aug 2017 - May 2019

Drexel University Bachelor of Science, Computer Engineering • Dec 2013 - Apr 2017

Technical Expertise

  • Distributed Systems: Consensus algorithms, replication, consistency models
  • Cloud Infrastructure: Azure Storage, distributed file systems, cloud-native architecture
  • Observability: APM, distributed tracing, high-volume telemetry analysis
  • Backend Engineering: Event-driven services, resilient APIs, fault-tolerant automation
  • Languages & Technologies: Go, Python, Java, Kubernetes, Docker, PostgreSQL, Redis

Major Accomplishments

Reducing Azure Storage Outages by 75%

Within one month at Microsoft, Yoan discovered a critical issue with consensus management in the Paxos engine that was causing frequent outages. His deep understanding of the codebase allowed him to foresee and address the issue, reducing outages by 75%.

Building HDFS for Azure Storage

Part of the team that created Hadoop Distributed File System (HDFS) at Microsoft for all of Azure Storage, enabling massive-scale data storage and processing for Azure customers.

Engineering Philosophy

  • Deep Understanding Over Quick Fixes: Take time to understand systems deeply rather than applying surface-level solutions
  • Reliability First: Build systems that can handle failure gracefully
  • Scalability as Default: Design for scale from day one, don't retrofit later
  • Observable Systems: If you can't measure it, you can't improve it
  • Simple Solutions to Complex Problems: The best code is code you don't have to write

Open Source Contributions

Active contributor to open source projects. Maintains various repositories on GitHub related to distributed systems, observability, and infrastructure tooling.

Technical Focus Areas

  • Designing consensus and replication protocols for CashOps data
  • Building real-time ingestion and reconciliation pipelines that back Canvas and Billing
  • Creating developer-friendly APIs that expose the control plane without sacrificing guardrails
  • Implementing security, compliance, and evidence frameworks at the infrastructure level
  • Optimizing database performance, retention, and telemetry for high-volume financial events

Personal

Outside of Oppulence, Yoan enjoys contributing to open source projects, exploring new distributed systems papers, staying current with cloud infrastructure trends, and mentoring junior engineers. He believes that the best infrastructure is invisible—it just works, and you never have to think about it.

Back to team