Fintech · Argentina · PCI-constrained platform

• Cloud Architecture team reporting to VP of Infrastructure; establish order and standards for a fast‑growing platform.
• Onboard undocumented services: analyze code, reconstruct flows, create sequence diagrams and go/no‑go docs; register risks early.
• Publish readiness assessments and ADRs so product and business can see explicit trade‑offs.
• Design and implement deployment architecture and CI/CD for a new internal application, including environments and promotion strategy.
• Build repeatable integration and load/stress testing to surface performance boundaries and regressions.
• Call out risks: home‑grown proxies vs battle‑tested gateways; bespoke auth; limited staging; per‑environment image rebuilds; ad‑hoc TLS inside services; suboptimal traffic patterns around the cluster.
• Leverage regulatory constraints to argue for tokenization and reduced sensitive surface; promote QA gates, DB change promotion, and consistent environment practices.

Neobank · Technical lead for 7 DevOps engineers

• Took over problematic MX core banking implementation with outdated manifests/poor docs; reverse engineered behavior to run it reliably.
• Planned and executed EKS upgrades ahead of deprecations; produced runbooks, coordinated with product, and defined rollback strategies.
• Go‑to person for deep troubleshooting across infra, Kubernetes, and app layers for AR/MX cores and AML services.
• Raised team level through design/pipeline reviews, shared patterns, and prioritizing shared platform work.

Neobank · ~500 AWS accounts reach

• Joined central SRE/platform group; drove org‑wide observability patterns instead of product‑specific fixes.
• Prototyped OpenTelemetry adoption: routing strategies, metric design guidelines, and clear guidance on logs/metrics/traces/alerts.
• Delivered shared tooling for teams: chat integrations and automated multi‑account rollout of collectors.
• Produced reference docs/examples to guide teams, even when adoption was gradual.

IT Consulting · Multi‑client delivery

• Standardized CI/CD across clients to improve deployment speed and release consistency.
• Restructured infrastructure code for modularity and safer changes; simplified reviews and rollouts.
• Implemented golden‑signal alerting to improve operational visibility.
• Built a simple release orchestrator: chat/PR triggers, clear promotion steps, automatic rollback, and traceable logs.
• Versioned monitoring plans alongside infrastructure code.

Neobank · Infrastructure improvements

• Owned shared infrastructure for multiple products; joined a service squad to reduce technical debt and improve performance.
• Refactored networking stacks across hundreds of accounts to remove scaling pain and enable zero‑downtime changes.
• Cut environment provisioning from ~2 days to under 4 hours with automation.
• Maintained and tuned alerting with the operations team; improved signal quality.
• Standardized the organization’s infrastructure pipeline with reusable workflows.
• Clarified ownership in event‑driven systems by adopting a fan‑out pattern with team‑scoped channels and clear responsibility boundaries.
• Wrote documentation and ran internal sessions on Kubernetes, Infrastructure as Code, CI/CD, and cloud fundamentals.