AWS architecture review
Security, costs, availability, readiness for traffic peaks with stress testing, and technical debt, reviewed together with the team.
OutcomeA written assessment with prioritized risks and a target architecture.
Consulting
A few companies at a time, with real dedication.
I dedicate up to twelve hours a week to consulting. I read the code, talk with the team and put decisions in writing.
Legacy system migration
The system nobody wants to touch, whatever its technology, keeps running while the new service grows alongside it, with current technology on AWS and Kubernetes. Traffic moves over in stages, every step can be rolled back and the old system is switched off once nobody uses it.
OutcomeA staged plan, the first new services in production with CI/CD, and operations running throughout the change.
Payment systems and e-commerce
Banking integrations, CVU collections, interoperable QR, commission and tax engines, payment reconciliation, capacity for high-demand dates and technical SEO.
OutcomeAuditable money flows and a platform ready for the next peak.
Technical leadership
Support for Tech Leads and CTOs: standards, reviews, technical roadmap, training and adoption of AI agents with control over what reaches production.
OutcomeA team that makes better decisions and doesn't depend on a single person.
- 1A conversation about the problem and the business context.
- 2A written proposal with scope, expected outcomes and fees.
- 3Work in short cycles, with visible progress every week.
I also consider cloud architecture and technical leadership positions, full-time or part-time, on teams that build demanding products.
Frequently asked questions
How do you migrate a legacy system without stopping operations?
The old system keeps running while the new service grows alongside it, on AWS and Kubernetes. Traffic moves over in stages, every step can be rolled back and the old system is switched off once nobody uses it.
How much time do you dedicate to each engagement?
Up to twelve hours a week, with a few companies at a time.
How does an engagement start?
With a conversation about the problem and the business context. Then a written proposal with scope, expected outcomes and fees, and work in short cycles with visible progress every week.
Do you work remotely?
Yes. I work from Argentina, remotely, with teams in any country.
Do you also consider full-time positions?
Yes, cloud architecture and technical leadership positions, full-time or part-time.