QA Test Automation Engineer

QA Test Automation Engineer

Only candidates local to the Chicagoland area will be considered

Hybrid:
In Office Every Thursday in Elmhurst, IL Required

Join Med Speed and help deliver health! We're a healthcare logistics company partnering with organizations nationwide to transport vital medical supplies and specimens. At Med Speed, teamwork, integrity, and growth drive everything we do. If you're passionate, driven, and ready to make a real impact, we want to hear from you. Today, we have a nationwide presence with locations across the U.S., yet we've never lost the entrepreneurial spirit and close-knit culture that defined us from day one.

Our people are at the heart of what we do and how we support our customers. We work as one team, we keep our promises, and we get better every day. These aren't just words; they shape how we support each other, grow together, and deliver real impact.

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 Browser Stack, 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 Browser Stack.
• 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.
• Evaluate tooling and evolve our practice:
  Track how testing is changing in the Flutter, mobile, and CI ecosystems. Run a proof of concept before adopting anything new, present the tradeoff and migration cost, and retire tools and tests that no longer earn their maintenance.
• Raise the team's testing standards:
  Review test code in pull requests, set conventions others follow, and help developers write and maintain their own tests instead of routing everything through QA.
• Collaboration:
  
  Work with developers, Dev Ops, and product managers to agree on test criteria and find edge cases before code ships.

• 5 years of professional experience in test automation covering both UI and API layers.
• Bachelor’s degree in Computer Science, Software Engineering, or a related field
• Experience defining a test strategy rather than executing someone else's: choosing the automation layer, setting the device and browser matrix, and defending those calls to engineering and product.
• At least one testing tool, framework, or process change you introduced or migrated, and a clear reason it was worth the cost.
• Hands…