Test strategy and UAT
End-to-end system journey test plans and UAT coordinated across global sites and time zones.
E2E · UAT · smoke · smart regressionSenior QA Specialist · Quality Enablement
Remote from Buenos Aires, working US hours
I catch the defects before your customers do.
Test strategy, UAT and incident workflows for fintech and contact center platforms, built so every team can own quality, not just QA.
A service waits at the end of the line to approve or reject. A product gets designed, adopted and improved.
So I join at kickoff and ask the hard questions early: what test environment we have, what success looks like, how we roll back. Then I leave behind runbooks and guides that Product and Engineering use on their own.
End-to-end system journey test plans and UAT coordinated across global sites and time zones.
E2E · UAT · smoke · smart regressionAcceptance criteria, test environments, rollback and kill-switch plans and controlled rollouts, settled before the first line of code.
risk-based testing · traceabilityRollback-first P1 handling, alerting built from what the retros find, and priority-based SLAs on every corrective action, with Jira reminders at 21 days, 7 days and the due date so engineers can plan them into sprints.
Rootly · Jira · SlackChecking support chatbots against the knowledge articles, holding scope guardrails, catching hallucinations and matching tone to the contact reason.
LLM validation · conversational QAIntake pipelines and scripts that replace manual work, from production-support triage to compliance requests.
Python · Claude Code · AsanaOne intake pipeline for every report from the field: triaged, fixed in-house or routed to Engineering with the context already gathered, and fed back to Product.
Asana · Jira · XrayI built the shift-left quality function from scratch, turned a run of daily untracked incidents into a repeatable workflow in Rootly, and automated compliance work that used to be done by hand.
Every critical initiative now starts with test environments, success criteria and a rollback plan on the table. Escaped bugs and rollbacks on those initiatives have dropped.
I owned test strategy and UAT for the migration to a new CRM and routing infrastructure, and helped define the routing source of truth: which team gets each call, chat, message or email.
Caribou Financial, via Hip Hip QA
Shift-left quality on critical initiatives, the incident workflow in Rootly, risk-based testing, and runbooks that let Product and Engineering own quality.
Airbnb, via Sutherland Global Services
First QA analyst in the program. Owned UAT for the CRM and routing migration and validated AI chatbots for customer support.
Airbnb and Apple
Product expert on complex cases and the link to Software Development. Knowing the systems from the inside is what brought me into QA.
I don’t just test software. I question how it works, challenge how it’s built, and look for ways to make it better.
I came into QA from the contact center floor. I know where the edge cases hide because I used to be the person who ran into them. When something breaks, reporting it is only the start. I want to understand the flow, find the root cause, see who it affects downstream, and make sure it doesn’t come back.
I connect Engineering, Product and Operations, and turn messy problems into something each team can act on. Lately I’ve been exploring AI-assisted development with Claude Code and test automation with Playwright.
I’m Venezuelan, based in Buenos Aires, and I work in English and Spanish every day.
I sang tenor in the Aragua State Symphonic Choir. Rehearsing a hundred voices into one taught me a lot about listening, timing and getting the details right.
I train Shotokan karate. Same lesson as good testing: repeat the fundamentals until they hold up under pressure.
Venezuelan by birth, married to a bogotana, and now in Buenos Aires for the tango, the theater and the people.
VenezuelaPanama, 1 yrColombia, 10 yrsBuenos Aires
A Frenchie and a Yorkie who review every release from my lap and approve nothing without treats.