My journey from a engineer to a senior engineering manager has spanned over 15 years and several continents, evolving through a series of roles that demanded not only technical prowess but profound leadership growth.
Throughout my career from my early days, performing service desk roles to architecting IT infrastructure in Lisbon to overseeing cloud engineering teams across international borders I have learned that the path to senior management is as much about mastering invisible struggles as it is about visible accomplishments.
From individual contributor to people leader
Early in my career, my impact was straightforward to measure, before working with lines of code committed, features delivered, and systems improved.
My focus, initially, was on technical excellence and problem-solving within defined scopes. However, the moment I transitioned to management, a subtle but seismic shift occurred. Success no longer rested primarily on my individual contributions but on the collective output and health of my teams.
It felt I no longer matter, felt I was alone.
This pivot required a fundamental mental shift. I had to learn to care deeply about people their growth, motivation, and well-being while still keeping an eye on project goals and deliverables. The invisible struggle was internal relinquishing control over tasks I once owned, trusting others fully, and shifting satisfaction from personal technical achievements to the success of those I lead.
Learning to let go was especially challenging. It was tempting to jump in and “fix” problems myself rather than coaching a team member through finding solutions. Overcoming this impulse to micromanage required building confidence in my team’s abilities and embracing vulnerability as a leader.
Building leadership muscle the early tests
Leadership is frequently described as a muscle that requires consistent exercise. For me, the earliest tests were uncomfortable yet formative.
I volunteered for unglamorous responsibilities like managing endless migrations and resolving team conflicts tasks that rarely receive accolades but were critical to team health and operational continuity.
These experiences cultivated a servant leadership mindset leadership is less about recognition and more about service, making life easier for others and enabling them to excel.
This philosophy guided how I gave credit selflessly, whether applauding a junior engineer’s debugging success in stand-ups or publicly acknowledging product managers’ strategic insights.
The practice of candidly seeking feedback on my leadership style proved invaluable.
Early project leads solicited honest input from peers, which sometimes stung but ultimately refined my approach and helped me avoid common pitfalls.
The challenge of giving candid feedback
Giving constructive feedback especially negative feedback remained one of the toughest yet most vital skills to develop. Initially, I feared causing discomfort or harm to relationships by addressing shortcomings openly. I often delayed difficult conversations or sugar-coated critiques, which only diluted their impact.
With time, I learned that honest, empathetic feedback is a gift that fosters trust and growth. Adopting frameworks like Observation-Feeling-Need-Request helped me surface issues without blame, making conversations more productive and less confrontational.
In senior roles, this challenge intensifies as feedback extends to peers and even superiors. Holding up a mirror to others demands courage, tact, and emotional intelligence. Mastering this art has been a cornerstone of my leadership maturation and has enabled me to cultivate cultures of continuous improvement.
Mentoring and delegation growing others as a core responsibility
Mentoring emerged as both a responsibility and a personal passion. It demanded stepping outside the comfort of technical mastery to focus on others’ development. I began with informal pair programming sessions and evolved into crafting one-on-one structures that supported career growth plans.
Delegation was no less complex. I realized that effective delegation is an art it requires entrusting not just tasks but ownership, providing clear context but allowing autonomy in execution. I found that stepping back was difficult; it meant risking failures but also creating invaluable learning opportunities for team members.
Watching colleagues transform through mentorship was profoundly fulfilling and reinforced that leadership is less about telling and more about empowering.
Leading without formal authority
As a senior engineering manager, I frequently influence beyond my direct team. Whether collaborating with product, design, or external stakeholders, success hinges on building relationships and aligning diverse interests without explicit authority.
This influence requires patience, deep listening, and credibility cultivated through consistency. I’ve learned that success is often a quiet accumulation of trust and shared vision rather than top-down directives.
Navigating this leadership without formal authority has been one of the less visible but most strategic challenges in my role.
Bridging technology and business
One of the greatest challenges and opportunities of senior technical leadership is translating technical complexity into business impact. This skill is essential when communicating with executives, product leaders, or customers who may not share a technical background.
I have had to cultivate the ability to frame issues in terms of risk, value, and opportunity. This requires shrinking complicated technical problems into clear narratives that connect to company objectives while retaining enough nuance to inform decisions.
Bridging this divide is rarely highlighted in management guides but is critical for gaining strategic buy-in and advancing initiatives.
Navigating ambiguity and change
Unlike engineering roles grounded in specifications and measurable deliverables, management is often defined by ambiguity. Priorities shift, projects evolve, and information remains incomplete.
At times, this ambiguity provokes discomfort and doubt. Learning to make decisions with partial information and remain adaptable has been essential. I have found that transparency about uncertainty, combined with frequent check-ins and incremental adjustments, builds resilience.
Leading teams through change be it organizational restructuring or agile transformations has demanded emotional stamina and clear communication to maintain morale and momentum.
The mental load and burnout risk
The cumulative mental load of senior management is rarely visible externally. On any given day, I manage deadlines, interpersonal conflicts, strategic alignment, coaching, and operational issues simultaneously.
This sustained cognitive and emotional effort introduces burnout risks not just for me but also for my teams. I have learned the importance of managing my energy through rest, reflection, and setting healthy boundaries.
Moreover, supporting my team’s mental health requires empathy and creating environments where vulnerability and discussion of wellbeing are normalized rather than stigmatized.
Staying hands-on the balancing act
Maintaining technical engagement while fulfilling leadership duties is a constant balancing act. I have always valued staying hands-on whether reviewing code, participating in architecture discussions, or experimenting with emerging AI technologies.
This involvement helps me retain credibility and stay connected to the challenges my teams face. Yet, I also need to prioritize leadership time, avoiding the temptation to dive too deeply into technical execution.
Finding this balance is an evolving discipline, often requiring me to recalibrate based on team maturity and organizational needs.
Building a culture of psychological safety
Fostering psychological safety the confidence for individuals to take risks and express ideas without fear is foundational for innovation and team effectiveness.
Achieving this culture demands consistent behavior modeling, encouragement of diverse perspectives, and addressing toxic behaviors proactively.
Creating such an environment requires persistence and vulnerability from leadership and is a delicate task rarely captured fully in leadership literature.
Continuous learning and self-reinvention
The journey of a senior engineering manager is one of perpetual learning. The technical landscape shifts rapidly, and leadership challenges evolve continuously. I have embraced a growth mindset fueled by curiosity and humility.
Recognizing that I will never know everything has freed me to seek out new knowledge eagerly, solicit feedback, and adapt.
This openness to reinvention and self-awareness sustains my passion and effectiveness in leadership roles.
Unexpected lessons and realities
Beyond frameworks and best practices, my senior management experience has taught unexpected lessons
- The paradox of visibility Leaders are often unknown heroes behind team success but also visible targets for blame.
- Balancing competing priorities means constantly negotiating trade-offs without perfect solutions.
- Leadership can be a lonely place trusted confidants and networks become vital.
- Emotional labor is an underappreciated strain in mentoring, conflict resolution, and culture building.
These realities demand resilience, emotional intelligence, and thoughtful reflection.
Seems easy, right?
In the past information was not has accessible has today. Professionals now can with a few clicks and prompts obtain all the necessary info, templates to managed their daily activities. But most soon find out that sometimes all this help cannot prepare you to unexpecting things, even a simple 1-2-1 can go in a way you didn’t even expected. So, the best is to maintain everyone and yourself expectations. Change will happen and sooner than you think. The trick is to go with the flow, and sometimes anchor somewhere to get in touch, and see ahead.
The invisible weight of self-doubt
Almost every engineering leader I’ve spoken with shares a recurrent, unspoken struggle: self-doubt. As an engineer, my impact was measurable lines of code, features deployed. As a senior manager, the value I bring feels abstract team morale, culture, delivery velocity. Doubting whether I add real value or am making the right decisions is a constant companion. This self-questioning fuels growth but can also impair confidence if unchecked.
The overwhelming volume of responsibilities
The sheer amount of work as a senior engineering manager can overwhelm even the most organized. Juggling urgent fires, strategic planning, stakeholder alignment, career growth conversations, and administrative tasks often means not everything gets done. The real skill lies in ruthless prioritization and saying no to good things to say yes to great ones. Communicating clearly on limits and managing expectations becomes a leadership imperative.
Managing emotional and mental load
The emotional labor involved in leadership is profound. Supporting individuals through challenges, resolving conflicts, motivating diverse personalities, and coping with accountability pressures add to a mental load seldom visible from outside the role. Balancing empathy with firmness and managing my own wellbeing alongside my team’s is a daily, often silent, struggle.
The silent leadership moments
Not all leadership moments are loud or visible. Sometimes, leadership manifests in listening deeply, providing a calm presence during crisis, or facilitating connections quietly. These less glamorous but vital moments embody true leadership impact and often go unnoticed.
Ethical decision making and moral responsibility
Senior roles bring ethical dilemmas balancing business goals with fairness, integrity, and team wellbeing. Decisions can affect careers and company reputation and are not always black and white. Embracing moral courage and cultivating ethical leadership is a critical but seldom-highlighted challenge.
Personal sacrifices behind the role
Long hours, missed family moments, postponed vacations, and mental exhaustion are frequent companions on the leadership path. These sacrifices often remain unseen but profoundly shape the human experience behind the title.
Some great tips.
I’ve seen too many new managers cling to their old identity, micromanaging code reviews or taking over critical tasks. The faster you accept that your value is now in enabling others, the better off you and your team will be.
The glue that holds teams together
Early in my management career, I assumed that if I had the right answers, my team would follow. I was wrong again. Communication isn’t about having the answers; it’s about asking the right questions and listening really listening to what’s not being said.
- One-on-ones aren’t status updates. They’re opportunities to understand what motivates your team, what frustrates them, and where they want to grow. I’ve had engineers open up about burnout, career doubts, and personal challenges things I never would have known if I’d treated these meetings as box-checking exercises.
- Transparency builds trust. When I started sharing the “why” behind decisions even the unpopular ones my team became more engaged. They didn’t always agree, but they respected the honesty.
- Conflict isn’t failure. It’s a sign that people care. The key is to address it early, before it festers. I’ve found that framing disagreements as “How can we solve this together?” rather than “Who’s right?” leads to better outcomes.
Your most important lever
A mediocre team with great processes will always underperform compared to a great team with mediocre processes. Hiring is the highest-leverage activity a manager does.
- Culture fit isn’t about similarity. It’s about shared values. I’ve hired engineers who challenged my assumptions and pushed the team to think differently and those hires have led to our best innovations.
- Onboarding sets the tone. A rushed onboarding process signals that the team doesn’t value new members. I now treat the first 30 days as critical: pairing new hires with mentors, setting clear expectations, and giving them early wins to build confidence.
- Diversity isn’t optional. Homogeneous teams miss blind spots. I’ve seen firsthand how diverse perspectives lead to more robust solutions and better team dynamics.
The oxygen of high-performing teams
Engineers don’t leave companies; they leave managers who don’t invest in their growth. Your team’s development is your responsibility.
- Career conversations aren’t annual events. They’re ongoing dialogues. I’ve made it a habit to ask, “What’s one skill you want to develop this quarter?” and then help them find opportunities to practice it.
- Failure is a teacher. I’ve shifted from punishing mistakes to asking, “What did we learn?” This doesn’t mean tolerating sloppiness, but it does mean creating a culture where risks are taken and lessons are shared.
- Feedback is a gift. I used to dread giving critical feedback, fearing it would demotivate. Now I know that withholding feedback is the real demotivator. The key is to make it specific, actionable, and balanced with recognition.
The art of letting go
I used to think delegation was about offloading work I didn’t want to do. I was wrong. Delegation is about trust and empowerment.
- Ownership > tasks. When I delegate, I’m not just assigning a task; I’m entrusting someone with a piece of the team’s success. This means giving them the authority to make decisions, not just follow instructions.
- Mistakes are part of the process. I’ve had to resist the urge to step in when I saw someone struggling. Instead, I ask, “How can I support you?” rather than “Let me take over.”
- Delegation is a skill. It requires knowing your team’s strengths, weaknesses, and aspirations. I’ve gotten better at matching tasks to people’s growth areas, not just their current skills.
Strategy over tactics
It’s easy to get lost in the day-to-day firefighting. But the best managers keep one eye on the horizon.
- Technical debt is a strategic issue. I’ve learned to frame it not as a “nice-to-have” but as a risk to the business. This has helped me secure time and resources to address it.
- Your team’s roadmap should ladder up to company goals. I now start every planning session by asking, “How does this align with where the company is going?”
- Invest in your future leaders. I look for engineers who not only excel technically but also show potential in mentoring, decision-making, and communication. I give them stretch opportunities to grow into leadership roles.
Emotional intelligence in action
I used to think leadership was about logic and process. I’ve since learned that the most effective managers are the ones who understand the human side of work.
- Empathy isn’t weakness. It’s the foundation of trust. I’ve had team members go through personal crises, and how I responded with flexibility and support had a lasting impact on their loyalty and engagement.
- Stress is contagious. If I’m frazzled, my team will be too. I’ve had to learn to manage my own emotions, especially in high-pressure situations.
- Celebrate the wins. It’s easy to move on to the next problem, but taking time to recognize achievements big and small fuels morale and motivation.
It’s a journey
My journey from engineer to senior engineering manager has been as challenging as it has been rewarding. It has required mastering technical skills and, more importantly, invisible struggles related to leadership, empathy, influence, and continuous growth.
Sharing these unseen aspects aims to provide a fuller picture for those aspiring to similar roles. Leadership is a human endeavor with no simple formula an ongoing journey of learning, adaptation, and impact.
Despite the challenges, the privilege of guiding people, shaping culture, and contributing to meaningful outcomes continues to inspire and motivate me.
About the Author
Diamantino Almeida is a tech leader, coach, and writer reshaping how we think about leadership in a burnout-driven world. With over 20 years at the intersection of engineering, DevOps, and team culture, he helps humans lead consciously from the inside out. When he’s not challenging outdated norms, he’s plotting how to make work more human one verb at a time.