TN18 - Sr. QA Engineer – Test Framework & Automation
- Hiring from
- Latin America
- Work type
- Remote
- Posted
625,001 remote jobs, straight from company career pages
100% free · New jobs every minute
Show job descriptionHide job description
Senior QA Engineer, Test Framework & Automation
Remote (LATAM) · Full-time or contractor · 9 AM–6 PM ART
About our client
Our client is a US-based company that helps banks automate critical operations such as reconciliation, customer onboarding and payments. They deliver through small, focused pods, each embedded in a client engagement and working alongside AI agents. In banking, accuracy is non-negotiable, so quality is a core part of what they offer.
About the role
Every pod has its own QA Engineer. You will sit one level above them, owning what they all rely on: the test framework they adapt for each bank, the shared eval suite that checks the agent setup, and the coverage policy every team follows. None of these exist yet. You will start by extracting them from the first engagement, not by designing them on paper. This is a product-building role, and the product is a reusable library of tests.
What you will do
Inside the pod
- Set the acceptance criteria every change must meet and review how each implementation plan shows it meets them.
- Write test cases from signed functional requirements before any code exists, and validate them with the bank’s business users.
- For every bug, commit a failing test first and lock it so the agent cannot alter it.
- Query client data directly (warehouse, ledger, core reports) to confirm results are actually correct, not just that the code runs.
- Spot what automation misses: interface logic and business meaning that no test covers.
Across pods
- Design and build a banking test framework: a case library organized by automation type (reconciliation, onboarding, payments), covering happy paths, edge cases and the failures banks worry about most, like duplicate transactions, out-of-order files, cutoff handling, rounding errors and outdated reference data.
- Make it adaptable by design. Cases are parameterized by a bank profile (formats, calendars, cutoffs, policies), so onboarding a new bank means providing a profile and sample files, not rewriting tests.
- Build the test harness: runners for three CI tiers (local hooks, PR gate, full release suite), coverage gates, Playwright UI flows, API workflow suites with mock services, and realistic test data that is anonymized or tokenized.
- Own the shared eval suite that regression-tests the agent configuration. Every incident in any pod becomes a new eval or test case.
- Define the coverage policy and back it with data from the first instrumented engagement.
Communication
- Write bug reports anyone can understand at a glance, and keep test plans, framework docs and status reports up to date.
- Explain quality risks to clients in business terms, and say plainly when something is not ready.
- As the team grows, hire, mentor and review the work of new pod QA engineers.
What the client is looking for
- 8+ years in quality engineering, including building a test framework or platform that other teams adopted, not just used.
- Strong test architecture: parameterized design, fixture and data management, and deterministic suites at scale (hundreds of tests, no flakiness).
- Hands-on experience with Playwright or similar, API workflow testing, and a clear view of CI cost trade-offs (why the full suite can’t run on every PR).
- Advanced SQL, including complex joins across relational and non-relational sources.
- Knowledge of banking flows (payments, reconciliation, onboarding), or a proven ability to learn a regulated domain fast.
- A product mindset: versioning, documentation and upgrade paths for a framework with internal users.
- Comfort working directly with clients, in writing and in meetings.
- Advanced English (required).
- Experience with AWS or Azure.
Nice to have
- Experience evaluating AI systems or agents, or working with AI-assisted development.
- Previous ownership of a platform or developer experience.
How you work
- You own quality end to end, from the first design session to hand-off, and the framework from v1 to adoption.
- You are hands-on: you define the strategy and write the tests.
- You communicate clearly with both technical and business audiences.
- You are comfortable with ambiguity and pace, since client processes are rarely well documented.
- You care about details: in banking, a one-cent difference is a finding.
What success looks like in six months
- The framework exists, is versioned and documented, and was built from the first engagement.
- A second engagement starts with most of its tests coming from the library, measured by the share of reusable modules and time to first green build.
- The coverage debate is settled with data-backed targets, enforced by CI.
- Every incident from any pod has become an eval, and the eval suite blocks merges across all teams.
What the client offers
- 100% remote, paid in USD, working for a US company.
- 10 vacation days + 7 PTO days (prorated to start date).
- A company laptop.
- A growing team where your work shapes how quality is done.