interview questions for a test lead

Question

Maybe this question has been asked although I didn't find the answer.

I am going to attend an interview for a test lead. can you tell me the pattern of questions I will have to face other than the normal question that I was facing previously like What is Software testing? What is Bug life cycle? or Grilling me on my project experience.

Also I wnat to know when they are going to hire me for a test lead what would they want to see as an extra add ons?

Answer 1

Most likely it will be based on what you have done. When you are being interviewed the people interviewing you are attempting to see if you would be useful in assisting them with the projects that they currently need [which is hidden from your view].

Answer 2

Few of the questions which i can think of:

1. General questions about software development lifecycle.
2. Bit about your role in previous projects. Just to get some idea if you handled some developers/tester under you.
3. Bit about quality process used in testing especially in your process.
4. What were the tools you used in your projects and how comfortable are you.
5. If you got some testing certification to show, they might ask few about that.

Well this is not full list but will give you some idea.

Answer 3

Hi there.

I would imagine they would like to know how you approach the task of testing a piece of software. Examples might be, if you are given a website to test (an eBay clone maybe), then can you give an example of how you would plan to test the site:

• Test Cases
• Security Testing
• User Interface (correct spelling, controls interacting with each other correctly, etc)

If I was interviewing you then I'd like to know your methods for planning to test a piece of software.

Also I would assume they want you to know the different between unit testing, intergration testing, things like that.

Hope this is of some help.

Cheers. Jas.

Answer 4

Role and responsible for the current project. Planning and estimation. Team handling. Motivation to team member. How to allocate work and get it done from resorce. Different matrix, reporting. Objective setting to your resorces.

Answer 5

I always think knowing a little bit about programming helps. For example:

1) Knowing about form entry methods (e.g. using a Textbox to enter numeric values) and then being able to pick up on the edge cases for it's use (e.g. how does it handle decimal points, non-numeric values, extreme ranges, foreign cultures).

2) Knowing how to interpret a stack trace and being able to have a good guess at what sort of thing might be going wrong, that's always another useful skill.

I'd suggest if you have these abilities to highlight them.