Manual and Automation Testing Round

What they ask

The loop is compact: a thirty-minute HR interview for culture fit, a technical interview planned for an hour (for the test engineer role it ran closer to ninety minutes), then a fifteen-minute phone chat with the CTO. The technical part opens with your current role and responsibilities and then works through three areas. Questions in this area, for example:

Manual testing. Design test cases for a login form: which techniques do you apply (equivalence partitioning, boundary values, decision tables) and how many cases is enough? Severity vs priority with an example of high severity, low priority. What goes into a bug report so a developer can reproduce it first time.

Test automation. How you structure a UI automation project (page objects, fixtures, data separation). How you pick locators that survive UI changes. What makes a test flaky and how you fix it rather than retry it. Where automation runs in CI and what blocks a merge.

Agile. What testing looks like inside a two-week sprint: when test design happens, what "done" means for a story, how you handle a story that lands on the last day.

What they look for

A tester who thinks in risk and coverage, can talk about automation as code (not only a tool), and understands how QA fits in a hardware plus firmware plus app product where a release can mean a device in the field.