Need some good .NET Design Pattern interview questions

128   96.7
Mar 25, 2010
Hello. I will be interviewing a few candidates for a senior architecture position that we have open at our company.
As an architect we expect them to be familiar with commonly used .NET Design Patterns.

Does anyone have some suggestions for some good interview questions?  I am not looking for questions like: explain the Factory Pattern, but more like scenarios in which certain patterns are typically used.

Look forward to some great suggestions!.
 1 comment
Check this link for more interview questions of "Design Patern" --- Akaas Developer  Aug 18, 2011

370   99.9
Mar 25, 2010
The best way to understand the depth of knowledge a candidate might have in design pattern is by asking these questions...

1. What are all design pattern you have used in your project?
2. Explain a scenario where you have applied <any pattern name told in previous answer>PATTERN_NAME? and why did you applied this pattern?
3. How long you have been using design patterns for the projects you had worked?


70   95.9
Apr 22, 2010
Some interview questions:

  • What are Design Patterns. Where do they originate?
  • Describe a scenario and what Pattern would you use?
  • Explain in detail any of the the original Gof Design Patterns
  • Singleton: How do ensure a Singleton is Threadsafe?

70   95.9
May 14, 2010
I prefer to ask the following questions:
  1. What is the difference between command, strategy and template method?
  2. When would you prefer builder to object factory?
  3. Can you describe when you need to use vositor with your own simple words?
  4. What is the difference between facade and mediator?

70   95.9
May 21, 2010

1.which patterns you used?
2.why that pattern you used?
3.what are the benefits of design patterns?
4.In which situation you will use say singleton pattern(any other patterns)?

60   95.3
Aug 18, 2011
Check this link for more interview questions of "Design Patern"

Akaas Developer

108   96.7
Aug 19, 2011
First you need to ask them if they know the basic OO principles: SOLID and GRASP.

The Design Patterns are nothing more than concrete implementations of these principles.

Then you delve into the Design Patterns specifics.

In real world very often you may not use a Design Pattern as it is in a book, what matters is to know and understand the principles and the ideas behind OO. Then you can do a good job when you architect and design an application.