For more details check out http://www.virtualclarity.com
So here we go, got a call yesterday from my agent saying that that company X wants me on board. Don’t know how I feel about it yet, but these guys seem to invest a lot in the new tech and the first time since 2002 I’m going to be working on a truly greenfield project. Damn, the vacation lasted only one week.
In this very first blog post – various aspect of the interview questions and answers are discussed. Some people like the subject for their helpful hints and thought provoking subject, and others dislike these posts because they feel it is nothing more than cheating. I’d like to discuss the pros and cons of a Question and Answer format here.
- What is RDBMS?
- What are the Properties of the Relational Tables?
- What is Normalization?
- What is De-normalization?
- How is ACID property related to Database?
- What are the Different Normalization Forms?
- Support for strongly and loosely typed messages
- Support for bindings
- Support for the latest web services
- Integrated security model
- Boundaries are explicit
- Services are autonomous
- Communication via contract
As a developer writing source code generally means to create lines of code and then continuously find bugs and fix them in an iterative process of refining the software.
Looking for a job is not that different: you learn from mistakes and try to cope with them!
Here are some suggestions I have learned recently after having been refused by a big US company and after having accepted an offer from a UK company, which I ran away from after a terrible first day at work.
- Never use sales technique guidelines such as “How to handle two different offers” or “What to say when the interviewer asks you if you have any questions“.
It is still ok to know these techniques, but the truth is that your hiring manager is probably a PhD guy with several years of experience, with a QI above the average and surely…
View original post 643 more words