QC Assessment: Manual, DB, Automation

What they ask

For the software quality control engineer role the order is: HR interview first, then, if you pass, an assessment, then a technical interview. The assessment mixes three parts:

Manual testing task. You are given a feature description (for example a quiz flow where a student answers questions and sees a score) and asked to write test cases and list the bugs you would expect. What they check: coverage of the happy path, invalid inputs, boundaries (zero questions, the last question, a timeout), and clear expected results.

Database questions. Basic SQL against a small schema: select with conditions, a join, an aggregate, and a question on why a query returns duplicates.

Automation. Questions on how you would automate a web flow: which framework, how you structure page objects, how you make tests independent of each other, what you assert.

Find the error. A short code snippet (a loop or a condition with a subtle mistake) is shown and you are asked where the error is and what the fix would be. Reported as the part that catches people who only prepared theory.

What they look for

Test cases written like a tester who has shipped something: specific inputs, specific expected outputs, and bugs phrased so a developer can act on them. Reading code is part of the job here, so practise spotting off-by-one and wrong-condition bugs quickly.