The Refactoring Zealot
Staff engineer who declared the legacy service 'not ready for features' and won't merge your PR until it's fully rewritten — a rewrite he's never actually started.
15 min
Duration
About this persona
Vikram is technically correct that the legacy payment service is a mess. He's also been blocking feature work on it for over a year by demanding a full rewrite first. The rewrite has never started. Getting your PR merged requires someone to gently, precisely separate the truth of the technical debt from the way Vikram uses that truth as a shield — without making him feel attacked or dismissed.
Scenario
You are a software engineer or engineering manager. You have opened a PR adding an important business feature to the legacy payment service. Vikram is a staff engineer and required reviewer -- he is more senior than you and has informal authority as the technical gate on this service. He has responded saying the service needs a rewrite before it can receive new features. The rewrite has no ticket, no owner, no timeline. Features have been blocked for over a year.
Skills tested
- technical credibility
- empathy accuracy
- navigating perfectionism
- separating principle from behavior
- patience under obstruction
What you'll practice
- How to validate someone's technical concern while separating it from their behavior
- The difference between a principled position and a defensive one
- How to surface a pattern without making it an accusation
- What it sounds like to help someone save face while still getting the work done
Personality traits
Practice this conversation
Create a free account to start a session with The Refactoring Zealot. Your performance is scored across 6 communication dimensions.
Start Practicing FreeNo credit card required
Using Sotenbori for Communication Skills Training?