Overview Stord is building the operating system for modern supply chain, a unified platform handling Order Management, Warehouse Management, Transportation, and Consumer Experience for leading brands across commerce. Our Commerce suite is the layer that sits closest to end customers: Shopify-embedded storefront components, checkout extensions, and a brand-facing portal that merchants use to configure and manage the experience. Quality here is not an abstraction. It is what a brand's customer sees when they check out. As a Senior Software Engineer in Test on Commerce, you own quality engineering for this product surface. You execute structured manual QA to hold the quality standard today, while systematically building the automation infrastructure that raises the ceiling over time. You will define what "tested" means across our Shopify apps, checkout extensions, and brand portal, build the tooling to enforce it, and operate as the quality authority on a team that treats reliability as a competitive advantage. If you are an engineer who takes quality personally, thrives in an environment where the practice is yours to shape, and wants to do technically serious work on a product surface that real customers depend on every day - this role was built for you. Why This Role • Establish the quality standard - you shape how quality engineering is practiced in Commerce; the decisions you make early become the foundation the team builds on • High-visibility product surface - our Shopify components and brand portal are what merchants and their customers interact with every day; quality here has a direct line to brand retention • Real technical scope - Shopify app testing spans checkout extensions, theme app blocks, storefront embeds, and a TypeScript-first service layer; this is not a forms-and-clicks automation job • AI-forward environment - Stord has made AI adoption a company-level mandate; you will work in an environment where AI-assisted development is the norm • Leadership investment - the Commerce team has the direction and the motivation to make quality infrastructure a first-class priority What You'll Do Manual QA and Quality Coverage Serve as the quality gate for Commerce feature releases. Write and execute test plans, run structured regression passes before releases, and document coverage gaps with enough fidelity that engineers can act on them immediately. Manual QA here is the bridge you build across while automation catches up, not a permanent operating mode. Test Automation Infrastructure Build an E2E test suite covering key customer journeys across the storefront and brand portal, wired into CI so regressions are caught on every PR. Make it easy for engineers to add coverage as a natural part of shipping. Shopify-Specific Quality Own the quality strategy for Stord's Shopify-embedded products: storefront app blocks, checkout extensions, onboarding flows, and the brand configuration interface. Define the right mix of automated and manual coverage for a surface that spans multiple merchant themes and checkout environments. Maintain a structured cross-theme QA playbook for compatibility scenarios that require human verification. Quality Strategy Define coverage matrices and quality gates tied to Commerce's product areas: Protect, Engage, Resolve, Unbox, and Renew. Surface quality metrics to the team so regressions and gaps are visible before they reach production. Participate in sprint planning and spec reviews to shift quality left. What We're Looking For Required Software Engineer in Test or quality engineering experience (4+ years) - You have worked as a dedicated SET or quality engineer in a production software environment, owning test strategy for a meaningful product surface rather than executing tests written by others. You have tested against real scale: multi-team codebases, high-release-cadence teams, or customer-facing surfaces where defects have measurable business impact. TypeScript (4+ years) - You write real production TypeScript across test frameworks and CI tooling, not just configuration files. You can navigate a codebase you did not write. E2E test automation - You have built and maintained Playwright or Cypress suites against real web applications in production CI. You know how to handle flakiness, authenticated flows, and rate-limited environments. Manual QA methodology - You write test plans, execute structured regression passes, and file bugs with enough detail that engineers do not need to ask follow-up questions. CI/CD integration - You have wired test suites into GitHub Actions or equivalent. You know when to block a PR versus report asynchronously. API testing - You test at the API layer directly, not only through a UI, and understand request/response contracts and authentication flows Directed AI-Assisted Development - You use AI coding tools as a productivity multiplier while maintaining independent technical judgment. This is a hard requirement. Required Soft Skills • Ownership and Accountability - You own the quality outcomes for your product area, not just the tasks assigned to you. If something ships with a regression, you care personally and act to prevent the next one. • Strong Communication - You translate "this is broken" into a bug report that gets fixed, and "here is what I am building" into a test strategy a PM and an engineer both understand. • Production Mindset - You think about failure modes, edge cases, and the real end-customer experience. A feature is not tested because the happy path passed. • Learning Agility - The Shopify platform evolves fast. You stay current, update your approach when the tooling changes, and do not get attached to how things worked six months ago. Strongly Preferred • Familiarity with Shopify app development: theme app extensions, checkout extensions, Shopify Functions, or App Bridge • Experience with visual regression tools (Percy, Chromatic, or equivalent) • Commerce or ecommerce domain knowledge • Experience establishing test infrastructure in a team without dedicated QA • Python proficiency Nice to Have • Exposure to Elixir codebases • Performance or load testing experience What Success Looks Like • 30 days: You have completed a structured walkthrough of the Commerce product surface, documented the critical user journeys, and executed your first regression pass. You have a prioritized automation roadmap and the team trusts your quality judgment. • 90 days: Automated E2E coverage is live for the highest-risk customer journeys in CI and the team has clear standards for what requires test coverage before shipping. Manual QA still happens but is shrinking as a percentage of total coverage. • 6 months: The Commerce team ships with quality confidence they can point to. Regressions are caught before production. New features have test coverage as a default. You are the quality authority on a team that ships with intent.