Hi Shawn and Dave. Thanks for your wonderful contribution to this post. I am agree with your views but at the same time I do agree with Charan's statement also. I know that clearing an interview totally depends upon your real time experience and coding skills but as you know that each and every company has its own working environment and technique. They have several projects and so different ways of handling them. May be I've worked on data driven and keyword driven frameworks but not aware of the exact mode of the questions. Further, sometimes it happens to the candidates that they are not able to answer the questions even if they know it very well and have actually worked on them. It happens because they are not ready or aware of the types of questions which is asked in the interviews. So, I think its always better to prepare a lot before you attend an interview. Medium could be anything. It can be your or others real time experience. That doesn't matter. I would like to add here something. Most of the people I met and asked from QTP background, there were many common questions which they were asked. Like, VB Script Functions, Check Points, Recovery Scenarios, FSO, Reporting etc. So it was just a polite request to all the members of this group to share their real time interview experience here. So that we can see what are the common questions which an interviewer can ask.
On Aug 6, 2:28 am, Shawn <[email protected]> wrote: > I also agree and see way too many of these types of requests. You > either know the product or you don't. It is one thing to ask support > on how to solve certain technical questions, but asking specifically > for "answers" to interview questions is just wrong. > > When I hire people they have to go through 3 interview phases: > 1. They have to take a written test > 1a. I then review the answers > 2. Then I conduct a verbal in-person interview and discuss the test as > part of it > 3. Finally I end it with a hands-on test. This is the best because > some people who have "book knowledge" and just "study" for the > interview can get by the first two phases but people that don't have > real world experience can't fake the hands-on test. If you have real > experience then its easy. People get nervous and it can be a little > stressful, but the ones that can demonstrate that they know what they > are doing not only get the job but I normally cut them off on the > hands-on part as I don't need them to finish the script because I can > tell they know what they are doing. > > If you really know what you are doing then don't "cheat" with > questions and answers, but simply practice automating things and > continue to learn. Make things up to automate and then develop a QTP > script to automate it. That's what employers want, is people that > truly know what they are doing and can be productive very quickly. > --- > Shawn LoPortohttp://www.asi-test.com -- You received this message because you are subscribed to the Google "QTP - HP Quick Test Professional - Automated Software Testing" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/MercuryQTP?hl=en
