QA stuff to think about and maybe discuss in an interview :

* Design
* Requirements (including acceptance criteria)
* Testing requirement compliance (functional + non-functional)
* Edge cases, non 'happy path' cases
* Bug reports
* Testing bug fixes, regression tests
* Version control
* Documentation/terminology/context

Testing is a huge subject - consider unit testing and end-2-end testing.

Consider that QA should have veto control over any release of any product - from a patch for a game to an airliner. How does QA fit into the organisational structure - will you have the authority to guarantee quality?

Nb - none of this is software specific.