I am 7 years of experience in J2EE and have to go for interview tomorrow and there they are going to give 1 hour assignment of java project like library management/ATM or something like that.
I am not getting confidence to do that assignment it can be programmatic or UML based high level design, but I think it will be UML based/sudo code development because in 1 hour we can't do much.
I feel, They will be interested to know our approach for assignment like design pattern etc so they can see our potential of candidate.
but I am not getting confidence to do very well... but I really need this job..as its a very good company.. and cant afford to miss it.
My Question from folks here is what design pattern one can use to show better idea of designing.. such application.. (provided its not web based).. or have some experience in such interview.. ?
or any inputs people would like to give so I can perform better.. with good confidence.
As time is short I need urgent suggestions and will appreciate ideas in critical timings.
You know what you know. Any last-minute cramming, or ideas that you get from people on the net, is unlikely to be of any help. After all, you don't want to misrepresent yourself and get hired for a job you are not qualified for, do you?
Also you want to do what you are are comfortable with so when they ask follow up questions, you sound confident. If I tell you to use a singleton and they ask why, what do you say? That makes things worth than not using it at all.
Here's my $0.02: Don't even try to find "a design pattern to use to show better idea of designing" -- that approach to using design patterns will lead you nowhere that's good for you. First of all, you should be familiar with a few design patterns and be able to recognize the various situations in which they are applicable. More importantly, you have to be able to recognize when a particular design pattern should not be used. The key word here is recognize. This means that you start with the problem, with no preconceived idea of what pattern you should use. Then you recognize similarities between the current problem and the class of problems to which a particular design pattern can be applied. You should never start with a design pattern already in mind.
I am trying to understand your critics for my last moment question.
I do know some design pattern being 7 yrs of exp in j2ee, but the concern is the approach with which I should proceed ?
Also can you share some major design pattern I should use and that help me to RECOGNIZE in generic situation of solving ATM/library management system.
I respect everybody views on 11th hour... but still looking for ideas that can help me... and increase my confidence... and everything is possible.. So i m still optimistic with some good positive constructive reply...
Here's the only other idea that I can offer to help you: Don't try to make it appear that you know more than what you actually know. If you don't know something or if you're stumped, be honest enough to say so. There is really nothing wrong with admitting that there are limitations to your knowledge and experience. Nothing ruins an interview more for me than someone who is clearly trying to just talk their way through a question. Any good interviewer will instantly recognize when someone doesn't know anything about something but is still trying to bluff their way through. If you try to bluff your way through, that will most likely be the end of your chances at getting hired. As Jeanne says, be confident that you know what you know and just do your best to answer honestly to the best of your ability.