Clara

<p><strong>Clara is the leading spend management platform in Latin America.</strong> More than 40,000 businesses run on our corporate cards, bill pay, financing and B2B payments, and in 2025 the Financial Times named Clara the fastest-growing company in Latin America. We're ~400 people, backed by Kaszek, monashees, Coatue, DST Global, ICONIQ, General Catalyst and Goldman Sachs, among others.</p>
<p>We are looking for a <strong>Fullstack/Backend Engineer focused on QA Automation</strong> — a software engineer who builds the infrastructure, frameworks, APIs, and tooling that make automated quality possible at Clara. This is an <strong>engineering craft</strong> role (closer to SDET / SET / platform engineer than classic manual QA): you write production-grade code that enables pods and QA to generate, run, and trust automated tests.</p>
<h2><strong>The Role</strong></h2>
<p>You build and maintain the systems behind Clara's QA platform: Playwright-based frameworks, services and APIs that support test execution and reporting, CI wiring, and internal tools (e.g. test case / run persistence on Clara's React/Next stack). You collaborate with the QA Automation Lead, Pod Leads, and product engineers so automation is reusable, agent-ready, and owned as real software — not a pile of brittle scripts.</p>
<h3><strong>What You Own</strong></h3>
<ul>
<li><strong>Automation infrastructure</strong> — Design and implement shared frameworks and libraries for web/API automation (Playwright preferred), with stable selectors, modular architecture, and clear extension points for pods.</li>
<li><strong>Tooling &amp; services</strong> — Build backend APIs and fullstack components that store test cases, record run results, expose reports, and integrate with delivery workflows (e.g. Linear webhooks, Slack notifications, GitHub Actions).</li>
<li><strong>Enablement for AI-assisted QA</strong> — Structure frameworks and contracts so agents and CLIs can generate and execute specs reliably (ticket matrix runnable tests evidence).</li>
<li><strong>CI/CD for quality</strong> — Implement and harden pipelines for smoke and regression suites; reduce flakiness; make failures diagnosable.</li>
<li><strong>Engineering quality of test code</strong> — Treat automation as a first-class codebase: reviews, tests for helpers, versioning, documentation, and refactoring for maintainability.</li>
<li><strong>Partnership</strong> — Work with QA engineers on adoption and with product engineers on testability (APIs, data-testid / ARIA, environments, test data hooks).</li>
</ul>
<h3><strong>What Distinguishes This Role</strong></h3>
<ul>
<li>Stronger software engineering depth than a traditional QA Engineer JD (services, APIs, data models, frontend for internal tools).</li>
<li>Focused on <strong>enabling</strong> automation at scale — not owning all manual exploratory testing for every pod.</li>
</ul>
<h2><strong>Technical Skills</strong></h2>
<ul>
<li>4+ years of software development experience (backend and/or fullstack), with demonstrable automation or developer-tooling delivery.</li>
<li>Proficiency in <strong>TypeScript/JavaScript</strong> for Playwright (or equivalent E2E frameworks) and willingness to work in Clara's backend stack (<strong>Java / Spring Boot</strong>) where services or integrations require it.</li>
<li>Experience building and maintaining <strong>test automation frameworks</strong> (web and API); understanding of the test pyramid and when to prefer API vs UI coverage.</li>
<li>Backend fundamentals: REST APIs, relational databases, authentication basics, and clean service boundaries.</li>
<li>Fullstack comfort for internal tools: React / Next.js (or similar) for dashboards and test-management UIs is a strong fit with Clara's internal scaffold direction.</li>
<li>CI/CD experience (GitHub Actions or similar), Docker familiarity, and Git-based collaboration.</li>
<li>Ability to debug flaky tests, environment issues, and integration failures systematically.</li>
</ul>
<h2><strong>Soft Skills</strong></h2>
<ul>
<li>Builder mindset: you ship frameworks and tools that other engineers adopt.</li>
<li>Clear documentation and communication with QA and product engineering partners.</li>
<li>Comfortable with ambiguity and iterating from working prototypes to reliable platform pieces.</li>
<li>Collaborative code review habits; you raise the bar on test-code quality.</li>
<li>Good English (written and verbal); Spanish is a plus.</li>
</ul>
<h2><strong>Nice-to-Have</strong></h2>
<ul>
<li>Prior SDET / SET / Test Infrastructure Engineer experience.</li>
<li>Mobile automation (Appium) or BrowserStack.</li>
<li>Workflow orchestration (n8n), Linear/GitHub API integrations, or AI/agent tooling for test generation.</li>
<li>AWS and observability basics for running automation reliably in shared environments.</li>
<li>Fintech / payments domain exposure.</li>
<li>Experience replacing external test-management tools with internal systems.</li>
</ul>
<h2><strong>Why Clara</strong></h2>
<ul>
<li><strong>A high talent-density team</strong> driven to make an impact in Latin America — low ego, high ownership.</li>
<li>Competitive salary and stock options (ESOP) from day one.</li>
<li>An annual learning budget and accelerated development paths.</li>
<li>English is our working language, with Spanish and Portuguese every day.</li>
</ul>
<h2><strong>How we work</strong></h2>
<ul>
<li><strong>Clarity</strong> — Open and direct communication: we say what we mean and give context where it matters.</li>
<li><strong>Simplicity</strong> — If it can be simpler, it should be.</li>
<li><strong>Ownership</strong> — We own everything we do, end to end. When something needs to happen, we don't wait.</li>
<li><strong>Pride</strong> — We hold ourselves to a high standard, and it shows in what we deliver.</li>
<li><strong>ABC (Always Be Changing)</strong> — We adapt fast, embrace change, and keep learning.</li>
<li><strong>Inclusivity</strong> — Diverse ideas, stories and perspectives build a better Clara.</li>
</ul>
<h2><strong>Hybrid at Clara</strong></h2>
<p>Claridians split their time between the office, customers and home. We don't set a minimum number of office days for most roles, but we expect you to spend time there naturally, and most days during your ramp-up or when your leader asks.</p>
<p>If you meet the must-haves, apply — the nice-to-haves are a bonus, not a requirement.</p>


Software Engineer in Test (SDET) (Ingeniero de Software en Pruebas) - Remote First New

Software Engineer in Test (SDET) (Ingeniero de Software en Pruebas) - Remote First New

This job is no longer available

Talents

Recruiters

About