About Smart Working

At Smart Working, we believe your job should not only look right on paper but also feel right every day. This isn’t just another remote opportunity - it’s about finding where you truly belong, no matter where you are. From day one, you’re welcomed into a genuine community that values your growth and well-being.

Our mission is simple: to break down geographic barriers and connect skilled professionals with outstanding global teams and products for full-time, long-term roles. We help you discover meaningful work with teams that invest in your success, where you’re empowered to grow personally and professionally.

Join one of the highest-rated workplaces on Glassdoor and experience what it means to thrive in a truly remote-first world.

About the Role

As a QA Automation Engineer, you will take end-to-end ownership of quality across a large, roughly 10-year, multi-repo digital health platform. You will build the automated test framework hands-on, define expected behaviour, and help improve reliability from an existing baseline where test coverage and pass rates need strengthening.

You will work with an engineering team of 4, collaborating to understand how the system should work from client, end-user and internal operations perspectives. The role is predominantly hands-on and independent, with shared responsibility for product quality.

The first phase will involve speaking with stakeholders, clarifying requirements, documenting expected behaviour, and building out automation that enables faster, safer releases.

Responsibilities

• 
  
• Own the quality process end to end and build the automated test framework hands-on
• 
  
• Understand how a large, roughly 10-year, multi-repo system works and how it should work from client, end-user and internal operations perspectives
• 
  
• Ask the right questions and document expected behaviour where inherited documentation is partly out of date
• 
  
• Author English-readable scenarios in Cucumber and Gherkin
• 
  
• Build automation in JavaScript and TypeScript
• 
  
• Drive the UI through a page object model
• 
  
• Add data-test-ids to React code where missing
• 
  
• Validate correct database state using SQL
• 
  
• Maintain the automated tests as new features arrive
• 
  
• Feed into requirements upfront as new features are planned
• 
  
• Flag compliance, regulatory and security implications
• 
  
• Run exploratory testing to identify where the product behaves incorrectly
• 
  
• Improve reliability and enable faster, safer releases through automation
• 
  
• Reproduce multi-step defects precisely and identify edge cases
• 
  
• Build a repeatable, documented QA process from an unreliable baseline
• 
  
• Work out how the system should behave across multiple user perspectives and how it might break
•