Software Developer in test

Primary: Headless functional test automation — fast, stable, and CI-friendly

Secondary: Appium / device UI automation is an important layer, but not the entire role

Spec-driven: Candidates will read and review specifications and test plans, not just work from tickets labeled "write tests"

Manual coverage: 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 efforts

Role focus Primary: Headless functional test automation — fast, stable, and CI-friendly

Secondary: Appium / device UI automation is an important layer, but not the entire role

Spec-driven: Candidates will read and review specifications and test plans, not just work from tickets labeled "write tests"

Manual coverage: 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 efforts

How We Work We 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 Do Write and maintain C# automated tests for survey workflows (download, collect readings, GPS, export, settings)

Review developer test PRs and send incomplete coverage back to engineering

Triage failing CI / stage runs: product bug vs flake vs environment — then fix the ones that are ours

Decide what to automate at which layer: unit / headless functional / device UI (Appium) / manual

Grow Appium coverage where the headless suite cannot see the real screen

Partner with Product, Arch, and Dev so new work is testable before it ships

This 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 line

Real experience writing automated tests as code (xUnit, NUnit, or MSTest)

Page Object Model (or equivalent) — maintainable tests, not one giant script

Can debug a failing test and explain flake vs product bug

Git + pull-request review

Clear written communication (Jira / PR comments)

Strongly Preferred Mobile UI automation: Appium, Espresso

.NET MAUI

GitHub Actions or Azure DevOps pipelines

Async / timing issues (tests that race the app)

Nice to have GPS, Bluetooth, offline, or hardware-adjacent testing

Field / inspection / GIS / industrial software

Test design (what not to automate)

#J-18808-Ljbffr