Definition
- Control your response – Focus on your own actions, not on changing the other person.
- Assume good intent – Most difficult people are optimizing for something you cannot see, not being malicious.
- One-on-one first – Understand their perspective before reacting publicly.
- Shared goal – Name the common objective out loud so the conflict shrinks.
- Objective rules – Replace subjective debates with a written definition of done.
- Durable fix – A shared checklist that settles arguments once, not personal mediation every time.
Imagine at National Bank of India, Rajesh is a careful backend engineer who wants every edge case tested before release, and a teammate keeps pushing to ship fast. They are both right in their own way, but they keep clashing. Managing a difficult person is like being the bank teller who stays calm with an angry customer: you listen first, find the shared goal, and solve the real problem instead of winning the argument.
Understanding the Concepts
What is this question really testing?
Emotional intelligence, conflict resolution, and professional maturity. The interviewer wants to see that you can work productively with someone whose style clashes with yours without damaging delivery or team morale.
package com.bank.interview;
public class ConflictTest {
enum Signal { PROFESSIONAL, AVOIDANT, ESCALATORY }
public static Signal evaluate(boolean understood, boolean foundGoal, boolean builtDurableFix) {
if (!understood) return Signal.AVOIDANT;
if (!builtDurableFix) return Signal.ESCALATORY;
return Signal.PROFESSIONAL;
}
public static void main(String[] args) {
System.out.println(evaluate(true, true, true)); // PROFESSIONAL
}
}
How do you assume good intent?
Most difficult people are not malicious. They are optimizing for a deadline promise, a past incident that burned them, or a different definition of quality.
package com.bank.interview;
public class GoodIntent {
public static void main(String[] args) {
System.out.println("He seems reckless, but maybe he promised a stakeholder a date.");
System.out.println("She seems slow, but maybe she was burned by a production bug before.");
System.out.println("Assume the positive interpretation first; verify with a conversation.");
}
}
How do you find the shared goal?
Both people want the transfer service at National Bank of India to succeed. Name that shared goal out loud: "We both want reliable transfers shipping on time." The conflict usually shrinks.
package com.bank.interview;
public class SharedGoal {
public static void main(String[] args) {
String myGoal = "Full test coverage on money paths";
String theirGoal = "Ship the reporting feature on time";
String sharedGoal = "Reliable transfers shipping on time";
System.out.println("My goal: " + myGoal);
System.out.println("Their goal: " + theirGoal);
System.out.println("Shared goal: " + sharedGoal);
}
}
How do you build an objective definition of done?
Replace subjective debates with a written checklist. "Any change touching money must have tests and a second reviewer. Everything else can move fast."
package com.bank.service;
import java.util.List;
public class DefinitionOfDone {
record Rule(String scope, String requirement) {}
public static void main(String[] args) {
List<Rule> rules = List.of(
new Rule("Money path", "Tests required + second reviewer"),
new Rule("Non-money", "Tests recommended, single reviewer OK")
);
System.out.println("Shared Definition of Done:");
rules.forEach(r -> System.out.println(" " + r.scope() + ": " + r.requirement()));
System.out.println("The checklist decides, not our opinions.");
}
}
What does the one-on-one conversation look like?
Ask to understand, not to persuade. Listen for the constraint behind their behavior.
package com.bank.interview;
public class OneOnOneApproach {
public static void main(String[] args) {
System.out.println("Open: 'I want to understand your perspective on review speed'");
System.out.println("Listen: learned he had a deadline promise to stakeholders");
System.out.println("Propose: 'Can we agree on a definition of done that respects both?'");
System.out.println("Result: he agreed; his urgency was not carelessness, it was a promise");
}
}
How do you make the fix durable?
A one-time conversation resolves one conflict. A written definition of done prevents all future conflicts of the same type.
package com.bank.interview;
public class DurableFix {
public static void main(String[] args) {
System.out.println("One-time: 'We agreed to review this PR faster' -> helps once");
System.out.println("Durable: 'Money path = tests + 2nd reviewer; non-money = fast' -> helps always");
System.out.println("After the rule was written, the argument disappeared.");
}
}
What should you never do in this answer?
Never badmouth the other person, never say "I avoided them", and never say "I escalated to my manager" as your first and only action.
package com.bank.interview;
public class NeverDo {
public static void main(String[] args) {
System.out.println("Never: 'He was impossible to work with' -> badmouthing");
System.out.println("Never: 'I just avoided him' -> avoidance is not resolution");
System.out.println("Never: 'I went straight to my manager' -> shows no personal effort");
System.out.println("Always: 'I initiated a conversation, found the shared goal, built a rule'");
}
}
What are common interview follow-up questions?
Expect: "Did the relationship improve?" (yes, trust grew), "What if they refused to cooperate?" (escalate only after personal effort), and "Would you work with them again?" (yes, we became effective collaborators).
package com.bank.interview;
public class DifficultPersonFollowUps {
public static void main(String[] args) {
System.out.println("Improved? -> Yes, review turnaround dropped from days to hours");
System.out.println("Refused? -> Escalate after personal effort, with evidence");
System.out.println("Again? -> Yes, we became effective collaborators after the rule");
}
}
Visual Overview
┌────────────────────────────────────────────────────────┐ │ Managing a Difficult Relationship │ ├────────────────────────────────────────────────────────┤ │ │ │ ┌──────────────────┐ │ │ │ 1. ASSUME GOOD │ They are optimizing for │ │ │ INTENT │ something I cannot see │ │ └────────┬─────────┘ │ │ │ │ │ ▼ │ │ ┌──────────────────┐ │ │ │ 2. ONE-ON-ONE │ Listen to understand │ │ │ (private) │ their constraint │ │ └────────┬─────────┘ │ │ │ │ │ ▼ │ │ ┌──────────────────┐ │ │ │ 3. SHARED GOAL │ "We both want reliable │ │ │ │ transfers on time" │ │ └────────┬─────────┘ │ │ │ │ │ ▼ │ │ ┌──────────────────┐ │ │ │ 4. OBJECTIVE │ Written definition of done: │ │ │ RULE │ money = tests + 2nd review │ │ │ (durable) │ The rule decides, not opinions │ │ └──────────────────┘ │ │ │ │ Result: friction disappeared, trust grew │ └────────────────────────────────────────────────────────┘
Key Takeaway
Early at National Bank of India I worked closely with a teammate whose style clashed with mine on the transfer service for Rajesh's and Priya's accounts. I wanted full test coverage and a second reviewer on any change that touched customer money, and he wanted to ship quickly. Every code review turned into a personal argument and our pull requests were stuck for days.
Instead of escalating or avoiding him, I asked him for a short one-on-one and listened first. I learned he was under pressure from a commitment he had made to stakeholders, so his urgency was not carelessness, it was a promise. Once I understood that, I separated the person from the problem and proposed something neutral: a shared definition of done. Money-path changes require tests and a second reviewer; everything else can move fast.
After that, the argument disappeared, because the checklist made the decision, not our opinions. Review turnaround dropped from days to hours, and we shipped the feature on time without cutting corners on the money path.
What I learned is that most difficult relationships are really unmanaged expectations. When I assume good intent, find the shared goal, and make the rules objective, the friction usually solves itself and the relationship actually gets stronger.
Remember one sentence: Assume good intent, find the shared goal, and replace subjective friction with an objective written rule that settles the debate permanently.
---