There was a detailed technical question about a test strategy for a complex system built with a domain-specific language. When I answered in general terms, the interviewer kept pressing for more specifics and detailed examples. I finally realized that she didn't really understand the problem. I confronted her with "This is your job, isn't it? And you don't know how to do it!" She admitted I was right.
Thread lifecycle
phone : questions about your background etc. and a simple coding question in C# f2f: selenium coding question.
How would you test a cofee mug?
describe types of tests, linked list, web architecture
NDA Helpful Notes: Go though data structures, algorithms and collections. The technical interviews will mainly focus on testing strategies and coding skills. You might be asked to write up test cases for multiple services. Be sure to cover all negative cases, edge cases, happy path scenarios and dependencies. It will help if you practice enumerating test cases for websites, algorithms and functions. For coding questions, I think they are looking to see if you come up with the strategy. They might ask you to implement the solution in a different way. If you can give them a fair idea about your analysis on how to address the solution, I think that should be sufficient. Be prepared for database queries. Joins and normalization in specific. Apart from that, you can expect process related questions related to bug tracking, metrics, CI/CD, release management etc. Automation and REST services questions were also part of the mix (If you work with technologies like Selenium, they will ask you specific questions related to it).
NDA Helpful Notes: Go though data structures, algorithms and collections. The technical interviews will mainly focus on testing strategies and coding skills. You might be asked to write up test cases for multiple services. Be sure to cover all negative cases, edge cases, happy path scenarios and dependencies. It will help if you practice enumerating test cases for websites, algorithms and functions. For coding questions, I think they are looking to see if you come up with the strategy. They might ask you to implement the solution in a different way. If you can give them a fair idea about your analysis on how to address the solution, I think that should be sufficient. Be prepared for database queries. Joins and normalization in specific. Apart from that, you can expect process related questions related to bug tracking, metrics, CI/CD, release management etc. Automation and REST services questions were also part of the mix (If you work with technologies like Selenium, they will ask you specific questions related to it).
NDA Helpful Notes: Go though data structures, algorithms and collections. The technical interviews will mainly focus on testing strategies and coding skills. You might be asked to write up test cases for multiple services. Be sure to cover all negative cases, edge cases, happy path scenarios and dependencies. It will help if you practice enumerating test cases for websites, algorithms and functions. For coding questions, I think they are looking to see if you come up with the strategy. They might ask you to implement the solution in a different way. If you can give them a fair idea about your analysis on how to address the solution, I think that should be sufficient. Be prepared for database queries. Joins and normalization in specific. Apart from that, you can expect process related questions related to bug tracking, metrics, CI/CD, release management etc. Automation and REST services questions were also part of the mix (If you work with technologies like Selenium, they will ask you specific questions related to it).
Data Structures and Algorithms. Design Q (1) Past experience.
Asking about linting in javascript to write cypress automation
Viewing 811 - 820 interview questions