Irbisa · Cheatsheet
Behavioral Interview
Tell me about yourself, the hardest bug, mistakes in production, conflicts, pushing back on requirements, estimates and deadlines, feedback, mentoring, questions for the interviewer
Junior Developer · 17 questions
- 01
Tell me about yourself.
The interviewer checks whether you can give a short, relevant summary and why you fit this role.
- 02
Why are you leaving your current job, and why do you want to join us?
The interviewer checks your motivation and whether you would leave them for the same reason.
- 03
Tell me about a project you are proud of. What was your part in it?
The interviewer checks the scale of what you have built and what you personally did in the team.
- 04
What are your strengths and weaknesses?
The interviewer checks self-awareness and honesty.
- 05
What are your salary expectations?
The recruiter checks whether you fit the budget and know your market value.
- 06
We have a few minutes left. What questions do you have for us?
The interviewer checks your interest and what matters to you; "no questions" reads as indifference.
- 07
Why did you choose Flutter, and when did it hold you back?
The interviewer checks that your choice was deliberate and that you know Flutter's limits from experience, not from articles.
- 08
Tell me about the hardest bug you have fixed.
The interviewer checks how you debug: how you narrow a problem down, which tools you use and whether you fix the cause or the symptom.
- 09
Tell me about a mistake you made that reached production. What changed afterwards?
The interviewer checks ownership: whether you admit the mistake, limit the damage fast and change the process so it does not happen again.
- 10
Tell me about a release that broke on only one platform. What did you do?
The interviewer checks how you act under pressure and whether you know that one Dart codebase still means two builds.
- 11
Tell me about a conflict with a colleague. How did you resolve it?
The interviewer checks whether you can disagree without damaging the working relationship.
- 12
How do you estimate a task, and what do you do when you see you will miss the deadline?
The interviewer checks whether you plan realistically and raise a risk as soon as you see it, not on the deadline day.
- 13
Tell me about a time you disagreed with a product or design requirement. What did you do?
The interviewer checks whether you think about the product and push back with arguments instead of silently building or refusing.
- 14
How do you work with designers on a shared widget library?
The interviewer checks whether you can turn a design system into code both sides trust and handle the gap between a mockup and a real device.
- 15
How do you give and receive feedback?
The interviewer checks whether you can hear criticism without getting defensive and tell a colleague about a problem without hurting them.
- 16
How have you helped a junior developer grow, or raised your team's level?
The interviewer checks whether you multiply the team's output, not just your own.
- 17
How do you convince the business to give you time for technical debt?
The interviewer checks whether you speak the business's language and prioritise, instead of asking for a rewrite.