5 Career Lessons Learned Over 40 Years to Advance Your Engineering Career

A Life Engineered

Summary:

This video distills 40 years of career experience into 5 critical "unlearnings" for engineers aiming for advancement. The speaker, an Amazon Principal Engineer, explains that solely focusing on technical skills is insufficient.

• 1. Make your work visible. Hard work without visibility is invisible and won't be rewarded. Prioritize solving problems that those in power care about and ensure they see your contributions.

  

• 2. Prioritize collaboration. Beyond a certain technical threshold, your ability to enable others and foster teamwork is more crucial than being the absolute best engineer.

  

• 3. Promote your work. Don't assume good work is self-evident. Managers are busy; proactively communicate your contributions and their impact.

  

• 4. Treat your manager as your most important customer. Your manager controls your projects, reviews, and promotions. Align your efforts with their key metrics and help them succeed.

  

• 5. Embrace high agency. Don't wait for permission or opportunities to come to you; actively create them and take control of your career path.

  

Introduction [0:00]

The speaker, a Principal Engineer at Amazon with no engineering degree, reflects on 40 years of experience, realizing that merely excelling technically did not guarantee career advancement. He wasted years doing what he thought he was supposed to do, only to find himself stuck. He identifies 5 key beliefs he had to "unlearn" to achieve significant career growth.

1. Hard Work Without Visibility is Invisible Work [0:40]

• The Problem: The belief that "if I worked hard enough, someone would notice and reward me" led to stagnation. Managers see only a fraction of your effort, and if what they see isn't impressive, the hard work done in secret doesn't matter.

  

  • An example of invisible work: He spent weeks refactoring a messy legacy system at Amazon, making it clean, maintainable, and reducing operational burden. Despite being objectively better, it only received a "looks good" in code review and went largely unnoticed.

    

  • An example of visible work: A few weeks later, he spent a couple of hours writing a simple script to automate a weekly report, saving program managers three hours of tedious work weekly. This made him a "hero" because the impact was immediate and visible to many.

    

    

• Key Questions to Ask: Before investing hours, ask yourself two questions:
  1. Is what I'm working on solving a problem that someone with power actually cares about?
  2. Can they see me solving that problem?

     

• Actionable Advice: If your work doesn't have natural visibility, actively broadcast it.
  • Practice: Never let your manager ask for your status. If they have to ask, you lose.
  • Start small by promoting others' work (e.g., call out a teammate's contribution, send a quick message to their manager).

    

  • Gradually include yourself in positive updates once comfortable. You're not bragging; you're accurately reporting what happened.

2. Technical Skills are Not the Only Path to Advancement [3:41]

• The Problem: The belief that "if I became the best engineer in the room, I'd get ahead" proved false beyond a certain threshold.

  

  • Beyond a certain skill level, being difficult to work with is what truly holds a career back, not technical proficiency.
  • Software development is a team sport; the person who gets ahead isn't always the most technical but the one others want on their team, who makes collaboration easier.
• The Contrast:
  • Technically Brilliant but Difficult Engineer: Solved complex problems, but working with them was exhausting due to their tendency to shoot down ideas and make others feel stupid. People started routing around them.

    

  • Technically Solid and Collaborative Engineer: Not necessarily the absolute best, but highly valued because they made meetings better, improved others' code, and asked questions that helped the whole team think more clearly.

    

• Outcome: The collaborative engineer was promoted first and continued to rise, because at senior levels, impact is measured by what you enable others to do, not just what you do yourself.

  

• Actionable Advice: Shift your investment to how you show up for others.
  • Ask yourself: Am I the person people want in the room, or are they relieved I'm not there?
  • When disagreeing, do you help others understand or just try to prove you're right?
  • Multiply the people around you – this is the real leverage that propels your career.

    

3. Don't Rely on Work Speaking for Itself [5:46]

• The Problem: The belief that "good work is self-evident" is a form of self-sabotage.

  

  • Managers are overwhelmed and not observing every detail of your work. If you don't actively surface your contributions, they'll assume you have none.

    

• The Solution (A Personal Example):
  • The speaker managed a massive project involving nearly 100 engineering teams, a huge scope, an unmovable deadline, and billions of dollars at stake.
  • He sent daily email updates to literally thousands of people involved, including junior engineers and VPs.
    • The emails covered project status, help needed, blockers, and next steps.

      

  • This constant communication ensured that when the project launched successfully, everyone was aware of his critical role and contributions in real-time.
• Actionable Advice: Proactively communicate your status and contributions.
  • Play the game: Never make your manager ask for your status. If they ask, you lose.
  • If you're uncomfortable with self-promotion, start by promoting others' work.
  • Once comfortable, include your own contributions in team updates (e.g., "The team shipped this feature on time. [Teammate's] testing was crucial, and I'm proud of the integration work that I contributed."). This is accurate reporting, not bragging.

    

4. Your Manager is Your Most Important Customer [8:31]

• The Problem: Treating your manager like any other stakeholder is a significant mistake.

  

• The Solution (A Personal Example):
  • The speaker's manager was under pressure due to the team's low delivery velocity.
  • Instead of just working harder, he analyzed where the team's time was wasted (unclear specs, constant back-and-forth between product and engineering).

    

  • He presented this data to his manager, empowering the manager to initiate crucial process improvements.

    

  • This helped his manager succeed and get promoted, and the manager remembered who helped him get there, which in turn helped the speaker's career.
• Actionable Advice: Treat your manager like your most important customer.
  • The "Pro Move": In your next one-on-one, ask: "What's the one metric or initiative you're being measured on right now?"

    

  • Then, actively look for ways to contribute to that metric, even if it's outside your direct responsibilities. Surface problems, propose solutions, and provide data to support their goals.
  • When your manager succeeds, they will remember and return the favor.

5. Don't Wait for Permission; Take Your Turn [10:32]

• The Problem: The belief that you should "wait for clear directions before acting" or wait for someone to give you permission to do more.
  • While you wait, others are actively creating their own opportunities and making things happen.
  • "Your turn doesn't come. You take your turn."

    

• Low Agency vs. High Agency:
  • Low Agency: Characterized by thoughts like "This isn't fair," "My manager plays favorites," or "I've been here longer." This leads to waiting, hoping, and complaining, with no change.

    

  • High Agency: Characterized by "I need those projects to grow. What can I do?" This leads to proactive action.

    

• Actionable Advice for High Agency:
  • Message colleagues to shadow them or join their planning meetings.
  • Tell your manager you want to lead the next initiative and ask what you need to do to make it happen.
  • Identify an unsolved problem, build a quick prototype, and create your own high-visibility project.
  • If nothing changes, update your resume and find a job that offers the work you deserve.
  • High agency is the belief that you are in control of your outcomes, regardless of circumstances. Act like an owner, not a victim. The question isn't "can you," but "will you?"