On this page
Questions to practise
Tell me about an interesting bug you found.
She wants to see how you notice problems and explain them clearly.
Choose one real bug. Say what you saw, how you made it happen again, and what happened after you reported it. Example: the app lost the basket when the phone went offline.
How did you prove the bug was real?
She wants a tester who checks carefully before reporting a problem.
Describe your steps. Say you tried to make the bug happen again, step by step. Mention the device, the version, or the settings you used. Say how many times you checked.
How do you decide what to test first?
Time is limited. She wants to know you choose the most important things first.
Say you start with the most important parts for users, like login or payment. Explain why: if these break, many people are affected. Then say what you test next.
How do you plan your tests?
She wants to see a clear, careful way of working.
Mention checking the requirements first. Then say you write test cases with clear steps and expected results. Name one way you stay careful, like a checklist or a second review.
Can you tell me a little about how you like to test?
She wants a picture of your normal working style.
Give two or three habits. For example: you read the requirements, plan the important tests, then try unusual actions too. Add one short example from your work.
How do you report a bug so a developer can fix it quickly?
Clear reports save time for the whole team.
Name concrete habits: a short clear title, numbered steps, expected and actual result, a screenshot or video. Say you talk to the developer directly if the bug is urgent.
A developer says your bug is not a bug. What do you do?
She wants to see if you stay calm and respectful in a disagreement.
Say you listen first. Then you check the requirements together. You show your steps again. If you still disagree, you ask the product owner. Talk about developers with respect.
Can you give me an example?
She asks this when an answer sounds too general, like 'I am very careful'.
Do not repeat general words. Tell one short, real situation: what happened, what you did, and the result. Keep it to four or five sentences.
What steps did you write in your bug report?
She wants proof that your reports are clear and exact.
Say the steps out loud, like in a real report. For example: 1. Add an item to the basket. 2. Turn off the internet. 3. Open the app again. Then say what you expected and what happened.
What happened after you reported the bug?
She wants to know if you follow the bug to the end.
Explain the next steps: the developer fixed it, and you tested the fix again. Mention if you checked nearby features too. Say what you learned from it.
Let me think of a good example of a bug I found.
Clara
AI coach
Leo
AI coach
Lines to try
Let me think of a good example of a bug I found.
First I tried to make the bug happen again, step by step.
I write the steps clearly, so the developer can see the problem quickly.
I start with the most important parts, because they affect the most users.
I expected this to happen, but instead the app did this.
If it is urgent, I talk to the developer directly.
Common questions
What if I don't remember a big or serious bug?
A small bug is fine if your story is clear. Dana cares about how you found it, how you checked it, and how you reported it. Pick one bug you understand well. Practise telling it in a few short steps.
My English is not perfect. Will that be a problem?
Speak slowly and use short sentences. Clear steps matter more than difficult words. If you need time, say: 'Let me think for a moment.' If you don't understand a question, you can ask: 'Could you say that again, please?'
How long should my answers be?
Try about one minute for each answer. Start with the main point, then give one example, then the result. If Dana wants more detail, she will ask. It is better to be short and clear than long and general.