Software Engineer In Test Interview Questions

Software Engineer In Test Interview Questions

Software engineers in test are IT professionals who focus on building tools for software testing. They also sometimes perform the tests and assist in developing the product being tested. In a software engineer in test interview, prepare to answer advanced questions about the software testing and development process.

Top Software Engineer in Test Interview Questions & How To Answer

Question 1

Question #1: Explain the difference between priority and severity.

How to answer
How to answer: You might recognize this as a technical question assessing your knowledge and skills. A successful answer would define the terms concisely and correctly. Explain that priority refers to the time sensitivity of a bug, while severity refers to how destructive the bug is.
Question 2

Question #2: What is ad-hoc testing?

How to answer
How to answer: Ad-hoc testing is a regular task you might perform. Explain that ad-hoc testing is performed informally to attempt to find bugs without test cases. To stand out, consider explaining why this step is valuable, or share an anecdote about a time you found a significant defect through ad-hoc testing and were able to repair it.
Question 3

Question #3: Explain the difference between SDET (software development engineering in test) and manual software testing.

How to answer
How to answer: While these roles may seem similar, it is important that you understand the unique differences in responsibilities and processes. Demonstrate a thorough understanding of your role and how it operates within the team. Explain that software development engineers in test focus on building automated tests, while manual software testers do not.

36,220 software engineer in test interview questions shared by candidates

1. How do you do (based on your work experience): - White box testing? - Functional testing? - Regression testing? 2. We have 'Employee' table with 'Name', 'DepartmentName', 'Salary' columns. Write a query to retrieve a max salary from each (different) department.
avatar

Software Development Test Engineer

Interviewed at A9.com

3.7
Apr 6, 2015

1. How do you do (based on your work experience): - White box testing? - Functional testing? - Regression testing? 2. We have 'Employee' table with 'Name', 'DepartmentName', 'Salary' columns. Write a query to retrieve a max salary from each (different) department.

5 places you have. You have 50 got eating a food. A d 50 for fair. You are looking for a specific dish and no one knows how will you reach there. Every place you visit then you have to pay 15 rs. How will you get success.
avatar

Senior Test Engineer

Interviewed at Delhi Public School Ghaziabad Society

3.1
Feb 20, 2020

5 places you have. You have 50 got eating a food. A d 50 for fair. You are looking for a specific dish and no one knows how will you reach there. Every place you visit then you have to pay 15 rs. How will you get success.

The most difficult question actually came from me. It seemed innocent enough. As all interviewers do, I was asked if I had any questions. My question was, what event brought them to Mountain States. Why did they come to work there and why did they stay there? Trained in Appreciative Inquiry techniques, created by Case Western University, I know the value of storytelling in understanding what motivates people. It is a valuable tool in creating consensus. In asking this question, I asked them to tell the story (beginning, middle, and end) about how they came to work there and why they stay there. When I asked the question, the department head seemed uncomfortable with both the question and the approach. I liked what I heard, thought we could work together, and said so. But, I knew the question was not well received by this person, who I assume was the main decisionmaker in this process. I knew I would not be hired. Just because an interviewer asks if you have any questions, that does not mean they are open to your questions. You never know unless you ask. And if they are not comfortable answering or prove evasive, then it seems to reveal a potential future weakness in the relationship. It forces the interviewer to show personality on a basic level. If the individual does not like that, it is a good thing to know before accepting an offer. I wish them well with their new hire. All things work out for a reason. I trust this will too.
avatar

Testing, Testing, and More Testing

Interviewed at Mountain States Employers Council

3.8
Jun 5, 2013

The most difficult question actually came from me. It seemed innocent enough. As all interviewers do, I was asked if I had any questions. My question was, what event brought them to Mountain States. Why did they come to work there and why did they stay there? Trained in Appreciative Inquiry techniques, created by Case Western University, I know the value of storytelling in understanding what motivates people. It is a valuable tool in creating consensus. In asking this question, I asked them to tell the story (beginning, middle, and end) about how they came to work there and why they stay there. When I asked the question, the department head seemed uncomfortable with both the question and the approach. I liked what I heard, thought we could work together, and said so. But, I knew the question was not well received by this person, who I assume was the main decisionmaker in this process. I knew I would not be hired. Just because an interviewer asks if you have any questions, that does not mean they are open to your questions. You never know unless you ask. And if they are not comfortable answering or prove evasive, then it seems to reveal a potential future weakness in the relationship. It forces the interviewer to show personality on a basic level. If the individual does not like that, it is a good thing to know before accepting an offer. I wish them well with their new hire. All things work out for a reason. I trust this will too.

Viewing 831 - 840 interview questions

Glassdoor has 36,220 interview questions and reports from Software engineer in test interviews. Prepare for your interview. Get hired. Love your job.