Sunday, November 30, 2008

Interview Questions

Software Testing Question:
1. Tell me about your experience on different level of testing .
There are many different ways and levels to test software based on project SDLC. It is always confusing. Tell same this what you have written in resume. But don't miss these
Integration Testing.
System Testing:
System testing one of the major level testing that cannot be bypass. During this level of testing, a QA tests system as a whole and verifies it works as expected. There are some specific types of testing that can be during during system level testing. some are :Recovery testing :( how well the system recovers the failure.) Security Testing : (capability of system to defend itself ), Load & Stress Testing (System is capable to handle maximum load and figure out the extreme load points), Performance Testing (determine the processing speed)Installation Testing (Installation & uninstallation is checked out in the target platform.)
Regression Testing
Acceptance Testing

2. What is Scenario based Testing ?
A scenario is a hypothetical story, used to help a person think through a complex problem or system. Scenarios are used to describe the functionality and behavior of a (software) system in a user-centered perspective. As scenarios form a kind of abstract level test cases for the system under development.Scenarios cover a number of steps/cases. In Test Director, after completing writing test cases, a tester can create test sets adding possible test case in it to make a test scenerio. Test suites and scenarios can be used in concert for complete system tests.How to create a scenerio; The scenario creation procedure:
Find all actors (roles played by persons/external systems) interacting with the system.
Find all (relevant system external) events.
Determine inputs, results and output of the system.
Determine system boundaries.
Create coarse overview scenarios (instance or type scenarios on business process or task level).
Prioritize scenarios according to importance, assure that the scenarios cover system functionality
Create a step-by-step description of events and actions for each scenario (task level).
Create an overview diagram and a dependency chart.
Have users review and comment on the scenarios and diagrams.
Extend scenarios by refining the scenario description, break down tasks to single working steps.
Model alternative flows of actions, specify exceptions and how to react to exceptions.
Factor out abstract scenarios (sequences of interactions appearing in more than one scenario).
Include non-functional (performance) requirements and qualities in scenarios.(if in scope)
Have users check and validate the scenarios (Formal reviews)
(This answer is enough to answer in interivew. To learn more about it go to
Here In this Kaner, has explained in detail.

3. When Does Testing Stop?
Testing might stop when Deadline has been met.
Testing comes to a halt when the budget has been exhausted.
Testing might stop when all test cases have been run or when a predetermined percentages have been passed
Testing might stop when a cettain coverage % is made.
Testing might stop when bug rate, severity/priority falls to comfortable zone.
................continue
HR TYPE
* What is your strength? (Always have answer before interview)Dependability, willingness to work hard, eagerness, fast-learner, technical skills, politeness, and promptness, expressed in concrete terms and good examples.* What are your career goals?> Short term - "I want to be the best in my current position, while learning additional responsibilities. This, in itself, will assure my commitment to the firm and raise me to the next level of responsibility and promotion. I see myself wanting to stay technical but learn the necessary skills to lead people and projects."Long term - "After proving my abilities, I see myself in a firm with the possibility of moving into a level of management that allows me to keep my skills sharp."
Why are you looking for another job?
Again, be positive. "I have to say that I really enjoyed my years at Corporation. There are a lot of good people over there. But I am looking for a more progresssive organization with greater opportunities for growth, and recognition. I am looking for a team to join where I can make real contributions and advance my career."

Tell me about yourself
This is a most common, important, and crucial for each and every interview. Because this is the first question you have to answer. So, i personally suggest to prepare a script for best performance and practice at least couple of times looking at mirror to make interview in your advantage.
First, provide a brief overview of your most relevant experience, focus on your recent project, most important project from job requirement point of view. Second, highlight education and personal qualities likes. focus on your personal interest on this particular job (Why? -matching skill set, love for technology. growth opportunity)
"I'm a QA engineer with expertise and skills in .NET, QTP, UNIX and, Apache, White box, black box, manual as well as automation. My most recent experience .................before that .....My industry experience encompasses the telecommunication health and, loan industries. My background also includes roles as QA engineer at ABA , QA Analyst (position title) and, ,....... I am (CSTE, ASTQB) certified and graduated from.. (Boston University).
Colleagues from past describe me as Team player, easy going person and detail oriented , and, supervisor describes me as a dependable, goal oriented. they remember me for positive attitude and energy.

“Do you prefer to work alone or as part of a team?”
Both. Describe two examples working as a team player and working individually and conclude with you have been been successful in both work situations.

What do you know about our company?
Before interview, spent some time to know the company. Find out as much as you can and make a note. So you can answer some other question related to it like Why do you want to work for us? Go online and Google about company. Also review other job posting from the same company. It will give you a lot idea about what type of person they are looking for QA position. For example, a job positing for a .NET developer from same company can give you some idea that they are using .NET framework and you can prepare about it in advance.
Also find out about products, size, income, reputation, image, skills, history and philosophy. If they ask about why do you like you can answer something ..always want to work for well reputed company like ...

No comments: