Project Interview Questions for Testers
Process questions check that you've worked inside a real team: how bugs move through Jira, who attends Scrum meetings, when you write test cases, how big the team was, what happens when requirements change. Interviewers compare your answers with how teams really work — so specific, consistent details matter more than textbook definitions. This guide gives a model answer for each question, with what makes it credible.
1. How Do You Report a Bug?
Model answer
"First I reproduce it and check it isn't already logged. Then I create a Bug in Jira linked to the story, with a clear summary, environment and build, exact steps, expected and actual results, and evidence — a screenshot or video, plus logs or the API response. I set severity based on impact and suggest a priority; the product owner confirms priority in triage. Then I follow it through the workflow and retest the fix."
A well-written bug
| Field | Example |
|---|---|
| Summary | Checkout: "Pay" button stays disabled after a valid card is entered (Safari only) |
| Environment | QA, build 2.14.3, Safari 18, macOS |
| Steps | 1. Log in as test user · 2. Add any product · 3. Checkout · 4. Enter test card 4111… |
| Expected | "Pay" becomes enabled |
| Actual | "Pay" stays disabled; console shows a validation error |
| Severity / priority | High / to be set in triage |
| Evidence | Video, console log, network response |
| Links | Story SHOP-412 |
A good summary says where, what and when, so the triage team understands it without opening the ticket. More: Jira Defect Management and Severity vs Priority.
The bug lifecycle
New → Open/Assigned → In Progress → Fixed/Resolved → Retest → Closed — or Reopened if the fix fails, and Rejected/Duplicate/Deferred when triage decides so. Workflows vary by team; describe yours.
2. Who Joins the Scrum Calls?
| Event | Who attends | What testers contribute |
|---|---|---|
| Daily scrum (15 min) | Developers (including testers); Scrum Master often facilitates | Progress, blockers — environments, data, open bugs |
| Backlog refinement | Product Owner, developers, testers, sometimes BA | Questions, edge cases, testability, acceptance criteria |
| Sprint planning | Whole Scrum team | Testing and automation estimates |
| Sprint review | Scrum team and stakeholders | Demo of tested features, quality status |
| Retrospective | Scrum team | What slowed testing and how to fix it |
In Scrum, "Developers" means everyone building the increment — testers included. The Product Owner owns the backlog and priorities; the Scrum Master coaches the process and removes impediments. More: Agile & Scrum for Testers.
3. When Do You Start Writing Test Cases?
"As soon as a story is refined and its acceptance criteria are agreed — usually at the start of the sprint, in parallel with development. I write scenarios and test cases from the acceptance criteria and designs, review them with the developer or BA, and have them ready when the build arrives. Automation scripts for the story come once the feature is stable, often in the same sprint."
In STLC terms this is the test design phase, after requirement analysis and planning. The key point interviewers look for: testing starts before code is finished, not after. See The Complete Manual Testing Tutorial.
4. How Long Was the Project, and How Big Was the Team?
"The product has been in development for about three years; I joined 18 months ago. Our Scrum team had eight developers and three QA — two focused on automation, including me — plus a Product Owner and a shared Scrum Master. A separate team handled performance testing."
- Give numbers that match your résumé and LinkedIn.
- Distinguish the product's age from your time on it.
- Mention the QA-to-developer ratio and how work was split — it tells the interviewer how much you owned.
5. How Many Bugs Did You Find?
Don't quote a big number — talk about quality and impact:
"It varies by sprint — typically a handful to a dozen per sprint on new features, fewer in regression. The ones that mattered most were a double-charge bug when users clicked 'Pay' twice, found in exploratory testing, and a rounding error in tax totals that our API tests caught before release."
One or two specific, high-impact bugs are far more convincing than "I found 500 bugs". Be ready to explain how each was found and what happened next.
6. What Happens When the Client Changes Requirements?
"The change comes in as a new or updated story. We do an impact analysis — which features, test cases, automation scripts and data are affected — update the traceability and test cases, and re-estimate. If it lands mid-sprint and is large, the Product Owner may move it to the next sprint. Then we test the changed area and its neighbors first and run regression." Full walkthrough with an example: Requirement Changes & Release Pressure.
7. Which Tools, Database and Tech Stack?
Answer with your real stack, in layers:
| Layer | Example answer |
|---|---|
| Application | React front end, Java Spring Boot microservices, REST APIs |
| Database | PostgreSQL (plus Redis for sessions) |
| Test tools | Selenium + TestNG, REST Assured, Postman, Maven |
| Management | Jira (stories, bugs), Confluence (docs), Zephyr or Xray (test cases) |
| CI/CD | Git, Jenkins, Docker |
If asked how you check the database: SQL queries after UI or API actions — manually in a client like DBeaver, or in automation through JDBC. See SQL for Testers.
8. More Process Questions
- What's your Definition of Done? — code reviewed, tests passed, acceptance criteria met, no open critical bugs, automation added where agreed.
- How do you handle a bug the developer rejects? — point to the requirement and evidence; involve the Product Owner if the requirement is unclear.
- How many environments did you have? — e.g. Dev, QA, Staging, Production, and what testing happens in each.
- How do you share test results? — Jira test execution, CI reports, a short sprint quality summary.
- What would you do if the build is broken on the last day of the sprint? — raise it immediately, test what you can, and make the risk visible to the Product Owner.
Rehearse all of these out loud, with follow-ups, in the Selenium Interview Simulator, or practice Jira-specific questions in the Jira Interview Simulator.
From Real Projects
When I explain my own projects, I use the same structure this page recommends. For example: Canolog is an automotive dealership management system that connects sales, inventory, finance, service and parts; my role covered requirement analysis, writing and reviewing test cases, execution and defect tracking in Jira, and Selenium script development in a POM-based framework. Prepare your own project the same way — the application, your role, your tools and one concrete contribution. On Apkope, prospect and customer data arrives from email, phone, social media and chatbots, so test scenarios had to cover every channel that feeds the same records. Show how you worked with developers, BAs and the rest of the team.
FAQs
How do you report a bug in Jira?
Reproduce it, check for duplicates, create a Bug linked to the story with summary, environment, steps, expected and actual results, severity and evidence, then track it through retest and closure.
Who attends Scrum meetings?
The Scrum team — Product Owner, Scrum Master and Developers (including testers); stakeholders join the sprint review.
When do you write test cases?
Once stories are refined and acceptance criteria agreed — in parallel with development, so tests are ready when the build arrives.
How should I answer "how many bugs did you find"?
Give a realistic range and describe one or two high-impact bugs, how you found them and what they prevented.
Who sets bug priority?
The tester sets severity from the technical impact and may suggest priority; the Product Owner (or triage team) decides priority based on business needs.
What happens when requirements change?
Impact analysis, updated test cases and traceability, re-estimation, and testing the changed area plus regression — with large mid-sprint changes often moved to the next sprint.
Related
- Real-Time Questions: Framework & Testing
- Jira Interview Questions
- Top 30 Manual Testing Interview Questions
