Test Engineer - UI Regression - 6 Month Contract

About Fero: We’re revolutionising the supply chain and financial foundations of the $800bn global drinks industry by building a platform that will change the way that commerce is executed forever! We’ve just secured our Series A funding and are proud to be part of Notion Capital's portfolio. We’ve already influenced immense change in the UK markets and have personally already seen tremendous growth, with over £250 million of product transacted through the platform and increased annual sales by 1,000% since early 2023. To date we’re proud to say that we’ve deployed over £500m of funding in support of UK wine and spirits producers. As we look to expand our offering globally we’re looking for ambitious builders that want to change an industry and be part of the journey with us. We’re first to market and intend to stay ahead of the game!

The Role: As a Test Engineer you’ll work with our QA Lead to expand Fero’s Playwright/TypeScript regression suite so that the most important user flows are covered and run on every release. The role is hands‑on: learning how the platform works today, mapping and validating real user journeys end‑to‑end (including backend dependencies), and turning those flows into maintainable automated tests. It also needs someone comfortable with hands‑on development; making code changes when needed to improve testability and reliability, and working closely with engineers on fixes and refinements. You’ll help plan and prioritise the backlog in Linear, with the goal of growing coverage quickly and reducing production issues caused by unintended change.

What is this? The regression suite is traditionally the largest test suite covering all existing functionality, it is executed every time we make changes to provide protection against things accidentally changing or breaking unexpectedly. The aim of this suite is to prove that all user flows will be functional and will work together with the backend systems. It will focus on the UIs available on the Fero platform today.

Why is this important? Our system today has a lot of moving parts which are all tightly coupled, it’s not uncommon for a single change to have a cascading effect. These can sometimes have devastating effects on the system and because we don’t (as of today) have visibility of what each change will affect, it’s very difficult to catch those issues. What’s paramount to us is the user’s experience with the Fero platform and to protect it we need to prove that all user flows still work. This would be a huge undertaking in terms of manual effort, so it’s only manageable with test automation. Fixing issues found in Production is a massive time and cost sink and a constant source of frustration for Operations + Engineering.

What are we doing about this? From October last year, QAs started investigating and documenting the existing user flows on Fero. Quickly after realising the scope of the system, we started focusing on building test automation which turned into a mini‑project. Right now we have:

• The initial platform for test automation using Typescript and Playwright
• All the required connections, data, and pipelines to run tests with every release
• Initial set of tests ranging from full to partial coverage of some user flows

However, what we’re missing crucially is coverage. We only had time to cover roughly 13% of the overall crucial user flows.

What is our goal? Given the velocity of changes we’re introducing each sprint, and the scope of our goals for 2026 and beyond it’s a necessity to expand this quickly. Our goal on the crucial flows is 100% coverage.

What do we need? We need a Test Engineer to:

• Learn about, understand, and critically analyse existing functionality on the Fero platform
• Contribute code changes for test automation project
• Collaborate with our QA Lead to further plan ahead required work

While writing tests themselves is a considerable effort alone, it’s just as important for this person to be analytical, critical, and capable of communicating efficiently.

How will the project run? You will work with our QA lead to work through the backlog of tasks based on the priority. Our first priority is to cover the High priority user flows from this project. Our estimation is that it will take approximately 24 weeks. Based on that, we’d need the resource at least for 6 months to finish this task in addition to time spent onboarding, investigating the platform, and additional unplanned delays. We will be tracking overall progress in the overall tracker and all individual pieces of work will be in Linear.

Fero provides equal employment opportunities (EEO) to all employees and applicants for employment without regard to race, color, religion, sex, national origin, age, disability, genetics, sexual orientation, gender identity, or gender expression. We are committed to a diverse and inclusive workforce and welcome people from all backgrounds, experiences, perspectives, and abilities.