QA Automation

Clara is the leading platform in Latin America for companies to execute and manage every payment operation. More than 50,000 leading and fast-growing businesses run on our corporate cards, bill pay, financing and B2B payments, and in 2025 the Financial Times named Clara the region’s fastest-growing company. We’re passionate about helping every company we work with become more effective—and, through that, raising the region’s competitiveness. We’re ~400 people, backed by Notable Capital, Coatue, Kaszek, monashees, DST Global, ICONIQ, General Catalyst and Goldman Sachs, among others.

We are looking for a QA Automation Lead to own Clara's test automation strategy, frameworks, and quality standards. This is a technical leadership role for someone who sets the automation bar across web, API, and mobile surfaces — not a classic people-manager seat. You partner with Engineering Directors, pod leads, and Product to make automation the default path to release confidence, while mentoring QA and engineering teammates who build and adopt the frameworks.

The Role

You are the technical authority for QA automation at Clara. You own the strategy, architecture, and reliability of the automation platform (Playwright-based web/API frameworks, CI integration, reporting, and enablement) so pods can ship with confidence without QA becoming a bottleneck.

What You Own

• Automation strategy — Define and evolve the automation roadmap (test pyramid, risk-based prioritization, shift-left practices) aligned with product delivery across surfaces such as payments, onboarding, cards, and accounts.
• Framework ownership — Own architecture decisions for shared automation frameworks (e.g. Playwright for web/API; Appium/Wdio where mobile automation applies). Set coding standards, review patterns, and maintainability rules for test code.
• Quality standards — Establish org-wide definitions for release-blocking coverage, flakiness thresholds, and what must be automated vs. explored manually. Protect trust in automated results.
• Stakeholder partnership — Align with Engineering Directors, Pod Leads, Product, and Platform/Infra on capacity trade-offs, environment/test-data dependencies, and adoption plans so pods own execution while QA owns the capability.
• Mentoring & enablement — Coach QA engineers and developers on automation craft, code review, and adoption of shared tooling. Run technical hiring signal for automation-related roles.
• CI/CD & observability — Drive integration of automation into GitHub Actions (smoke on PR, regression on deploy), reporting (e.g. Allure/Qase or internal test-manager), and actionable failure triage.