Skip to content
Clara

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

Bogota D.C. / DC / Colombia; Mexico City / CDMX / Mexico; Sao Paulo / SP / Brazil; Brasil ; Colombia; MexicoColombia
Engineering/ Builders
POSTED 5 OCTVERIFIED 55M AGO
Apply Ask
Open for
29d
since 5 Oct
H-1B · FY26
2
UK sponsor
Hiring · 30d
159
+3 net · open roles
TypeScriptJavaScriptReactNext.jsJavaDockerTesting

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 Fullstack/Backend Engineer focused on QA Automation — a software engineer who builds the infrastructure, frameworks, APIs, and tooling that make automated quality possible at Clara. This is an engineering craft 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.

The Role

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.

What You Own

  • Automation infrastructure — Design and implement shared frameworks and libraries for web/API automation (Playwright preferred), with stable selectors, modular architecture, and clear extension points for pods.
  • Tooling & services — 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).
  • Enablement for AI-assisted QA — Structure frameworks and contracts so agents and CLIs can generate and execute specs reliably (ticket → matrix → runnable tests → evidence).
  • CI/CD for quality — Implement and harden pipelines for smoke and regression suites; reduce flakiness; make failures diagnosable.
  • Engineering quality of test code — Treat automation as a first-class codebase: reviews, tests for helpers, versioning, documentation, and refactoring for maintainability.
  • Partnership — Work with QA engineers on adoption and with product engineers on testability (APIs, data-testid / ARIA, environments, test data hooks).

What Distinguishes This Role

  • Stronger software engineering depth than a traditional QA Engineer JD (services, APIs, data models, frontend for internal tools).
  • Focused on enabling automation at scale — not owning all manual exploratory testing for every pod.

Technical Skills

  • 4+ years of software development experience (backend and/or fullstack), with demonstrable automation or developer-tooling delivery.
  • Proficiency in TypeScript/JavaScript for Playwright (or equivalent E2E frameworks) and willingness to work in Clara's backend stack (Java / Spring Boot) where services or integrations require it.
  • Experience building and maintaining test automation frameworks (web and API); understanding of the test pyramid and when to prefer API vs UI coverage.
  • Backend fundamentals: REST APIs, relational databases, authentication basics, and clean service boundaries.
  • 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.
  • CI/CD experience (GitHub Actions or similar), Docker familiarity, and Git-based collaboration.
  • Ability to debug flaky tests, environment issues, and integration failures systematically.

Soft Skills

  • Builder mindset: you ship frameworks and tools that other engineers adopt.
  • Clear documentation and communication with QA and product engineering partners.
  • Comfortable with ambiguity and iterating from working prototypes to reliable platform pieces.
  • Collaborative code review habits; you raise the bar on test-code quality.
Source · ClaraFirst seen 2 NovOriginal ↗