Primary: Headless functional test automation — fast, stable, and CI-friendlySecondary: Appium / device UI automation is an important layer, but not the entire roleSpec-driven: Candidates will read and review specifications and test plans, not just work from tickets labeled "write tests"Manualcoverage: A significant portion of our legacy coverage is still manual — candidates must also be comfortable executing and validating manual test cases as part of feature testing and regression effortsRole focusPrimary: Headless functional test automation — fast, stable, and CI-friendlySecondary: Appium / device UI automation is an important layer, but not the entire roleSpec-driven: Candidates will read and review specifications and test plans, not just work from tickets labeled "write tests"Manualcoverage: A significant portion of our legacy coverage is still manual — candidates must also be comfortable executing and validating manual test cases as part of feature testing and regression effortsHow We WorkWe use AI-assisted tooling (Cursor, AI code/test review, agent-driven test design) as part of daily workflow. We are adopting Loop Engineering — a structured process where docs, coding, QA, and DevOps run as coordinated loops with clear ownership, human gates, and agent participation.



Candidates should be open to working alongside AI tools and contributing to a maturing engineering process.What They Will DoWrite and maintain C# automated tests for survey workflows (download, collect readings, GPS, export, settings)Review developer test PRs and send incomplete coverage back to engineeringTriage failing CI / stage runs: product bug vs flake vs environment — then fix the ones that are oursDecide what to automate at which layer: unit / headless functional / device UI (Appium) / manualGrow Appium coverage where the headless suite cannot see the real screenPartner with Product, Arch, and Dev so new work is testable before it shipsThis is not a record-and-playback role, and not a full-time manual tester who automates on the side.Must-haves (do not send without these)Strong C# and comfort running tests from Visual Studio / command lineReal experience writing automated tests as code (xUnit, NUnit, or MSTest)Page Object Model (or equivalent) — maintainable tests, not one giant scriptCan debug a failing test and explain flake vs product bugGit + pull-request reviewClear written communication (Jira / PR comments)Strongly PreferredMobile UI automation: Appium, Espresso.NET MAUIGitHub Actions or Azure DevOps pipelinesAsync / timing issues (tests that race the app)Nice to haveGPS, Bluetooth, offline, or hardware-adjacent testingField / inspection / GIS / industrial softwareTest design (what not to automate)#J-18808-Ljbffr

📌 Software Developer In Test (Colombia)
🏢 Braintrust
📍 Colombia