TN18 - Sr. QA Engineer – Test Framework & Automation
EngineeringQa Engineer
1 views0 saves0 applied
Quick Summary
Requirements Summary
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 (reconcilia
Technical Tools
EngineeringQa Engineer
About the Role
~2 min readInside 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.
- 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
~1 min read- Experience evaluating AI systems or agents, or working with AI-assisted development.
- Previous ownership of a platform or developer experience.
- 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.
- 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.
- 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.
Location & Eligibility
Where is the job
Argentina
On-site within the country
Who can apply
AR
About this job
- Who can apply
- Argentina
- Posted
- Today
Listing Details
- First seen
- November 18, 2026
- Last seen
- November 18, 2026
Posting Health
- Days active
- 0
- Repost count
- 0
- Trust Level
- 58%
- Scored at
- November 18, 2026
Signal breakdown
freshnesssource trustcontent trustemployer trust
External application
4 other jobs at
View all →Similar Qa Engineer jobs
View all →Test Automation Engineer (m/f/d) Daily Banking Frontend
Product Test Engineer - Staff
F - Full Time
Remote
Associate SDET (Software Development Engineer in Test)
$90,000–$105,000
Full-timeRemote
Java Test Automation Engineer - VOIS
Remote
Senior QA Engineer
Full-timeRemote
Remote
Senior QA Engineer
Full-timeRemote
Browse Similar Jobs
Devops Engineer6.2kEngineering Manager4.4kFullstack Developer4kMechanical Engineer3.4kElectrical Engineer3.3kSoftware Architect3.1kProject Engineer2.9kSecurity2.8kDesign Engineer2.8kSecurity Engineer2.6kQuality Engineer2.4kBackend Developer2.2kProcess Engineer2kFrontend Developer1.6kApplication Engineer1.4kProduct Engineer1.3kAutomation Engineer1.1kEmbedded Engineer1.1kCivil Engineer1kMobile Developer1k
Newsletter
Stay ahead of the market
Get the latest job openings, salary trends, and hiring insights delivered to your inbox every week.
A
B
C
D
No spam. Unsubscribe at any time.
