The short answer
When a Staff Engineer drives junior developers off your team through aggressive, hostile behavior in pull request reviews, you are facing a severe crisis of engineering culture. Staff Engineers are highly compensated, immensely talented technical leaders. They often believe their technical brilliance grants them immunity from basic professional courtesy. They use code reviews to assert dominance, leaving harsh, belittling comments that humiliate younger developers. You cannot allow this toxicity to persist simply because the engineer writes excellent code.
As the Engineering Manager, you are the guardian of your team's psychological safety and talent retention. If you ignore the Staff Engineer's behavior, you endorse it. You will establish a culture of fear where developers hide their mistakes, avoid asking questions, and eventually quit. Your team's velocity will collapse, and you will become known across the company as a manager who harbors brilliant jerks.
You must explicitly and immediately correct the toxic behavior. You will not negotiate the necessity of professional communication, and you will not accept the excuse that they are just trying to maintain high code standards. By isolating the aggressive behavior and enforcing a strict framework for objective code review, you force the Staff Engineer to realize that their technical skills do not excuse their destructive impact on the organization. You must prove that leadership requires teaching, not just punishing.
Why this question is a trap
The trap relies entirely on the fear of losing a critical technical asset. The Staff Engineer is likely the architect of your most complex systems. They possess immense institutional knowledge and can solve problems in hours that would take others weeks. You are terrified that if you confront them about their attitude, they will quit in a rage, leaving your roadmap in ruins. You are tempted to write off their hostility as a minor personality quirk that the junior developers just need to learn to tolerate.
If you surrender to this fear and protect the Staff Engineer, the consequences are disastrous. You immediately sacrifice your junior talent pool. The two transfer requests are just the beginning. The rest of the team will actively avoid working on components owned by the Staff Engineer, creating massive bottlenecks in your delivery pipeline. Human Resources will eventually audit the turnover on your team and hold you accountable for fostering a hostile work environment. You will lose your managerial credibility entirely.
Furthermore, giving a pass to a brilliant jerk destroys your ability to hold anyone else accountable. If the rules of professional conduct only apply to average performers, your corporate governance is entirely fake. You must break this dynamic by proving that no single engineer, regardless of their output, is more valuable than the health and retention of the entire development squad.
What most people say
Most frontline engineering managers panic when confronted with a toxic top performer. They want to avoid a massive confrontation, so they try to find a soft compromise and blame the junior staff. They say something like, "I know you are just trying to keep the code quality high, but some of the juniors are getting a little sensitive about your comments. Can you try to use a few more emojis or maybe soften the language a bit so they don't get so upset? They are still learning the codebase."
This response is an absolute failure of managerial courage. By validating that the engineer is "just trying to keep the code quality high," you excuse their hostility. Calling the juniors "sensitive" throws your victims under the bus and confirms the Staff Engineer's belief that everyone else is just weak. Asking them to use emojis is a pathetic, administrative suggestion that fails to address the core cruelty of the behavior. You sound like a terrified coordinator begging for a favor rather than a leader enforcing a standard. The Staff Engineer will ignore your plea completely.
What to say instead
"Your recent pull request reviews are actively destructive to this engineering team. Driving two junior developers to request transfers because of aggressive, humiliating commentary is a massive failure of your leadership mandate. I do not care how technically accurate your code critiques are; your delivery is toxic. Effective immediately, your code reviews must be exclusively constructive and objective, focusing on teaching the architecture rather than attacking the developer."
This script is a flawless execution of behavioral correction and cultural defense. You open with a direct, uncompromising confrontation. Stating clearly that their reviews are "actively destructive" shatters their illusion that they are helping the team. You do not soften the blow. You name the exact damage they caused by citing the two transfer requests.
You then immediately dismantle their primary defense mechanism. By declaring that you "do not care how technically accurate your code critiques are," you separate their technical brilliance from their behavioral failure. You label the delivery exactly what it is: "toxic." You force the Staff Engineer to realize that being right does not give them the right to be cruel. You raise the conversation from a technical debate to a serious discussion about their leadership mandate.
Finally, you dictate the operational path forward. You do not ask for a favor. You mandate that their reviews must be "exclusively constructive and objective." You define the required behavior clearly, ordering them to focus on "teaching the architecture rather than attacking the developer." You solve the problem by forcing the senior engineer to act like a mentor. You protect the business and force your top performer to actually lead.
The phrase to anchor on
Exclusively constructive and objective.
How to deliver it
Deliver this response with the absolute, unshakable calm of a corporate director delivering a final warning. Your tone must project complete professional detachment and total command of your team's culture. Do not sound angry that they upset the juniors, and do not sound intimidated by their technical skills. Treat the interaction as a routine enforcement of professional physics.
Maintain direct, unwavering eye contact with the Staff Engineer. When you mention the two transfer requests, speak slowly and deliberately. You want the operational weight of that failure to land heavily in the room. When you outline the requirement for constructive and objective reviews, keep your voice entirely neutral. You are making a literal business routing decision to solve their behavioral problem, not begging for their understanding. You are issuing an ultimatum.
Mistakes that cost you the room
The most fatal mistake is delivering this feedback via Slack or email. Text-based feedback to an aggressive communicator guarantees a defensive, hostile written response that will escalate out of control. You must deliver this confrontation on a video call or in a private office where you control the cadence and the physical environment. Look them in the eye.
Another critical error is refusing to approve the transfers for the junior developers. If you force the juniors to stay on the team to prove a point, you revictimize them and guarantee they will quit the company entirely. Approve the transfers immediately to protect the juniors, and use the empty headcount as the visible consequence of the Staff Engineer's failure.
Do not threaten to fire the Staff Engineer in this initial conversation. The goal is rapid behavioral correction, not immediate termination. Issue the harsh warning, establish the new standard, and monitor their next five pull requests closely. If they violate the standard again, then you move directly to a formal Performance Improvement Plan.
Practice plan
First, gather the actual pull request comments as undeniable evidence. You must have the specific, hostile quotes printed out or open on your screen before you confront the engineer. If you do not have the hard data ready, they will claim you are exaggerating or taking things out of context.
Second, practice the transition from the hard confrontation to the required behavioral standard. You must sound entirely comfortable telling a brilliant engineer that their personality is unacceptable while smoothly offering a path to redemption. Record yourself delivering the script until the cadence sounds effortless and entirely devoid of emotional friction.
Finally, run the drill in the Talk Rightly studio. Focus heavily on keeping your facial expression completely neutral. When an arrogant top performer pushes back defensively, any sign of anxiety or frustration will invite them to argue louder. You must train your body to remain perfectly still under pressure, projecting absolute certainty in your behavioral boundaries.