Courses › Behavioral Interviews › Question Themes
Leadership & Conflict
Disagreeing with a manager, influencing without authority, and mentoring.
Conflict and leadership questions are the most common behavioral questions for engineers at every level. They test whether you can disagree productively, bring people along and get to good decisions — essential skills on any team.
Typical questions
- Tell me about a time you disagreed with a teammate.
- Tell me about a time you disagreed with your manager.
- Describe a time you had to influence someone without authority.
- Tell me about a time you led a project.
- Tell me about a time you helped someone grow.
What interviewers look for
- You disagreed about something that mattered — technical direction, priorities, quality — not personalities.
- You sought to understand the other perspective before pushing your own.
- You used data, prototypes or principles, not authority or volume.
- You reached a resolution — and maintained the relationship.
- You can disagree and commit when the decision goes the other way.
A strong conflict answer, outlined
Situation: Our team planned to build a custom job scheduler; I believed an existing workflow engine would serve us better. Actions: - Asked the tech lead to walk me through their reasoning — the main concern was operational overhead and vendor lock-in. - Built a two-day prototype of our most complex workflow on the engine and measured effort and failure handling. - Wrote a short comparison doc addressing their concerns specifically, including an exit strategy. - Proposed that the team decide together in a design review, with clear criteria agreed in advance. Result: The team chose the engine; we shipped in five weeks instead of the estimated three months. The tech lead and I co-owned the rollout. Reflection: Starting with their concerns, not my proposal, is what changed the conversation.
Disagreeing with your manager
Show courage and respect together:
- Raise concerns early and privately, with evidence
- Propose an alternative, not just an objection
- Respect the final call; commit fully; revisit later with data if needed
It's fine — even good — if the story ends with your manager being right and you learning something. That shows openness.
Leading without authority
Senior engineers lead through influence. Strong stories show you:
- Built a shared understanding of the problem before proposing solutions
- Created artifacts that moved decisions forward: design docs, prototypes, metrics
- Brought stakeholders in early so they co-owned the outcome
- Made it easy for others to say yes — reducing risk, offering help
Mentoring and growing others
Pick a specific person. Show that you diagnosed what they needed, tailored your approach (pairing, stretch assignments, feedback loops), and that they grew measurably — took on ownership, got promoted, became the go-to person for a system.
[!WARNING] Red flags - The other person is a villain and you are the hero - You "won" by escalating immediately - No resolution, or the relationship ended badly and you don't reflect on it - The conflict was trivial (tabs vs spaces)