I can't give away actual questions, but on some occasions, the answer lies in thinking outside the box and going beyond the pass/fail framework of most test cases in defining success. Sometimes whether the product or feature works or not cannot be boiled down to a simple binary.
Nothing unexpected. Make use of "cracking the coding interview" book.
Why I wanted the testing role and not the developer role
Nothing unexpected. Study the usual stuff, code on your work, and be confident and you can do it.
Had to sign an NDA so won't break that here. Overall there wasn't anything too challenging, I've come across more difficult questions in interviews. The more difficult ones were open ended questions about how to test a google service.
Design elevator management system. Design parking lot problem.
How would you test XYZ?
Hacker Rank backspace string compare problem
Java programming, Selenium basics API
Testing pyramid, working with developers, how to give and receive feedback, previous projects
Viewing 891 - 900 interview questions