Design concepts.

Note :  - There is no straight forward answers to any design questions. There can be n number of solutions of any problem, discuss the trade-offs of different variations, your interviewer may twist the requirement to see how you are approaching to solve it. There is no right and wrong answer to any design question, it just depends, how well you are able to present your design and how good you are in tackling different alternatives. Each alternative design have their own plus and minuses, you just have to sense your interviewer's interest, what he is looking. So talk to him/her. Design interviews has to be mutually executed, you cannot derive it alone. Covering all aspect would be difficult, just come up with one or two main working flows and demonstrate in your design. Please go through how to handle software design questions , if you have not read it, before you read further. Problem statement -  Design a call center. List out the classes and data structure you will us

I have came cross many design questions in my technical interviews, and to be honest I failed a lot. So I have put efforts to learn how to deal with hifi design questions. Which every small to big companies ask in their design interview round, if you are applying for SDE-II or higher positions. When interviewer ask you design question,  you don't have to think about any architecture or UMLs, or HLD, or LLD, or any object oriented design. Just p ick pen and paper and start modeling requirement. Any design will come latter, at the first you have to understand problem statement, as deep as you can. Before you go ahead and jump into design jargon, convey your understanding on asked problem with interviewer. You may have understood it correct or may not!  Share all assumptions with interviewer, you have to make sure you both are in same page, before you start thinking solution, otherwise you will conflict with interviewer at latter stage of interview, if you both have different a