Senior Software Development Engineer in Test (SDTE)

We're looking for an exceptionally talented Senior SDET join our Side São Paulo Team, where you will design, build, and own our regression automation framework across iOS, Android and Web platforms. This is an exciting opportunity for someone to come in to a builder and leadership role, with the resources and stability of a mature engineering org, but the autonomy and blank-slate opportunity to architect our test automation infrastructure the right way. You'll set the technical direction for test automation, partner directly with mobile and web engineering leads, and raise the quality bar across the org.

• Architect and build a unified test automation framework from the ground up that supports iOS, Android, and Web clients, minimizing duplication of test logic across platforms where possible.
• Own regression test case generation strategy - analyze existing manual test suites, user flows and product requirements to identify and codify high-value regression scenarios, and define the process for keeping the suite current as the product evolves.
• Implement and maintain UI, API, and integration test suites using tools such as Maestro/XCUITest/Espresso (mobile) and Playwright/Cypress/Selenium (web).
• Design and integrate automated test suites into CI/CD pipelines (e.g., Buildkite, GitHub Actions) to enable fast, reliable feedback on every build.
• Establish test data management, environment provisioning, and reporting strategies to keep the automation suite stable and maintainable at scale.
• Own triage and reduction of test flakiness - set the standard for what "reliable" means for the automation suite and hold the line on it.
• Define and report on quality metrics (coverage, pass rate, flake rate, execution time) to engineering leadership, and use them to drive prioritization.
• Partner with product and engineering leads to translate feature specs and acceptance criteria into automated test case suites, influencing testability during design.
• Mentor and set technical direction for other engineers on testability best practices (e.g., writing testable code, dependency injection, accessible UI locators)
• Evaluate and evolve tooling and framework architecture to keep pace with mobile OS and web framework changes, making build-vs-buy calls as needed.