This role is about more than maintaining an automated test suite.

Youll help establish a quality engineering capability that gives engineers reliable evidence that the software they build behaves correctly while keeping responsibility for quality with the people designing and building the platform.

That means deciding where verification belongs, improving unreliable automation, strengthening API and integration coverage, making CI/CD feedback more useful, and building reusable testing infrastructure that can support the engineering team as the platform grows.

If you have strong automation experience but find yourself questioning whether another end-to-end test is really the right answer, this role may suit you.

Your work will include

- assessing existing automated verification and identifying gaps, duplication and ineffective coverage;
- deciding whether behaviour is best verified through unit, component, integration, API or end-to-end testing;
- improving shared automation infrastructure including fixtures, helpers, test data, authentication, isolation and environment dependencies;
- investigating and reducing flaky, slow or unreliable automated tests;
- improving CI/CD verification so failures provide useful engineering feedback;
- building automated verification for critical user journeys and material regression risks;
- reviewing and guiding developer-written tests without becoming responsible for writing every test; and
- identifying quality risks and helping Product and Engineering make informed decisions about them.

Why this role exists MenuWise is applying more than twenty years of foodservice industry learning to build the next generation of its platform.

Foodservice information is unusually difficult to work with. Supplier products change. Prices fluctuate. Nutrition information may be incomplete. Allergens and regulations vary between countries.



Terminology differs between regions.

Yet users still need the platform to produce accurate and defensible results.

Correctness is the product.

As the new platform is built, we want quality engineering to be part of normal engineering work rather than a downstream QA function. Developers remain responsible for the quality and appropriate verification of what they build.

Your role is to help make that model work.

What matters most

We’re interested in demonstrated quality engineering capability rather than a particular career path or number of years in a specific tool.

You should be able to demonstrate:

- strong automated-testing and quality-engineering fundamentals;
- good judgement about which verification level to use and why;
- experience designing and improving maintainable automated verification;
- strong API testing capability;
- experience integrating automated verification with CI/CD;
- an understanding of test isolation, deterministic execution and test-data design;
- the ability to diagnose flaky or unreliable tests rather than simply rerun them;
- enough software-engineering capability to work directly with frontend, backend and DevOps engineers; and
- the professional judgement to investigate complex problems and explain your conclusions clearly.

You should be comfortable writing automation code yourself, but this is not a role where success means personally writing every automated test.

Relevant technology

Playwright and TypeScript/JavaScript are particularly relevant to the current testing workplace.

Experience with Playwright is useful, but it is not a mandatory gate. Solid experience with Cypress, Selenium or another automation framework can transfer well if you understand the engineering principles behind reliable automated verification.

Formal testing qualifications such as ISTQB can provide supporting evidence, but practical engineering capability and judgement matter more.

📌 Senior Quality Engineer (Hyderabad)
🏢 Menucoster
📍 Hyderabad