Senior QA Engineer, automation and manual, with product enablement

ABOUT THE ROLE

We are a climate technology team operating a multi-tenant SaaS platform used by carbon registries and project developers. Correctness matters here in a way it does not in most products: the records our customers create are written to a public ledger and cannot be edited afterward.

You would own quality end to end. That means the automated test estate, hands-on manual and exploratory testing, and being the first technical responder when a customer reports something that does not look right.

It also means something we think is underrated: because you will know each feature better than anyone once you have tested it, you will be the one who documents it, demonstrates it, and walks customers through it. We do not think that work belongs to someone who has never exercised the feature.

RESPONSIBILITIES

• Own the automated test estate: unit, API and end-to-end suites, and the CI pipelines that run them.
• Manual and exploratory testing, including release verification. Not everything worth catching can be automated, and we are not interested in a team that pretends otherwise.
• Regression strategy for a platform with a large surface area and frequent releases.
• Bug triage: reproduce, isolate, write the report a developer can act on without a second conversation.
• Feature documentation. Partner with the developer who built it, understand it properly, and write the documentation for it. You will have tested it, so you already know where users will get stuck.
• Demos of completed features, internally and to customers and partners.
• Front-line technical response and customer onboarding: reproduce what the customer reports, walk new customers through the platform, and answer the technical questions that come in.
• Test data strategy for a domain where realistic data is scarce and production data is sensitive.
• Performance and load testing, if that interests you. The foundation exists.

REQUIREMENTS

• Strong in both automation and manual testing. This is the core requirement. Candidates who are excellent at one and absent in the other are not a fit for this role.
• 4+ years in QA, with ownership of a test suite rather than only executing someone else's.
• API testing depth: REST contracts, auth, error paths, and what to assert beyond a 200.
• End-to-end and UI automation with a modern framework. We use Playwright; Cypress or Selenium experience transfers.
• Unit and integration testing in a JavaScript or TypeScript codebase.
• CI/CD literacy: able to read a pipeline, work out why a job fails, and fix it. You will own the workflows that run your tests.
• Formal test design: boundary values, equivalence partitioning, decision tables. We want deliberate coverage, not intuition.
• Able to judge whether a test actually proves anything. A green suite that asserts nothing is worse than no suite, and we will ask you about this directly.
• Able to write clearly for a non-engineer. Feature documentation is part of this role, not an afterthought handed to someone else.
• Comfortable presenting. You will demo features to customers and partners, and onboard new users onto the platform.
• Comfortable talking to customers. You will sometimes be the first person a frustrated user reaches.
• Willing to sit with a developer and ask questions until you genuinely understand a feature, rather than testing it from the ticket description.
• English at B2 or above for written technical discussion and calls.

NICE TO HAVE

• Load and performance testing with k6, JMeter or similar
  Test data generation, including synthetic or AI-assisted approaches
  Kubernetes literacy, enough to read logs and understand where a service runs
  MongoDB
  Exposure to blockchain, carbon markets or regulated reporting. Optional, we will teach the domain.

WHAT YOU WOULD WORK ON FIRST

• Being specific, because it is more useful than a list of adjectives:
• Taking ownership of an existing test estate and deciding what to keep, repair or retire.
• Bringing a substantial body of generated test coverage under review and judging what genuinely earns its place.
• Establishing regression coverage for a part of the platform that is currently verified by hand.
• Building a test data approach for a domain where realistic data is genuinely hard to obtain.
• Documenting and demonstrating the features shipping in the next releases.
• If you have spent years asking for the authority to fix a test pipeline properly, this role is that authority.