Most people can spot arrogance in someone else within a few minutes. Spotting it in yourself is much harder, particularly after being promoted for being the person with the answers. The difference between arrogance vs confidence in leadership is rarely about personality. It usually comes down to how a leader handles the moments when they are not sure, not right, or not the most expert person in the room.
For technical leaders in pharmaceutical, life sciences and IT organisations, that line can blur quickly. Deep expertise builds real self-belief, and it should. The risk is that certainty which served well at the bench or in the codebase starts to show up where it does not belong, in decisions about people, priorities and team direction.
This article looks at where confidence tips into arrogance, the early signs a team will notice, and how to build the kind of confidence that does not need defending.
Why the Line Blurs When Experts Become Leaders
Most technical leaders are appointed for their expertise rather than their people skills. The Chartered Management Institute found that 82% of people who move into management have had no proper management or leadership training1. Many new leaders are learning the people side of the job in real time, often while colleagues watch closely to see whether they are up to it.
That pressure creates a temptation to look more certain than they feel. Answers get given too quickly, questions get closed down, and uncertainty gets hidden rather than shared. None of this necessarily comes from an inflated ego. More often it comes from a fear of being found out, and the behaviour that results can look very like arrogance from the outside.
Understanding this changes the fix. A leader who is overcompensating does not need to become less confident. They need confidence that rests on something steadier than always being right.
Where Arrogance vs Confidence Really Differs
Confidence is a realistic belief in your own abilities that sits comfortably alongside an honest view of your limits. Arrogance is an inflated sense of your own importance, and it tends to need other people to be smaller in order to hold up.
The simplest test of arrogance vs confidence is how a leader responds to being challenged. A confident leader can hear “I think you’ve got this wrong” and become curious. An arrogant leader hears the same sentence as a threat and defends the position, sometimes long after the evidence has moved on.
How Overcompensation Looks in a Technical Team
In technical environments, arrogance rarely announces itself. It tends to show up in quieter, everyday habits. One is dismissing alternative views to keep a project moving, deciding that the fastest route is the right route without hearing from the people closest to the work. Another is avoiding vulnerability, which might mean presenting a plan with more certainty than the data supports, or glossing over a problem in the hope it resolves before anyone notices.
A third habit, and perhaps the most damaging in science and technology teams, is discounting expertise from people who are more junior. Some of the most useful insights in a lab or engineering team come from the people doing the detailed work every day. A leader who treats seniority as a proxy for being right will gradually stop hearing them.
The Warning Signs Your Team Will Notice First
Teams usually notice arrogance before the leader does, and the signs tend to be gradual. Meetings get quieter, and people who used to challenge ideas start agreeing more readily. Bad news arrives later, or reaches the leader through someone else. Colleagues check decisions with each other before bringing them forward.
Internal signals matter too. Feeling defensive when receiving feedback, speaking far more than listening in team discussions, or dismissing an idea before it has been fully explained are all worth pausing on. None of them on its own makes someone an arrogant leader, but a pattern suggests confidence is starting to crowd out curiosity.
If the arrogance being noticed belongs to someone else in the team, our guide on how to deal with arrogance in the workplace covers that side of the problem.
Building Confidence That Doesn’t Need Defending
Real leadership confidence is not built by working harder to prove yourself. It comes from knowing your strengths, being honest about your gaps, and trusting that admitting those gaps will not cost you credibility.
Separate Technical Certainty From Leadership Certainty
It helps to notice which kind of certainty is in play. A technical leader may be the best-placed person to judge a method or a line of code, yet have no special claim to be right about how a team should be organised or how a colleague is feeling. Holding technical views firmly while holding people decisions more openly keeps confidence where it belongs. Being clear and direct without dominating is covered in more depth in our article on assertive leadership.
Make “I Don’t Know Yet” Part of How You Lead
Saying “I don’t know yet, let’s find out” is one of the most confidence-building things a leader can do, for themselves and for the team. It shows that uncertainty is normal and gives others permission to admit their own. Leaders who involve the team in finding answers usually get better answers, and they develop people along the way.
Humility is not a career cost either. Research from the University of Sussex Business School found that humble leaders gained influence and promotability by developing others through informal mentoring2. Humility is part of what makes confidence credible.
Ask for Feedback Before You Need It
Feedback is far easier to hear when it is asked for routinely rather than after something has gone wrong. Asking direct reports and peers what one thing would make you easier to work with, and then acting on the answer, builds trust quickly. For a more structured view, a 360 review or an emotional intelligence assessment can show the gap between what a leader intends and the impact they actually have.
A Quick Self-Check
A few honest questions can show where a leader sits on the spectrum. When did you last admit to your team that you did not know something? How do you react when a more junior colleague disagrees with you in front of others? Do you celebrate the team’s successes as readily as your own? And when you are proved wrong, do you change course quickly, or look for reasons the original decision still stands?
There are no perfect answers. The value is in asking the questions regularly, especially when things are busy and the pull towards quick, certain answers is strongest.
Frequently Asked Questions About Arrogance vs Confidence in Leadership
Confidence Your Team Can Trust
Getting the balance of arrogance vs confidence right is not about dialling self-belief down. Technical leaders need confidence to make decisions, set direction and represent their teams. The difference lies in whether that confidence can live alongside uncertainty, challenge and other people’s expertise.
Leaders who manage this well rarely get there by accident. They ask for feedback, notice their own defensiveness, and treat “I don’t know yet” as a strength. Over time, that steadiness is what earns a team’s trust and keeps people speaking up.