Pre Screening Interview Questions and Answers: It is always good to have a checklist of questions you can ask during an interview. These are some of the questions that you should use in your pre-screening interviews.
A pre-screening interview is a type of screening interview that allows a company to identify suitable candidates for an upcoming position. The pre-screening interview is usually done before the formal interview, which makes it easier for companies to choose the best candidate and avoid wasting their time on candidates who would not be suitable for the job.
Being interviewed for a job can be a stressful experience. However, with proper preparation, you can turn it into an enjoyable and productive interaction. You need to be well-prepared for this task as the interviewer will probably ask you questions that are relevant to the position.
This article is a list of interview questions you should expect to be asked during a pre-screening. Some of these questions are standard, while others are based on the job and industry you will be working in.
Pre Screening Interview Questions
- How’s your relevant experience in Rest assured and Selenium?
- Can you give me a high-level summary of the automation framework?
- What BDD Framework have worked you on?
- Do you use Core Java or Advanced level?
- How you handle exceptions in core Java?
- What’s your contribution to the storage /sprint area?
- What version control and repository u use?
- How about a code repository?
- For CI/CD who develops the scenario?
- Any experience in UFT or Mobile Automation.
- What other BDD framework have you worked in?
- How do you build an automation framework?
- The basic difference between JSON and cucumber?
- What kind of reports or validations you do in Automation?
- Where is the code located?
- Worked with GIT or GIT labs?
- How do you do exception handling in Java?
- How do you handle Null point exception?
- What is the main class in cucumber?
- How do execute the scenario that you automated?
- How to resolve the merge conflict in GIT?
- The process you go through to determine what more inputs you need.
- Are you offering test cases or just automating the test cases?
- The process you used to automate new test cases
- Do you have experience in testing directly with API?
- Experience with SWA
- Do you have any functional testing experience?
- How would you rate yourself in Selenium and Java?
- How to handle merge conflict?
- In Java, how about method overloading?
- Exception handling scenario
- Any experience in UFT or LeanFT?
- Webservices automation?
- Any challenges you faced while automating?
Pre Screening Interview Questions and Answers
- IF you are working on a user story, but become blocked by test data, what do you do?
Ans: While working on a User story first thing is you should look for if the story is in a ready state or not. That is if it meets the definition of ready… This should also include whether test data is available or not… Else that story can’t be moved to do state.
If you are blocked by test data, then you have to ask the Development team to do the required mapping of functionality, then the sanity testing to be done to check the basic functions and most importantly include the product owner or BAs to arrange a walkthrough on the BRD. In that walkthrough, the testing team and Dev team should also join.Sometimes for an end to end testing, a synergy is also needed with the backend team and the data set they require should be incorporated into the front end application.
- What does a QA person do when testing a new feature with limited info?
Ans: To start a feature you need to have an adequate amount of info. Having limited info can’t define a feature. The product owner should come up with the required info before the team starts its work on the feature. If only QA-related information is missing the QA person should seek help from the Business or PO or the team whoever can help. Scrum and agile believes in openness and communication. The QA person should ask for the information and then start his/her work.
- Explain the difference between exploratory and scripted testing.
Ans: As per my knowledge exploratory testing is experienced and knowledge-based testing where the tester does testing randomly and important features may not have 100% code coverage. Whereas Scripted testing is always planned and covers testing of all the features. Others can give their view as well.
- Explain why integration testing is important.
Ans: Integration testing is important because the components or modules may work perfectly independently but that may fail at some points when they are integrated. For example due to configuration settings or other stuff.
- What data points do you use to determine if a feature is ready for shipping to the public?
- How do you define quality?
Ans: In general prospective quality is the value that a customer gets from a product. If a product works perfectly without any problem we can say the quality of the product is good.
- What do you do when a developer rejects your bug?
Ans: If you understand the function properly and the defect you raised is a defect and the developer rejects it, you can reopen the defect and have a discussion with the developer as well as BA or Solution architect or dev team whoever are interested to attend the discussion and take it with them. If it is not an actual defect you need to understand why and then close it or deferred it as per the team’s practice.
- How should Manual testers work with SDETs?
- What tools or metrics would you use to identify a production issue? how would you begin triaging an issue?
- How do you set expectations with stakeholders?
Ans: To set expectations with the stakeholders, you need to understand their Business functionalities properly, should be properly involved in the discussion, during the sprint review they can see your demo and also you need to do your job proactively. This is my view. There may be different answers, as this is a subjective question.
These Pre Screening Interview Questions you should expect to be asked during a pre-screening interview. If you’re thinking of applying for a job, or simply want to know what’s expected of you, this post is for you! We’ve broken down the most common questions we ask at employers and included them in the list below. If any of these sound familiar, share this post with your friends and family members who might be looking for jobs.