3×
Integration delivery velocity
Transfero · 2023 →
Designed a Microkernel architecture for external-integration adapters and built a Visual Studio template that scaffolds the full library structure. Tripled delivery speed for new adapters and became the team standard.
Trade-off accepted
Accepted more complexity in the core - an extensible kernel costs more to maintain - in exchange for linear adapter delivery. Worth it because integrations were the team's growth vector.
C# / .NET 7MicrokernelClean ArchitectureVisual Studio
Py → .NET
Critical migration from Python to .NET 7
Transfero · 2023 →
Rewrote a critical integration from Python to .NET 7. Performance gains, higher reliability, and alignment with the company's core stack - fewer incidents on critical financial operations.
Trade-off accepted
Accepted the cost of rewriting battle-tested code in exchange for consolidating the stack in a single language - smaller oncall surface, one CI/CD pipeline, unified observability.
Python.NET 7PerformanceReliability
↓ cost
Centralized pricing service
Transfero · 2023 →
Built a centralized service that aggregates external pricing data and serves every internal application. Eliminated redundant calls, standardized the source of truth, and cut company-wide operational cost at scale.
Trade-off accepted
Accepted a single point of failure in exchange for consistency and cost. Covered with aggressive Redis caching, clear SLOs, and graceful degradation when the upstream goes down.
C# / .NETRedisAzureDistributed Cache
SDK
SDK + template that accelerated the payments team
Transfero / BTG Pactual · 2022 →
Built an SDK and a Visual Studio template that scaffold the base project for payment adapters. Other teams now focus only on the integration itself - time per adapter fell from weeks to days, with quality consistent by design.
Trade-off accepted
SDKs demand semantic versioning discipline and an API surface that ages well. I took on that responsibility to remove cognitive load from consumer teams - they no longer need to know the plumbing.
C# / .NETSDK designVisual StudioDX
7 days
Regulatory delivery under pressure
Financial system · delivered in one week
A project with tight regulatory requirements delivered end-to-end in seven days. Prevented significant operational losses and kept the company compliant with the regulator.
Trade-off accepted
Knowingly accepted tech debt - minimal coverage, deferred refactor - in exchange for a non-negotiable deadline. Follow-up plan written on delivery day; debt cleared in the two sprints that followed.
High-pressure deliveryComplianceExecution