Most questions were either scenario based or experience based. For example, "Tell me about a time you managed stakeholders with conflicting priorities." or "The feature you're working on is broken and the launch needs to be delayed, how would you escalate this to leadership?"
How do you handle when your project timeline/deadline has been halved?
What do you do when you want to join a program that is new?
What would you do if you have some nasty customers you have to work with?
1. Which is better - Agile or Waterfall? 2. How will you test XYZ product from a user's perspective? 3. How will you deal with disagreement between Engineering team and Testing team? 4. How will you communicate your disagreement with the Engineering team to upper management? 5. Will you be involved in product design? 6. How will you deal with a critical issue a week before launch? 7. What is your risk management strategy? 8. How do you prioritize bugs? 9. Why Apple?
Tell me about your current position.
How would you deal with very fact paced and technically strong team?
How do you deal with conflicts
Common questions you can expect. Fairly reasonable.
(Describes a big technical challenge) "what can you do to solve this?" Not as open ended as it sounds, the described problem is real
Viewing 91 - 100 interview questions