The posting
About PackageX
PackageX builds the Physical Logistics Execution Platform for enterprise teams working across manufacturing sites, distribution centers, warehouses, retail locations, and other logistics-heavy environments.
Our platform combines Vision AI, workflow automation, mobile execution, and integrations to help companies digitize, execute, and verify physical operations at the point of work, creating trusted evidence of what actually happened.
Our operating model is simple: Execution. Verification. Evidence.
Why This Role Exists
Our software runs on warehouse floors, in mailrooms, and at receiving docks. When it breaks, it doesn't fail quietly in a dashboard somewhere. A worker is standing there with a scanner that won't scan, a label that won't read, and a line of packages piling up behind them.
We're hiring a Senior QA Automation Engineer to make sure that moment never arrives. You'll own quality across our mobile apps, web platform, SDKs, and Vision AI workflows, and you'll build automation as core infrastructure so coverage grows at the pace our releases demand.
You'll write and own JavaScript/TypeScript automation across mobile, web, API, and SDK layers, wire it all into CI/CD, and test by hand where automation falls short: new features, scanner quirks, camera capture in bad lighting, and networks that drop mid-shift. You'll join our engineering team, work alongside our existing QA function, and set the direction for how we test.
How This Role Works
This is one role with a few hats, and you'll switch between them often, sometimes in the same day.
Web and API automation. You're in the code: building Playwright-based web automation, and driving it through MCP servers to speed up how tests get written and maintained. You write API and integration tests in Vitest, grow regression coverage, triage failures, and keep suites reliable instead of flaky.
Mobile and SDK automation. You own our WebdriverIO and Appium mobile suite (Mocha, Allure reporting, Testmo integration) for the PackageX React Native app, and you build test coverage for our SDKs: integration harnesses, sample apps, contract tests, and version regression matrices.
Hands-on validation. Where automation can't see well, you pick up the device: exploratory testing of new features, scanning and camera capture, offline sync, rugged handhelds, and customer-specific workflows before pilots and go-lives.
If you only want to write scripts and never touch a device, or you've only ever executed manual test cases, this probably isn't your role. If you genuinely enjoy both, keep reading.
What You'll Do
- Design, build, and maintain automation frameworks for our React Native app (WebdriverIO and Appium with Mocha), web platform (Playwright), and APIs and SDKs (Vitest).
- Build and maintain Playwright web automation, including driving it through MCP servers, with guardrails that keep generated tests trustworthy.
- Own failure triage, flaky-test detection, and coverage analysis. When a suite gets noisy, you fix it rather than mute it.
- Build and maintain SDK test coverage: integration harnesses, sample apps, contract tests, and cross-version regression suites.
- Wire everything into CI/CD so regressions get caught on every pull request and build, with clear reporting and traceability in Allure, JUnit, and Testmo.
- Run exploratory and manual testing on real Android and iOS devices, including the rugged handhelds and scanners our customers actually use.
- Test Vision AI features the way the real world treats them: poor lighting, damaged labels, angled shots, and low-end devices.
- Validate offline behavior, data sync, and recovery when connectivity drops mid-workflow.
- Reproduce and isolate issues reported from customer sites, and hand engineers a clean repro with steps, logs, and screenshots. No “cannot reproduce” dead ends.
- Get into requirements and designs early, flag gaps and untestable logic, and push for testability in the codebase: test IDs, mocks, seeded data, and environment parity.
- Give evidence-based go or no-go input on every release, and own the numbers: defect leakage, coverage, flaky-test rate, and escaped bugs.
- Look after test data, test environments, and the device lab, and keep suites healthy and run times reasonable.
You Might Be a Fit If
Automation
- You've spent 5+ years in QA engineering, with test automation as the core of your job, not a side task.
- You've built or seriously extended an automation framework yourself, not just added cases to someone else's.
- You know Playwright deeply, including driving it through MCP servers.
- You've done mobile automation with WebdriverIO and Appium for React Native or native apps. That's our stack.
- You write JavaScript/TypeScript that other engineers trust.
- You've written API, integration, or component tests with Vitest or Jest. We use Vitest.
- You've wired test suites into CI/CD before (GitHub Actions, GitLab CI, Bitrise, or similar).
Manual and exploratory testing
- You test with discipline: test plans, edge cases, boundary conditions, and structured exploratory sessions.
- You've tested on physical Android and iOS devices across OS versions and hardware tiers.
- You're comfortable with API tools, logs, and basic SQL when a bug hides below the UI.
How you work
- You communicate clearly with engineers, product managers, and customer-facing teams.
- You'll say a release isn't ready when it isn't, and you'll have the evidence to back it up.
- You create structure in fast-moving, ambiguous environments instead of waiting for someone to hand it to you.
Nice to Have
None of these are required, but any of them will make us sit up:
- You've tested SDKs or other developer-facing products.
- You've worked with Allure reporting and test management tools (Testmo, TestRail, or similar).
- You've tested camera-driven features, barcode scanning, OCR, or ML/Vision AI outputs.
- You've done performance and load testing (k6, JMeter, Gatling, or similar).
- You've worked in logistics, supply chain, manufacturing, warehousing, or another operations-heavy space.
