Not Every Scrum Master Job Is Worth Taking: Interview Red Flags
- Mary Iqbal
- 18 minutes ago
- 4 min read
Red flags I look for (and why I walk away)
After more than 20 years coaching Scrum teams, I’ve learned the interview isn’t just about them judging me: I’m judging them right back. I’m looking for clues about whether this is a place where I can actually help teams improve, or if it's just a toxic waste of my time.
Not every Scrum Master job is worth taking.
Here are my Red Flags
Culture, culture, culture
If they casually mention burnout, blame, or constant fire-fighting but show little interest in addressing the underlying issues, I know I’m walking into a problem. A Scrum Master can coach and facilitate, but can’t single-handedly fix deep cultural problems without the organizational will to do so.
Likewise, if the expectation is frequent overtime work for anyone on the team, I am going to nope out of that. I don't want to be part of a leadership team that demands unpaid labor from the team. Even if it is paid, there is rarely (make that, never) a good reason for more than a forty-hour workweek for the team on a regular basis.
Leadership
I always ask: “What are the biggest problems your Scrum teams are facing today?”
This question tells me a lot.
It's fine if they have problems that I can solve (excessive processes, even some interpersonal conflict) but if I hear that leaders are not open to change, or they don’t want to do Agile, or they are antagonistic to Agile, or anything along those lines, I start questioning whether I can actually make a difference there.
No career path
I'm here to grow, too. So I always ask what the career path looks like for Scrum Masters. If the answer is vague or hand-wavy, that tells me everything I need to know. There should be a career path for Scrum Masters. It can be as simple as Associate Scrum Master → Scrum Master → Senior Scrum Master → Agile Coach.
Bonus points if Scrum Masters may be able to move into Management positions (it says a lot about what they think of Scrum Masters, even if you are not particularly interested in Management yourself.) I want to know - does this organization promote from within or do they always hire from outside whenever there is a promotion opportunity?
Part-time Product Owner
A part-time PO can mean that the organization is not investing in Scrum. I will be asking follow-up questions here to see what other resources they may be lacking and whether there is an organizational will to give the Scrum team the support that they need. A part-time PO almost always leads to weak backlog refinement, unclear priorities, and the team guessing at value. It makes me question whether the organization truly believes in Scrum.
Technology-siloed teams
Every organization that uses Scrum will have at least some teams that are specific to a single technology. But if ALL teams are like that, then it causes unnecessary dependencies. Now I love a challenge, and I would love to help an organization to move from technology silos to product teams (I mean I would LOVE to!) but if rather than fixing it, they want to just Band-Aid it with something like SAFe, well, I'm not super excited about that. Scaled frameworks are frequently used as Band-Aids to work around poorly designed team structures.
Green Flags (Signs This Could Be a Great Fit)
They’re actually hiring a dedicated Scrum Master
Just seeing the role funded and taken seriously is a great sign. Too many organizations undervalue the Scrum Master and then wonder why teams never reach high performance.
Using AI constructively
We all need to learn to use AI. And I want to keep growing my skills. So, I want to know that I will be able to learn and grow using the latest tools. (Similarly, I always ask what they are using for the Scrum board (e.g., Jira, Azure Dev Ops, Monday, etc.) If the answer is that they are using a spreadsheet and aren't open to anything else, I'm just not interested in that anymore.
They see the Scrum Master as more than an admin
If they understand that the Scrum Master is a leader, a coach, and not just an admin, that's fantastic. This is obvious by the questions that they are asking me. If they ask me questions about how I have helped improve team performance, then I know this is how they see me.
The Scrum Master role reports into an Agile Delivery Office
I get genuinely excited when the role sits in an Agile Delivery Office (or similar central agile support structure). It tells me the organization sees agile as an ongoing capability, not a one-time project. And besides that, it means I’ll have peers to collaborate with, share lessons, and avoid feeling like the lone voice pushing for better practices.
Who am I interviewing with?
I pay close attention to who is part of the interview process.
Is it just the hiring manager? Or do they include other leaders, peers, or even someone I’d be working with day-to-day?
It’s a really positive sign when organizations include peers in the process. It tells me they value collaboration and want to make sure the fit goes both ways.
Just as important — do I actually connect with these people? Do their communication styles work for me? If I can see myself working with them, that’s a strong signal this might be a good fit.
At the end of the day, I treat every interview like a two-way street. I want a job where I can make a difference and grow my skills. Red flags help me avoid wasting years in a dead-end job. Green flags tell me this might be a place where I can actually thrive.
It's not that I need to walk into a high performing team (there would be nothing for me to do, then) but I do need to know that I can lead change. That's what I'm looking for.
If you’re a Scrum Master interviewing right now, trust your gut on these signals. The right role should feel like a fit for both sides.
-------
Set yourself apart during your job search. Join one of our upcoming Rebel Scrum training sessions or attend Scrum Day Madison 2026 to network with your peers.