Interview Strategy for Design Pattern Questions

When you get a design pattern question, structure your answer in five parts to show complete understanding. Start by identifying the problem the pattern solves — don't jump straight to the definition. If they ask about Factory, begin with 'I'd use Factory when I need to create objects but don't know the concrete type until runtime.' That shows problem-first thinking. Next, categorize it: 'Factory is a Creational pattern because it deals with object instantiation.' This proves you understand pattern taxonomy, not just isolated definitions. Then explain how it works using concrete terms. For Factory, you'd say 'you define a factory interface with a create method, implement it for each variant, and the client calls the factory without knowing which concrete class gets created.' Fourth, connect it to real Java or Spring code. Mention something like 'Spring's bean factories work this way, or you might use it to create different payment processors based on config.' Real examples prove you've seen patterns in production, not just textbooks. Finally, and this is crucial, say when the pattern would be overkill. Add something like 'but if I only have one implementation and no concrete plan to add more, a simple constructor call is better than introducing a factory.' This demonstrates judgment. A common mistake freshers make is giving only the textbook definition without context or trade-offs. That sounds like memorization. Another mistake is not connecting to real code — saying 'I'd use Observer' without mentioning event listeners or Spring's ApplicationEvent makes it theoretical. The strongest signal you can give in a design pattern question is knowing when not to use the pattern. That shows you're thinking like an engineer, not a student. In a cart service, you might say: 'I'd use Strategy for discount calculations when I have multiple customer types. It's Behavioral because it varies algorithms. I'd define a DiscountStrategy interface with implementations for standard and premium. Spring would inject the right one based on customer type. But if I only have standard customers and no plans to add premium, a simple calculateDiscount method is better.' That's a complete, balanced answer.