Burned out, frustrated, or convinced your job is the problem? Before you quit, get clear on what is actually broken. In this episode, Steve and Jake sit down with career coach Ben Fox, who helps burned-out software engineers figure out what is next. They break down bad managers, weak boundaries, AI-driven change, career uncertainty, networking, and how to know when to fix the situation versus leave it. Not theory. Practical, tactical advice for engineers who want more control over their careers.

Key Topics Covered:
• How to tell whether the job is the problem or your own boundaries are making it worse
• Why high-achieving engineers often overwork, people-please, and carry those habits into the next job
• The “Goldilocks quit date” for turning an emotional exit into a deliberate decision
• How AI is changing engineering work without eliminating the value of judgment, creativity, and problem-solving
• Why a bad manager can make you question an entire career you may still love
• How to manage upward before deciding the situation is hopeless
• Why career experiments beat making huge decisions based on fear
• How cold outreach and relationship-building can uncover better opportunities
• Why more education can become a way to delay a decision instead of make one
• How thinking like a business owner removes ego and creates better career decisions

Actionable Steps:
• Audit your last week and list what energized you versus what drained you
• Set a clear stopping time for work and protect nights and weekends
• Identify what you are contributing to the situation before blaming the environment
• Ask your manager directly for the support, clarity, or changes you need
• Talk to people already doing the work before changing roles, companies, or industries
• Run small career experiments before committing to a major move
• Reconnect with people in your network without overthinking the ask
• Use AI to remove repetitive work so you can spend more time on judgment and creative problem-solving
• Define a realistic quit date if staying indefinitely is no longer acceptable
• Ask what would need to change for you to genuinely enjoy the role again

Who This Episode Is For:
• Engineers who are burned out but unsure whether quitting is the answer
• High performers working nights and weekends with weak boundaries
• Engineers dealing with micromanagement or poor leadership
• ICs questioning their future as AI changes how engineering work gets done
• Anyone who feels stuck but has not yet tested another path

Why It Matters:
Career growth is not just about working harder. Your energy, boundaries, visibility, relationships, and willingness to speak up all shape your performance. If you never identify what is actually draining you, you can leave one job and recreate the same problem somewhere else. Own what you can change, test what you cannot, then make the decision with clarity.

Where to Listen:
Spotify
Apple Podcasts
Or wherever you get your podcasts

Find Ben Fox:
Visit benfoxcoaching.com to learn more about Ben’s coaching and sign up for a free 45-minute diagnostic call.

Connect with Ben on LinkedIn, where he regularly shares career insights, lessons from his client work, and practical ideas for engineers navigating change. 

Share:
If this episode hit home, send it to someone. The Impactful Engineer grows by word of mouth, just like the best careers do.

Most engineers try to improve focus by working harder, becoming more disciplined, or finding a better productivity system. That misses the real problem.

You probably have too many things competing for your time, energy, and attention.

In this episode, Steve and Jake break down why real focus starts with elimination. That means deciding what actually matters, accepting the tradeoffs, and removing the projects, commitments, distractions, and decisions that keep pulling you away from it.

Not theory. Practical, tactical advice for engineers who want to execute at a higher level without constantly fighting themselves.

Key Topics Covered:

• Why willpower is a terrible long-term strategy for staying focused
• The hidden cost of trying to maintain too many priorities at once
• Why becoming great often requires deliberately becoming less involved elsewhere
• How scattered technical interests can keep engineers from developing real expertise
• Why specialists become the people others specifically request for important work
• How saying yes to everything destroys execution and credibility
• Why fewer priorities reduce decision fatigue and mental clutter
• How simplifying routine decisions preserves energy for higher-value work
• Why every meaningful goal requires a tradeoff
• How focused seasons can accelerate career and personal progress

Actionable Steps:

• Write down the three to five things that matter most in your current season
• Audit where your time and mental energy actually go each week
• Identify commitments that do not support your highest priorities
• Eliminate unnecessary activities instead of trying to manage them better
• Choose which technical or professional skill you want to become known for
• Stop accepting work that compromises execution on your highest-value projects
• Create clear criteria for what deserves a yes and what automatically gets a no
• Simplify repetitive decisions wherever possible
• Write down what you are willing to trade to reach your current goal
• Commit long enough for focused effort to compound into visible expertise

Who This Episode Is For:

• Engineers who constantly feel busy but are not making enough progress
• High performers taking on too many projects and responsibilities
• Engineers struggling to become known for a specific strength
• Professionals who feel mentally overloaded by competing priorities
• Anyone serious about accomplishing something that requires concentrated effort

Why It Matters:

Your time and energy are finite. Every unnecessary commitment takes resources away from something that could actually change your career.

Focus gives you the bandwidth to execute better, build deeper expertise, become more valuable, and earn opportunities that average performance will never create.

You do not need to become better at juggling everything. You need to decide what deserves your attention in the first place.

Where to Listen:

Spotify
Apple Podcasts
Or wherever you get your podcasts

Share:

If this episode hit home, send it to someone. The Impactful Engineer grows by word of mouth, just like the best careers do.

How do you know when you are starting to lose trust at work? Sometimes the signs are obvious. Sometimes they look like fewer assignments, meaningless work, weak feedback, or people simply avoiding you. In this episode, Steve and Jake break down the warning signs that an engineer may be underperforming and, more importantly, how to turn it around. Not theory, practical, tactical advice for rebuilding trust, earning better work, and proving through execution that you deserve more responsibility.

Key Topics Covered:
• Why getting fewer meaningful assignments can be a warning sign
• What it means when coworkers and managers stop engaging with you
• Why meaningless work may signal a loss of confidence in your performance
• The danger of receiving feedback and doing nothing with it
• How defensiveness makes people stop giving you honest feedback
• Why better feedback has to be earned over time
• How small assignments can become opportunities to rebuild trust
• Why excellence matters even when the work feels beneath you
• How helping overloaded teammates can create your own opportunities
• Why technical skill alone will not make people want to work with you

Actionable Steps:
• Pay attention if meaningful work starts disappearing
• Ask directly for feedback instead of assuming everything is fine
• Receive criticism without immediately explaining or defending yourself
• Ask for specific examples when feedback is unclear
• Take visible action on the feedback you receive
• Follow up later and ask whether your changes are being noticed
• Treat small assignments like they matter, because your execution does
• Look for ways to take work off the plates of overloaded teammates
• Deliver work at a level that makes your effort undeniable
• Rebuild trust through repeated execution, not promises

Who This Episode Is For:
• Early-career engineers unsure whether they are performing well
• Engineers who feel overlooked or underutilized
• ICs who are frustrated by low-value assignments
• Engineers who struggle with defensiveness or feedback
• Anyone who needs to rebuild trust with a manager or team

Why It Matters:
Your career expands when people trust you with more. When that trust starts disappearing, so do meaningful assignments, visibility, responsibility, and growth. You do not rebuild it by demanding better opportunities. You rebuild it by taking ownership, acting on feedback, and demonstrating excellence with whatever is already in front of you.

Where to Listen:
• Spotify
• Apple Podcasts
• Google Podcasts
• Or wherever you get your podcasts

Share:
If this episode hit home, send it to someone. The Impactful Engineer grows by word of mouth, just like the best careers do.

Engineers are trained to analyze, validate, and reduce uncertainty. That becomes a problem when analysis turns into an excuse to delay action. In this episode, Steve and Jake break down two career-defining skills: urgency and agency. For early-career engineers, the order matters. You may not have enough experience yet to make every call confidently, but you can learn to reach a good-enough decision point quickly. Not theory, practical, tactical advice for engineers who want more responsibility, better projects, and faster career growth.

KEY TOPICS COVERED:
• Why urgency and agency are different skills
• Why early-career engineers should build urgency first
• How excessive analysis disguises procrastination
• Why working hard does not automatically mean you are moving fast
• How to recognize when you have enough information to proceed
• Why confidence comes after repeated decision-making experience
• How urgency accelerates learning early in your career
• Why high-agency engineers earn greater responsibility
• How managers evaluate new engineers beyond technical skill
• Why speed and judgment eventually have to work together

ACTIONABLE STEPS:
• Define what "good enough to decide" means before starting analysis
• Ask experienced engineers what information actually matters
• Set a limit on how long you will investigate before making a recommendation
• Separate missing critical information from information that would simply make you more comfortable
• Make a recommendation instead of only presenting data
• Take action once the decision threshold has been reached
• Review your decisions afterward to sharpen future judgment
• Use experienced teammates to shorten your learning curve
• Notice when "I need more information" is really fear of being wrong
• Build urgency now so agency has something to grow from later

WHO THIS EPISODE IS FOR:
• New graduates entering engineering roles
• Early-career engineers who overanalyze decisions
• Engineers frustrated by slow career progression
• ICs who want larger projects and greater responsibility
• Engineers trying to build confidence without pretending they know everything

WHY IT MATTERS:
The engineers who grow fastest are not the ones who somehow eliminate uncertainty. They learn how much certainty is actually necessary. Urgency creates more decisions, more feedback, and more opportunities to learn. Over time, that experience becomes agency. If you want more trust, visibility, and responsibility, you have to learn to move before everything feels perfectly clear.

WHERE TO LISTEN:
Spotify
Apple Podcasts
Google Podcasts
Or wherever you get your podcasts

SHARE:
If this episode hit home, send it to someone. The Impactful Engineer grows by word of mouth, just like the best careers do.

It is easy to explain why you are stuck. A teammate is late. Your team lacks a skill. Someone assembled the product wrong. A competitor has a better network. You never had the internship. In this episode, Steve and Jake break down how engineers turn legitimate constraints into excuses, then show how to flip them into action. Not theory, practical, tactical advice for taking ownership when the obvious answer is to blame someone else.

Key Topics Covered:
• Why excuses feel good now but cost you later
• How to separate a real constraint from surrendered ownership
• What to do when your work depends on someone else delivering first
• How to make progress without doing every task in sequence
• Why poor assembly results may point back to design, training, or instructions
• How leaders create systems that make mistakes harder to make
• Turning skill gaps and resource limits into capacity-building plans
• How to compete when someone else has a stronger network or built-in advantage
• Why discipline can outperform natural talent over time
• How to position nontraditional experience when your resume looks weaker on paper

Actionable Steps:
• Capture the excuse you are using instead of letting it pass unchallenged
• Ask, “What part of this is still under my control?”
• Check dependencies before the deadline, not after they fail
• Ask what can be completed in parallel while you wait
• Build instructions and systems that reduce reliance on perfect execution
• Verify whether people actually have the skills you expect from them
• Create capacity by systemizing work that does not require your direct involvement
• Translate another person’s advantage into a behavior you can reproduce
• Reframe missing experience around the value of what you did instead
• Choose the harder action now when it creates the better outcome later

Who This Episode Is For:
• Engineers who keep getting blocked by other people
• Early-career engineers worried they are already behind
• Technical leaders frustrated by execution mistakes
• Engineers comparing themselves to better-connected or more experienced peers
• Anyone who knows their explanation is becoming an excuse

Why It Matters:
Your career does not move forward because your reasons are valid. It moves forward when you take responsibility for what happens next. The engineers who grow fastest learn to turn constraints into decisions, disadvantages into work, and frustration into action. That is how you build trust, visibility, performance, and leadership capacity.

Where to Listen:
Spotify
Apple Podcasts
Google Podcasts
Or wherever you get your podcasts

If this episode hit home, send it to someone. The Impactful Engineer grows by word of mouth, just like the best careers do.

You will not agree with every decision your boss, client, or business makes. That does not mean every disagreement deserves a fight. In this episode, Steve and Jake break down why strong engineers know when to make the recommendation, accept the decision, and execute. Not theory, practical, tactical advice for protecting your energy, building trust, and becoming someone people want on high-impact work. 

Key Topics Covered:

• Why technically correct does not always mean strategically right
• How to separate a recommendation from the final decision
• Why the customer’s desired outcome can matter more than your preferred optimization
• When cost, capacity, margin, reputation, or peace of mind change the engineering tradeoff
• How unnecessary resistance burns energy without changing the outcome
• Why constant complaining changes how coworkers and leaders perceive you
• How being easy to work with can increase trust and opportunity
• The difference between a real hill to die on and an ego-driven objection
• Why safety, ethics, and legality are valid reasons to stand your ground

Actionable Steps:

• State your recommendation clearly, then let the decision owner decide
• Ask whether your objection changes safety, ethics, legality, or the required outcome
• Stop treating your preferred solution as the only acceptable solution
• Understand what the customer, leader, or business is actually optimizing for
• Execute the chosen direction without dragging resentment into the work
• Stop retelling every frustrating decision to coworkers
• Reclaim the energy you waste trying to prove a decision was wrong
• Make your leader’s life easier when the request is reasonable and responsible
• Build a reputation as someone who can disagree professionally and still deliver

Who This Episode Is For:

• Engineers frustrated by decisions they would not personally make
• Early-career engineers learning how technical work fits business priorities
• High-performing ICs who want more trust, autonomy, and leadership opportunity
• Engineers burning energy fighting battles that do not affect the outcome
• Future leaders learning when to challenge and when to execute

Why It Matters:

Your career is not built only on whether your technical recommendation was correct. People remember whether you brought clarity, judgment, energy, and execution. Fight the issues that truly matter. For everything else, make the recommendation, understand the decision, and get the job done. 

Where to Listen:

• Spotify
• Apple Podcasts
• Google Podcasts
• Or wherever you get your podcasts

Share:

If this episode hit home, send it to someone. The Impactful Engineer grows by word of mouth, just like the best careers do.

Accountability does not start when someone misses a deadline. It starts when the work begins. In this episode, Steve and Jake break down how strong engineers and leaders set clear expectations, document them, follow up before problems become emergencies, and address missed commitments without turning the conversation emotional. Not theory, practical, tactical advice for anyone responsible for getting results through other people. 

Key Topics Covered:

• Why accountability is impossible without clear expectations up front.
• Why important expectations should be written, not left to memory.
• How to anchor deadlines instead of asking, “When can you get this done?”
• Why confirmation matters after assigning actions or changing expectations.
• How early check-ins give you time to recover before a deadline is missed.
• Why responsiveness should be an explicit expectation, especially on fast projects.
• How objective scorecards remove emotion from performance conversations.
• Why criticizing behavior works better than attacking the person.
• How excuses weaken your ability to hold the standard.
• When to develop a struggling vendor, contractor, or teammate and when to move on.

Actionable Steps:

• Define the deliverable, deadline, and communication expectations before work starts.
• Put important expectations in writing and ask the other person to confirm alignment.
• Set required response times for questions, urgent issues, and critical-path decisions.
• Check progress before the deadline, not on the day something is due.
• Ask immediately whether new problems will affect the timeline.
• When an expectation is missed, document what happened without adding emotion or excuses.
• Ask what specifically must change to prevent the same miss from happening again.
• Look for opportunities to recover lost schedule elsewhere in the project.
• Track reliability, responsiveness, urgency, and execution over multiple projects.
• Decide whether someone is willing and capable of meeting your standards before investing more time.

Who This Episode Is For:

• Engineers moving into leadership or project ownership.
• Managers frustrated by repeated missed commitments.
• Engineers coordinating suppliers, vendors, contractors, or cross-functional teams.
• High performers tired of rescuing projects at the last minute.
• Anyone who wants to build a reputation for reliability and execution.

Why It Matters:

Your reputation is built on whether people can trust you to deliver. But leadership also means creating the conditions for others to deliver. Clear expectations, early communication, objective accountability, and the willingness to hold the line give you more control over execution. If you consistently accept missed deadlines, vague communication, and excuses, you are teaching people what you will tolerate. 

Where to Listen:

• Spotify
• Apple Podcasts
• Google Podcasts
• Or wherever you get your podcasts

Share:

If this episode hit home, send it to someone. The Impactful Engineer grows by word of mouth, just like the best careers do.

Leadership changes. Your boss changes. The way your team operates changes. You can waste energy fighting it, or you can learn how to lead through it.

In this episode, Steve and Jake break down how engineers should respond when new leadership arrives and how leaders should approach an established team without destroying what already works. Not theory: practical, tactical advice for navigating uncertainty, earning trust, communicating clearly, and keeping performance moving forward.

Key Topics Covered:
• Why judging a new leader before they have a chance to lead works against you
• How leadership transitions create an opportunity to increase your value and visibility
• Why “that’s how we’ve always done it” is one of the most dangerous mindsets on a team
• How to support a new leader without blindly agreeing with everything
• Why your new leader’s success directly affects your own success
• How good leaders learn before trying to change everything
• Why established team members can become critical sources of context during a transition
• How leaders earn buy-in instead of forcing compliance
• Why managers must translate between their teams and senior leadership
• How communication prevents good judgment calls from destroying trust

Actionable Steps:
• Drop assumptions about a new leader and judge them by what they actually do
• Learn how they communicate, make decisions, and define success
• Ask where you can help stabilize performance during the transition
• Bring forward broken processes instead of defending them out of habit
• Stay open to methods that worked successfully somewhere else
• Give leaders useful context about what has and has not worked before
• If you lead the team, listen before changing systems and expectations
• Identify respected technical leaders and involve them early
• Explain why decisions change when you override or modify someone’s recommendation
• Keep the team focused on the mission, not personal preference

Who This Episode Is For:
• Engineers getting a new manager or executive leader
• ICs frustrated by changes to familiar processes
• New managers inheriting established teams
• Engineers who want more influence during uncertain transitions
• Leaders responsible for maintaining performance while changing direction

Why It Matters:
Change exposes whether you are committed to progress or just comfortable with familiarity. The engineers who grow are not the ones who avoid uncertainty. They communicate, adapt, take ownership, and make themselves more valuable when the environment shifts. Leadership is not waiting until you agree with every decision. It is helping the team move forward when things are changing. 

Where to Listen:
Spotify
Apple Podcasts
Google Podcasts
Or wherever you get your podcasts

Share:
If this episode hit home, send it to someone. The Impactful Engineer grows by word of mouth, just like the best careers do.

Strong technical work does not automatically make you visible, memorable, or promotable. In this episode, Steve and Jake sit down with Vanessa Errecarte, author of Valuable and Visible and an instructor in digital marketing, corporate branding, and personal branding at the UC Davis Graduate School of Management. Vanessa explains how engineers can communicate their value without bragging, build trust through service, and stand out without becoming an online personality. Not theory, practical, tactical advice for making your work easier to understand, remember, and recommend.

Key Topics Covered:
• Why excellent engineers still get overlooked
• The difference between expertise, authority, visibility, and trust
• Why personal branding should serve others instead of promoting yourself
• How to communicate accomplishments without sounding arrogant
• The Truth Framework for creating clear, counterintuitive messages
• Why early-career engineers already have useful lessons to share
• How stories make technical value more relatable and memorable
• Why a focused audience beats meaningless reach and viral impressions
• How personal branding improves meetings, interviews, and leadership conversations
• How resumes and cover letters can break patterns without sacrificing credibility

Actionable Steps:
• Identify the specific person or group you want to help
• Write down what that audience commonly believes
• Define the real problem they may be missing
• Explain what you do differently and why it works
• Support your perspective with evidence, outcomes, or experience
• End every lesson with one action someone can take immediately
• Share one useful thought-leadership post each week
• Turn project experiences into stories about human impact
• Repeat your core message in different ways instead of constantly inventing new ideas
• Build visibility before you need a promotion, interview, or opportunity

Who This Episode Is For:
• Engineers whose work is strong but rarely recognized
• Early-career engineers who believe they have nothing worth sharing
• Individual contributors trying to move into leadership
• Engineers uncomfortable with networking, self-promotion, or personal branding
• Technical professionals whose resumes and interviews sound like everyone else

Why It Matters:
Your career does not grow solely from the quality of your work. People must understand the value you create, associate you with meaningful outcomes, and trust you enough to recommend you. Visibility without value is noise. Value without visibility gets ignored. Learning to communicate both is part of becoming an impactful engineer.

Where to Listen:
Spotify
Apple Podcasts
Google Podcasts
Or wherever you get your podcasts

Share:
If this episode hit home, send it to someone. The Impactful Engineer grows by word of mouth, just like the best careers do.

You can know your project, understand the data, and have the right answer, yet still make leadership doubt you. In this episode, Steve and Jake break down how passive language, hedging, weak tone, and overexplaining destroy credibility. They show you how to communicate decisions, problems, and recommendations with clarity and authority. Not theory. Practical, tactical advice you can use in your next meeting, email, or executive update.

Key Topics Covered:
• Why technically strong engineers plateau because they communicate without confidence
• How phrases like “I think,” “maybe,” and “this might be dumb” weaken your authority
• Why answering with a questioning tone makes leaders doubt your command of the work
• How excessive context buries the decision and exhausts the listener
• Why executives need the conclusion before the supporting explanation
• How concise communication improves trust, visibility, and decision-making
• When detailed context is valuable and when it becomes a distraction
• Why collective intelligence matters more than being the person who knows everything
• How strong communicators advance faster than isolated technical experts
• Why listening closely to the question changes the quality of your response

Actionable Steps:
• Remove unnecessary hedging from your next project update
• State the decision, result, or problem in the first sentence
• Follow your conclusion with no more than two or three supporting bullets
• Put detailed background in an attachment or below a clear summary
• Separate what happened from why it happened
• Answer the exact question before adding context
• Pause after giving the direct answer instead of filling the silence
• Practice replacing passive phrases with clear, factual statements
• Use AI to rewrite your updates in a more assertive executive style, then study the wording
• Review important emails from the recipient’s perspective before sending them

Who This Episode Is For:
• Engineers who know their work but struggle to sound confident
• Individual contributors who feel overlooked despite strong execution
• Technical experts whose careers have started to plateau
• New leaders who need to communicate decisions with authority
• Engineers who overexplain because they want everyone to understand their reasoning

Why It Matters:
Your work cannot create career momentum if people do not trust your delivery. Visibility is not enough. Leadership must hear clarity, ownership, and command when you speak. Strong communication turns technical knowledge into confidence, faster decisions, and greater responsibility. 

Where to Listen:
Spotify
Apple Podcasts
Google Podcasts
Or wherever you get your podcasts

Share:
If this episode hit home, send it to someone. The Impactful Engineer grows by word of mouth, just like the best careers do.