In detail

The roles, one by one

1. 2026now

   Banco Aliado

   QA Analyst, via Smart Consulting LA

   • Designing and running tests against the API services that expose the AS400 core banking functions, using Postman to check the response code, the payload structure, and its contents.
   • Cross-checking the data: comparing the JSON response against what actually landed in DB2 on AS400, with SQL verification queries.
   • Writing test cases for core modules, covering happy paths, negative paths, and edge cases.
   • Working in Scrum: joining the team ceremonies, refining user stories, and reporting and tracking issues inside the sprint.

2. 20222025

   Multibank (now BAC)

   QA Analyst, via Smart Business Solutions

   • Owning the test documentation, designing and running cases, reporting issues, and following them through to close.
   • Delivering the e-invoicing project for Core MB (AS400) and PREMIUM MB Seguros.
   • Rolling out improvements and fixes across the bank's applications (AS400, HiTech, ASICOM, and Tekins), and validating online banking modules.
   • Credit card testing on SYSCARD.
   • Running walkthrough and testing sessions with users and the departments involved, plus internal training on what we shipped.
   • Monitoring production after each release to make sure every deployment held.
   • Taking part in the project to migrate the bank's legacy servers.

3. 20172019

   Cable Onda (Tigo)Banesco

   QA Analyst, via Infosgroup

   • Gathering requirements with the business analyst to build the test matrices and validate every scenario in each project.
   • Running internal, user, and production testing, on applications and on physical devices.
   • Validating the Titan system (Cable Onda and Tigo).
   • Writing the test cases for the T24 core banking platform (Banesco), run by the team assigned to that project.
   • Supporting other teams, training branch staff, and onboarding new members of the team.

How I use AI in QA

AI is part of how I work, and a person checks the result every time.

• Designing

  test cases and matrices from user stories and functional docs, including the negative paths and edge cases that usually fall outside the first scope.

• Generating

  and reviewing the SQL validation queries against the core tables, to confirm that what the service answers is exactly what got written to the database.

• Comparing

  JSON payloads side by side (request, response, and database record) to catch missing fields, wrong data types, and transformations nobody documented.

• Writing

  technical docs, issue reports and test evidence, and building the validation assertions in Postman.

When the data can't leave the environment, I work with local models through Ollama.

Technical skills

• Testing and QA

  • Test matrices and cases
  • Functional testing
  • Integration
  • Regression
  • User acceptance
  • Happy, negative, and edge cases
  • Issue reporting and tracking
  • Production testing
  • Scrum

• API testing

  • Postman
  • Collections and environments
  • Variables and scripts
  • Response assertions
  • REST services
  • JSON ↔ database cross-checking

• Databases

  • SQL
  • Oracle SQL
  • DB2 on AS400
  • MySQL
  • PostgreSQL (Supabase)
  • Normalization 1NF–3NF
  • Stored functions
  • Triggers and procedures
  • JOINs and aggregation

• Core banking

  • AS400
  • HiTech
  • E-invoicing
  • Online banking
  • Credit cards
  • KYC and onboarding
  • GoAnywhere

• Development

  • React 18
  • TypeScript
  • Vite
  • Tailwind CSS
  • Supabase
  • Python
  • Flask
  • Java (fundamentals)
  • Git and GitHub
  • Vercel

• Artificial intelligence

  • Claude (Anthropic)
  • Ollama with Qwen3
  • Groq (Llama 3.1)
  • Google Gemini
  • Whisper
  • edge-tts
  • Prompt design
  • Graceful degradation

• Systems and networks

  • Linux desktop and server
  • Windows
  • PowerShell
  • DHCP
  • DNS
  • NTP
  • Active Directory

Education