London

June 28–29, 2027

New York

September 15–16, 2026

Berlin

November 9–10, 2026

How to coach engineers from different backgrounds

Great work doesn’t speak for itself.
November 19, 2026

You have 1 article left to read this month before you need to register a free LeadDev.com account.

Key takeaways:

  • Context defines what good work looks like. Effort counts for different things on different teams. Show engineers how their work connects to business priorities so they don’t have to guess what leadership values.
  • Coach the person, not the résumé. “Be more visible” isn’t advice anyone can act on.
  • Write down the career path nobody spells out. Ask where each person learned their idea of success, then explain how growth works on your team.

When I moved from working as a consultant to be a full time employee at a Fortune 500 fintech company, I assumed my approach to career growth wouldn’t change much: work hard, deliver what was assigned, and meet expectations. I was completely wrong. Context mattered more than I realized.

In consulting, I had well-defined goals and expectations for my work, but the ownership ended when the project was completed. In the full time role, I had far more freedom to shape my work, but the freedom comes with the responsibility for finding opportunities to improve the product, develop team members, and keep my application reliable. 

Nobody sat me down and explained that shift. It took me years to figure out on my own. What frustrated me most was the time I lost learning the lesson someone could have explained to me early on.

Today, I lead four engineering teams with more than 60 people, including consultants, internal transfers, external hires, engineers from other industries, graduates starting their careers, and interns.

I constantly see smart people bringing a career map that worked well elsewhere into an environment with completely different rules. That is why the same question about growth always requires a very different conversation.

The same effort can mean different things in different teams

A lot of people assume that knocking out assigned work and satisfying the expectations quickly leads straight to recognition and promotions. No one can deny that hard work matters, but speed and execution don’t tell the whole story of how someone actually adds value to the team or organization.

Let’s look at two engineers who might have similar experience and technical abilities, yet work in very different environments.

One builds customer-facing features, where success means identifying the user needs, evaluating the tradeoffs, and presenting the solutions effectively.

The other maintains a mission critical internal app, where preventing failures, app crashes, and thinking about the end-to-end transaction flow matter far more than presenting to customers.

Certainly, neither job is better than the other, but their opportunities to demonstrate impact are different.

I also saw that engineers often assume the hardest work is the work the organization values most. An intricate and highly complex feature might get little executive attention, while a minor fix to a glitch gets spotlight because it solves a problem leadership cared about at that time.

When expectations are not clear, that feels unfair and leads to disappointment, but managers should explain how the team’s effort gets connected to business priority. They should not leave their teams trying to guess priorities based on who got appreciation in last Friday’s email.

Then you have visibility. Many engineers still hold onto the idea that their smart work should speak for itself. In a large Organizations, leaders outside of their immediate team may never know how much effort or cross-functional team work went into the project unless someone tells them.

Helping your team to highlight their contributions shouldn’t be considered as teaching them to brag. It is giving leaders visibility into work they would otherwise miss.

Coach the person, not the resume

One engineer on my team did brilliant technical work, but he froze up in meetings while explaining how he solved the problem. Just telling him to “be more visible” would’ve been useless.

So, I started bringing him along to team presentations. On the first deck, I ran through nine slides and handed him one. Eventually, I took a step back and let him take over more of the deck until he was running the whole thing himself.

That gradual handover mattered. Having space to practice in a low impact environment gave him the confidence he needed before presenting to a broader group. From there, I brought him into stakeholder calls.

People across the company started noticing his work, and eventually, managers outside our team were trying to recruit him for higher-level roles. I can’t credit one presentation exercise for his whole career trajectory, but giving him a structured way to communicate made his impact impossible to miss.

Another case called for the exact opposite approach. A fresh computer science graduate joined a team doing mostly manual testing. He was a solid coder stuck doing manual tasks that barely touched his skill set. I could’ve just dumped an automation task on his plate and walked away. Instead, I invited him onto the hackathon team I mentored, where they built an enterprise testing platform around his skill set. The platform later saw extensive use for client testing. 

That experience completely transformed how he saw his skills fitting into a complex enterprise environment and how he can adapt. It was about spotting what he brought to the table and building a bridge so those strengths actually helped both him and the business.

Two engineers needed different coaching; one needed a gradual path to visibility of his work and the other needed a chance to apply his skills.

This is the exact reason I refuse to compare a new hire to someone who already knows our routines inside out. A person arriving from a different industry may be used to the habit of completing requirements before development begins, while the new team develops requirements and solutions in parallel. The immediate gap may be familiarity with the operating model, not ability.

Make the unwritten career path visible

My initial conversation with a new team member is about the work environment they came from and what growth means to them. I also ask about their past expectations and where they want to go in their career path.

Some care about titles. Others prioritize compensation. If I assume that everyone wants the same path and destination, my advice will miss the point even before we start.

I also try to carefully separate personal aspirations from company policy. Someone coming from a fast-moving startup might expect a promotion every year. A larger organization operates under different eligibility rules, role requirements, opportunities, and also headcount limits. Instead of promising a timeline I can’t guarantee or control, I explain how the process works and what real evidence of readiness looks like for that next designation.

When explaining career growth, I usually break it down into four distinct phases:

  • Discovery: learning about current role responsibilities, understanding the process, setting realistic expectations, and adapting the culture. 
  • Excellence: consistently delivering in your current role and meeting expectations.
  • looking beyond your boundaries: evolving to understand the next level and seeing where you can expand your reach.
  • Stepping up: taking on next-level responsibilities with a safety net. 

That last phase acts as a bridge. Once an engineer has clear proof of operating at that level, our advancement conversations become grounded in facts rather than guesswork. It’s never an automatic guarantee of promotion, but it’s a far better roadmap for the gradual progress than just telling someone to work harder.

NYC 27 Pre sale ticket block image

Coach engineers with context, not comparisons

Comparison across teams is another challenge managers cannot avoid. An engineer looks at a peer advancing faster and assumes that their career path also should look identical. I try to walk through differences in scope, visibility, business needs, and open opportunities without invalidating their frustration and disappointment.

You have to be candid about what’s actually in their control and what isn’t. Switching teams just because another group seems to be moving faster often ends in disappointment.

Above all, I try to be open about the lessons I learned the hard way. My goal is not to make someone repeat my path to prove they deserve to grow. It’s to give them context early enough to make smart choices for themselves.

Looking back, I wish someone had told me that doing good work and understanding how to grow in a career are two different things. I had to learn ownership, the priorities around my work, and how to communicate my impact on my own. That took much longer than it should have.

As engineering leaders, we can’t hand everyone the same career map, but we can uncover where they learned their definition of success, explain the expectations of the team they are in now, and help them navigate forward. They will write their own journey. 

We don’t hand out maps. We give them a compass so they can chart their own path.