QA Test Automation Engineer

Only candidates local to the Chicagoland area will be considered

Hybrid: In Office Every Thursday in Elmhurst, IL Required

The QA Test Automation Engineer will define and build our automated test coverage across web, mobile, and backend systems.

You'll own UI automation for our Flutter Web and mobile apps, run those suites on real browsers and physical devices through BrowserStack, and confirm that data moves correctly between frontend and backend.

This role is responsible for defining and owning the testing strategy from the ground up.

The ideal candidate will determine what should be automated, at which testing layer, and across which devices and platforms.

This position will build and maintain automated tests, integrate them into CI pipelines, and ensure the test suite remains reliable, effective, and actionable as the product evolves.

• Own the test strategy: Decide what gets covered at each layer (unit, widget, integration, end to end, manual exploratory), which browsers and devices are worth paying for, and where the coverage gaps carry real release risk. Document those decisions and revisit them as the product changes.
• UI and end-to-end automation: Build and maintain automated UI test suites for Flutter Web and native mobile using the Flutter testing stack and current automation frameworks.
• Cross-browser and multi-device runs: Execute regression suites on real iOS and Android devices and on Chrome, Safari, Edge, and Firefox through cloud device farms such as BrowserStack.
• API and integration testing: Validate data flows, request and response contracts, and system behavior across .NET backend APIs and connected Salesforce services.
• CI/CD integration: Run tests in parallel inside CI pipelines, define quality gates that block bad builds, and shorten the feedback loop before production releases.
• Flake triage: Track intermittent failures to their actual cause, whether that's front-end rendering, device-specific behavior, timing, or an unstable API response, and fix them rather than retrying around them.
• Measure and report quality: Define the metrics that show whether testing is working (escaped defects, flake rate, suite runtime, coverage of critical user paths) and report them to engineering and product on a regular cadence.