Software Manual Testing Interview Questions for Experienced Professionals

Topmost frequently asked scenario-based Manual Testing interview questions for the experienced professionals with details answers:

I recently had this unique experience of coaching a QA (10 years experience) to attend a client Software Testing interview with a leading Entertainment company in Los Angeles. The site to be tested was a simple customer-facing website (sort of like an online TV channel) that had both Web and Mobile components.

Software Manual Testing Interview Questions

A consulting company was projecting profiles to this client for an onsite tester + coordinator position but none of them was making it through the testing interview process. So they decided to collect the QA interview questions from the previous attendees and they gave me a questionnaire.

They wanted me to give the answers to the next candidate and coach that person to be successful in the testing QA interview.

Manual Testing interview questions for experienced

When I got the list of questions, I was surprised and ‘not-surprised’ at the same time. Surprised- because the questions were really basic and a 10 year experienced QA should have been able to answer them easily.  Not so surprised because QA is the field of IT that has most weeds in my opinion – but let’s not get into it.

After being done with the exercise, I thought it would be nice to share this experience with the STH readers. For beginners, this will be good live exposure. For others, it will be a friendly reminder of how important fundamentals are no matter how experienced we are.

Recommended Reading => 101+ Software Testing Interview Questions and Answers.

Here goes…..

Manual Testing Interview Questions for Experienced

9 Most Common QA Software Testing Interview Questions for Beginners as well as Experienced Candidates:

#Q 1) What is the Process for Creating a Test Script?


Step 1: is to get a thorough understanding of the AUT:

  • This could be by reading the requirement documents thoroughly.
  • In the absence of docs, we could try to understand any point of reference that we have – a previous version of the application or wire-frames or screenshots

Step 2: After understanding the requirements, we make a list of what are the areas in this application that will have to be tested. In other words, we identify the test requirements. The focus in this step is to identify “What” to test. The outcome of this step is a list of Test Scenarios.

Step 3: Once we have the test scenarios, we concentrate next on “How” to test them.  This phase involves writing detailed steps about how to test a particular feature, what data to enter (Test Data) and what is the expected result.

Once these 3 steps are done, we are ready for testing.

#Q 2) What are the fields in a Bug Report?

Answer: Following important fields should be included in a good Bug Report:

  1. A unique ID
  2. Defect Description: a short describing what the bug is.
  3. Steps to Reproduce: details about how to arrive at the error, exact test data, the time at which defect was found(if applicable) environment: any information that will help re-encounter the issue
  4. Module/section of the application (if applicable)
  5. Severity
  6. Screenshot
  7. Responsible QA: in case of any follow-up questions regarding this issue

#Q 3) How to test a customer-facing software?

Answer: With any application that we test, we are trying to see if a certain set of requirements are met by the application or not. But when it comes to a user-facing site, apart from concentrating on functionality, we also have to look into a few usability features, maybe performance and security aspects also to a certain extent.

The first level of testing is: Does the site satisfy its functional requirements.

For Example, if it is a loan management site, we need to look at – are the new customer able to apply for a loan, are the existing customer able to access their loan info, is the interest % applied to the loan amount correct, etc.

The next level of testing is: how easy is it to use the site, do the options make a logical sense and meet the expectations of the user or not.

For Example, if the user has to be pass 3-4 screens to submit the basic information they are going to be annoyed, so such issues have to be addressed.

Another example, after entering username and password, the user might click on the tab- which means the control should go to “Sign in” button, instead if it’s going to cancel, the user is going to be really annoyed and the experience of using the site is going to be compromised. Such issues have to be caught.

Performance Testing to the complete extent might not be in scope but simple situations like, how long does the search results take to be displayed and how much time does it take for the system to retrieve a customer info at the peak hour – these are some example of the kind of things we would want to keep an eye on.

Security – for sites where there is a secure login to access the site, the minimum functionality around it has to be tested. For Example, if I leave the site idle for more than 10 minutes, is it auto logging out or not. Something as basic as that should be focused on.

#Q 4) How to overcome the challenge of not having input documentation for testing?

Answer: IF the detailed standard documentation like BRD and FSD are unavailable, the tester will have to depend on some point of reference.

  • Screenshots
  • A previous version of the application
  • Wireframes, etc

Another factor that helps immensely, is to talk to the developers or the business analysts (when available) to get a confirmation on our understanding or clarifications in case of doubts.

When none of these situations works, we can just conceptualize the application based on our previous IT application experience and create the basic set of test scripts. When the testing phase comes up, we can set up a portion of test cycle time and do some test case management (make the already created scripts perfect) so we have the doc for the next phases.

#Q 5) How to get maximum productivity from an offshore team?

Answer: The key is to make sure that all the testers know about all the modules and that there is no knowledge concentration in one place. Involving everyone in test script peer reviews, defect meetings, and KT sessions are going to ensure that everyone is aware of the application to the best extent possible.

Also, by encouraging the concept of teamwork we can have the team members collaborate, help and aid each other for better productivity.

Regular follow up meetings also help the process very much.

#Q 6) What are the Roles and Responsibilities of an onsite coordinator? Does he/she test too?

Answer: The onsite coordinator is a point of contact for the offshore team and to the client for any information regarding the testing engagement.

This job includes:

  • KT from and to offshore and clients
  • Getting the environment to test all ready
  • Sanity testing, smoke testing
  • Testing – the key functionality.
  • Bug review – found by the offshore team
  • Bug assigning to the respective dev
  • Presenting metrics
  • Providing sign off

Yes, even an onsite coordinator has to test.

#Q 7) Inconsistent bugs- Why onsite can find it, but offshore can’t and vice versa – How to handle this situation?

Answer: Every bug has to be noted and analyzed – whether it is encountered at onsite or offshore, whether repeatable or not. A real value-add to a tester’s job is when we involve ourselves in the Root Cause Analysis process for a bug rather than simply reporting it.

Some of the ways we can handle this situation are:

  • All the onsite and offshore team members should follow a guideline that screenshots had to be taken for every error that we encounter – repeatable or not.
  • If there are logs, system files or anything like that, that might help us find any evidence of the issue- we should try to find it.
  • Despite all these steps, if we still can’t tell why and when the problem occurs- we should report it to the developer all the same – with as much information as we can.

#Q 8) Video/audio related testing – What does this include?

Answer: How to test an application having video or audio?

Here are the important points to consider:

  • Access levels (restricted or not – password controlled)
  • Different kinds of environments
  • Browser compatibility
  • Screen resolutions
  • Internet connection speeds
  • The specific options on a video – like play, stop, mute, etc.
  • Video by size
  • Response to the videos – comments (limitations on the comment length and number of comments it can take)
  • Video responses to the videos
  • Interface with social networking sites – Interoperability
  • Buffering speed
  • Embedding the video

#Q 9) Mobile Application Testing – What does it include briefly?

Answer: Mobile App Testing Important Test Scenarios:

  • Check if the app works well with multiple carriers and multiple devices.
  • Usability of the features on a mobile screen.
  • Testing it on different mobile platforms – like Android and iOS.
  • Installations, uninstalling, launching the app with network and without a network, testing functionality.
  • Network connections –WiFi, 2G, etc.
  • Logs at iOS iPhone configuration utility for Android Monitor.bat can be used for debugging.

That was it. Now, it wasn’t that simple.

As a final note, I reiterate the philosophy at STH – know the basics well, the rest automatically follows.

I conclude, hoping that this effort will be beneficial and meaningful to our readers. Please let us know below in the comments section on how we did.

Author: This post is written by our STH team member Swati Seela.

Recommended Reading

130 thoughts on “Software Manual Testing Interview Questions for Experienced Professionals”

  1. Hi, One of my friend faced this question in interview, Please tell me if the application is running successfully but unable to find in the google search…for example Facebook is my application but its not showing in google search then till me severity and priority of defect

    • Severity is low but priority is High. if application does not come in search result, chances of failure are more. bussiness risk is more.

      • Both severity and priority are High Since application does not appear in results, chances of failures are more.

        Terminology- meaning
        Severity – impact of customer’s business
        Priority – how soon a bug should be fixed

  2. I m a beginner in testing field but I got good information about this comments it very use full to who r interested in testing.

  3. I have been to an interview recently where I have been asked quite tricky questions like
    1. if you have reported a bug and developer says he cannot reproduce it. what would you do?
    2. If you have 2 hours to execute 30 test cases how would you do it.

    • I would rather do exploratory testing, because if you just have 2 hours for testing and have to execute 30 test cases in a hurry would be waste of time, because as a test eng first of all u should understand and analyse what u r doing.., which feature u r testing…

      • when we have less time but need to complete testing first thing we need to prioritize what test cases are critical and then we can use boundary value analysis and then execute them to finish it soon

      • If we have 30 test cases and we need to test all test cases in 2 hours we must do equivalence partitioning of test data for test cases like which are negative scenarios and which are positive, I do agree which danny that we should do exploratory testing( It is nothing but the testing way to cover all the priority area and verify that are working fine or not)

      • we need to prioritize the test cases,based on severity given and start execute the Test cases,First we need to execute all Critical and Major Test Cases and we can release the s/w to the customer even if it is having Minor defects and we should make shower that those Minor defects are not effecting customer business work flow…

    • If developer cannot replicate it then, you need to provide him the exact details of the scenarios that you are trying which is causing the defect, like screenshots, error log details, system logs, test data, environment, or a video recording will also help. Still developer doesn’t replicate it then you probably need to take it to manager for further discussion and decision making in the defect call.
      For point 2, i second Swetha’s views mentioned here.

    • Large number of Test Cases, you must be able to prioritize test cases as not all of them will have same priority. You may end up with High Priority, Medium Priority, and Low Priority set of Test Cases.

    • If you have 2 hours to execute 30 test cases how would you do it.: we will go for RBT(risk base testing) and priorities the Tc and focus on high priority tc .

  4. Hello Everyone Can anyone please send me the Test Material to test Customized CRM Website if anyone have.My Mail Id
    and My Mobile Number is:+91 8867055859

  5. Would like to thank Swati for the such a good article. The content is really and practical as well.
    Do keep sharing similar kind of information.


  6. Nice explanation for each andevery question for above duscussed questions. post the questions related to database testing .it will helpful to us

  7. Can someone give me your experience for this question?

    example of how you went about testing a web based application?

  8. Hii All,

    1-Can anyone tell me which automation tool is more popular UFT or selenium?
    2- Can anyone share some experiences of automation interviews?

  9. There is a one page in that 1-100lines are present,how we will click 50th line?
    There is a one home page how we will write xpath for all elements present in that home page dynamilly?

    • why you will write xpath for all 100 line , just click on 50th line inpsect element find attributes and write customize xpath for it as you mentioned its a dynamic xpath most probably the page designed with AJAX or Angular js.


  10. i have 2 years of experience in manual testing,i want to swich job ,so can you plz suggest me some material & topics,plz,its very urgent

  11. Thanks for sharing, I m having 4.5 yes of experience in manual testing, telecom billing, siebel & oracle crm, mobile application testing, plz confirm me if any vacancy for same field I can join immediately mail me on

    • Sanity should be performed first because of its a subset of a regression test where the smoke testing is the subset of acceptance testing.

    • Sanity test is done for particular module of application and smoke is subset of regression.
      Smoke is performed first to quickly check that after build deployment there is no errors in the application and we can proceed with regression .

  12. Hi,

    Excellent set of questions. Thank you for posting it! Though I have 2 questions:
    1. what are test estimation techniques? Have you used/done any test estimation in your project?
    2. If there is a bug which you missed to report and your product release date is near. And, you dont have time to do full regression. what will you do?
    Could you Please tell me how to answer these question .

    • for 2 question: You need to report it immediately and priorities it in your daily scrum(where dev ,business and qa are present) or you can schedule a incident call, in this call all can discuss how important this bug fix is, if all think this bug is not that imp functionality and all can live with it, so it should be kept in product backlog for further releases.

  13. There are 3 piece of code to be tested.Code B is dependent on code A and code C is independent. Now code B is ready for testing but code A is not and code C is ready for testing. What approach will you follow to test it.

    • Will go with Code C first as this is independent part
      Next code B excluding code A part as code B depended on code A
      Then after will go with code A

      • we can follow bottom-up approach, by using driver(duplicate module) for code A. code B is ready for testing but is dependent on code A.

  14. My question is, I am a Manual tester, but want to take steps to be an Automation tester.
    I am stumped as to where to start learning on this.

    1. What will I need to be a successful Auto tester
    2. What are the step by step actions that I need take, from the very basic.
    3. I do not know a language (example: Java).

    These are a few questions that I have.

    Thanks much!

    Any wisdom from a successful Automation tester would be super!

    • 1. Learn all BASIC JAVA concepts. (plenty of free courses are are available or you can subscribe to paid courses on udemy. I had one which i got on a deal for like $9.99)
      2. Once you get familiar with Basic java simultaneously you can start learning selenium. Use you tube for basic tutorials.
      3. Once you get familiar with very basic Selenium concept you can research same on udemy for selenium tutorials.

      Why i suggested JAVA+Selenium is because most of the industry I’ve seen uses java for automation and plenty of material is available on line for selenium as its open source.

      One more thing , without a programming Language its impossible to become a Automation Tester.
      And JAVA i thing is easiest to learn.

    • first of all tui Mr. Sankar ar sathe contact kor tar por tui nijar gar ta oke dis taholei hoya jabi bal . loke a akta job pacche na bal tor abar automation lagbe.

  15. I believe interview is an activity where we must be knowing that how to speak, what to speak. If we know the answers of questions but not able to speak than it won’t work out. Every-time it doesn’t possible that we know answers of all questions asking by an interviewer. But in this condition we must be know that how to tackle.
    For me there are two words which always help me to crack an interviews.
    “See” & “It Depends”, these two words usually help us to answer.

    I hope everyone would be able to relate these words if any of the questions you got stuck or not able to answer.

    All The Best!!

  16. I wasn’t able to answer a few tricky questions during my interviews. This blog from you helped me in preparing answers for such questions, with the help of tips shared. Thank you so much.

  17. Q: If there is a bug which you missed to report and your product release date is near. And, you dont have time to do full regression. what will you do?
    Could you Please tell me how to answer these question

    A: Have to inform to client about the bug before itself and should ask client to release the pending bug in the next sprint

  18. Nice work and good information shared. Thank You!

    Few query below:

    1. What is the difference between Test Script and Test Scenario?
    2. Please provide material on Test Estimation.

  19. As i understand, smoke testing should be done first. Smoke testing is done just before the build is accepted for system or regression testing. It describes the readiness of the build for further testing. On the other hand sanity testing is done just before the product is ready for delivery to the client i.e., at the last stages of the test closure just to ensure nothing is broken before it is shipped to client.

  20. Hi,

    This is Kushal. I have experience in SEO and m interested in software testing domain. So, want to switch on to Manual testing. Please if some could help me regarding the required concepts and if there is any openings for Manual testing.

  21. Hello,

    As a French teacher, I took Manual testing class long time ago. Now I want to come back to this field. Can anyone help me or guide me how to write a role of Manual tester for my interview? Thanks!

  22. I have a question on threads can anyone help?
    I am writing a query which gives me lakhs of records. Now each record I have to request to the server. I have written this logic in @Test.How to implement threads for these lakhs of records.

  23. You been assigned new work as part of an ongoing project.
    You have never had exposure to the technologies used, or had the opportunity to test anything like this before.
    The only thing you have been provided is a high level overview and the User Story that provides a bit more technical insight.
    In addition, the lead developer has given you a list of possible tests that need to be performed. She is available to answer any questions you may have.
    Most of the development has been completed barring some small changes.
    You been given 2 weeks to complete the testing.
    Briefly explain what steps/actions you would take to effectively test this new piece of work.

  24. You are part of a team that works within a very dynamic & fluid environment.
    You are responsible for the testing across a number of projects.
    All teams follow agile development practices, i.e. CI/CD, however some teams follow these more than others.
    Due to the nature of the product life cycle, some teams don’t always require testing on an ongoing basis.
    You are currently working on an important piece of work, however you been informed that you need to help test a critical part of the backend.
    The development of it was delayed and so now testing is crucial.
    At the same time, an additional small piece of work has been sent to you, which needs to be tested ASAP, and is due to be deployed into production tomorrow.
    Briefly explain how you would manage this sudden influx of work?

  25. Hi , i had attended an interview to which i am searching answer for. So the question is If u have completed all testing and release is day after tommorrow and it is the deadline like u have to submit it . But next day another Software with some new OS version has release with which ur software is not compatible. what will be Your take as a tester ? (Rem: Release is tommorrow. and U can’t wait for update)

    • There is two scenario in this question :-
      1. we don’t need to test that software because in question it is clearly mention that “Another software with some new OS version” then, what is the relation of that software with your current release…?
      2. And, if it relates with our current release then, we need to highlight these to customer & project manager that these integration testing not done after that its their call to release software or to postponed it.

  26. Hi,This is kiran,i had a question..pls answer.
    Q1:I have 2 testers in my team and 50 test cases assigned to each one but one tester took sudden leave for 1 week and i have 2 days/less time to release to client.This situation what is ur approach as test lead/sr tester?

    • Retrospective meeting is end of the each sprint which the scrum master conducted and as a team we discussed about what was done well during the sprint what worked well and what didn’t work well and could be done to improve the work for next sprint. It helped to progress our project make it us success.

  27. This is by far one of the best blogs I have found for QA Interviews. I have 5+ years of experience as a Manual and Automation tester and these are very basic questions you all should really prepare for. Some of the answers written by the author are what we do on daily basis as a QA. There are other QA questions I would definitely include, like 1) What is UAT? 3) How will you handle the timezone difference of your team working? For example, the Sales team is in London, UK and you are in Texas. How will you communicate and when? 4) What would you do if the requirements change in the middle of the Agile Sprint?


Leave a Comment