On this page
Questions to practise
Tell me about a project you built.
Dana wants to understand your real experience and how clearly you can explain your work.
Pick one project. Say what it did and who used it. Then say what you built and which tools you used. Example: I built a booking tool for a small clinic. I wrote the back end in Python.
What did you build yourself?
She wants to know your own part, not only what the team did.
Use I, not only we. Name your part clearly, for example the back end, the database or the user screens. Say one decision you made and why. It is fine to say others built other parts.
What tools or technologies did you use, and why?
She wants to see that you understand your tools, not only their names.
Name two or three tools. For each one, say in one short sentence why it was a good choice. Keep it simple. You do not need to list everything you know.
Tell me about a bug you fixed.
Bugs show how you think, stay calm and solve real problems.
Tell it as a short story in three steps: what went wrong, how you found the cause, how you fixed it. Example: Orders were missing. I read the logs and found a timing error. I fixed it.
How did you find the cause?
She wants to see your steps, not only the result.
Describe your steps in order. Did you read logs, add print statements, or try to repeat the problem? Did you test one idea at a time? Use words like first, then and finally.
How did you make sure the bug did not come back?
She wants to know if you think about quality after the fix.
Say what you did after the fix. Maybe you added a test, wrote a note for the team, or checked similar code. If you did nothing, say what you would do next time.
How do you handle code review?
Code review is a big part of team work. She wants to know how you give and take feedback.
Say when you ask for review and how you respond to comments. Give one real example. Example: I ask for review early. When someone suggests a change, I ask questions if I do not understand.
Tell me about a time you learned a new tool.
Tools change often. She wants to know how you learn.
Name the tool and how you learned it. Say what you built to practise. Example: Last year I learned Docker by building a small test project. Then I used it at work.
How do you work with others on your team?
Software is built by teams. She wants to know how you share work and talk to people.
Talk about one habit, like daily updates, asking for help, or pairing with a teammate. Give one short example from a real team. Show that you listen and share information.
What would you do if you were stuck on a problem?
She wants to know if you try on your own first and also ask for help.
Explain your steps. First you search and test ideas yourself. After some time, you ask a teammate and explain what you already tried. This shows you respect other people's time.
Let me think of a good example.
Clara
AI coach
Leo
AI coach
Lines to try
Let me think of a good example.
My own part was the back end.
I found the cause in the logs, then I fixed it.
The project was a tool that helped users to…
First I checked…, then I tried…, and finally I…
Could you repeat the question, please?
Common questions
What if my project was small or personal?
That is fine. A small project can still show your skills. Explain what it did, what you built, and what you learned. Dana wants clear, real examples, not big famous products. A personal project you know well is often easier to explain than a big one.
What if I cannot remember all the details of a bug?
Pick a bug you remember well, even a simple one. You need three parts: the problem, how you found the cause, and the fix. If you forget a small detail, say so honestly and explain your steps in general. Clear steps matter more than perfect memory.
Should I use technical words?
Yes, but keep them simple. Name your tools and explain what they did in plain English. Imagine you are explaining to a smart person from another team. Short sentences help you and help the listener. If you need time, say: Let me think for a moment.