← Back to the position
Bloodcuff
Scrum Master
We’re going to have a conversation about real work you’ve done
Before you start
This isn't a resume — not bullet points, not titles, not buzzwords. Have a few real projects in mind that you were involved in and that connect to what this role needs. You don't have to squeeze everything into one project — pull from whichever one fits the question best.
Take your time. Specific answers are better than short tidy ones. If you feel like you need a paragraph to explain something, write the paragraph. We're listening for what you personally did, what you decided, and what you'd say if a colleague asked you about the work over coffee.
It's okay if your experience is transferable rather than exact — explain how it applies. And please don't overstate your role. Clear boundaries help us evaluate you fairly.
What we'll cover
1
Your work today
Roles, domains, and what you spend time on
2
Projects in detail
Real projects you were involved in that connect to what this role needs
3
Tools you used
What and why — including AI tools in your workflow
4
How you solve problems
Your patterns for diagnosing problems and deciding what to do
5
A decision you made
What you chose and what you gave up
6
Ownership boundaries
What you owned vs. what others owned
7
Role transfer
How your past work maps to this role
8
Optional work evidence
GitHub, portfolio, or other public artifacts you can share