Hosted by Unknown Host · 🇺🇸 US · EN · 23 episodes
Established thought leaders with verified media credentials.
Re:Engineered is a podcast for engineers and technical professionals who've realized that being great at the technical work isn't enough anymore. Hosted by Chris Stasiuk, an engineer turned coach who spent 25 years growing from project engineer to shareholder at an engineering consulting firm, and now coaches technical professionals on the leadership skills no one taught them. The show treats communication, leadership, and influence as systems. Not personality traits. Not corporate theater. Skills you can learn and apply without pretending to be someone you're not. Episodes include solo takes, newsletter riffs, and conversations with engineers and experts in areas technical professionals often overlook. No theory. Real frameworks from real engineering environments, with direct guidance on managing up, leading without authority, and navigating difficult conversations. No buzzwords. No corporate platitudes. No advice from consultants who've never built anything. If you're the one who actually solves the problems but keep getting passed over for people who talk more than they contribute, this podcast was built for you. Because being a great engineer isn't enough anymore.
Unknown Host hosts Re:Engineered, a business show with 23 episodes published.
Engineering judgment gets treated as something mysterious. A gift. Something senior engineers have and junior ones don’t, with no clear path between them. That framing is convenient for the senior engineers and useless f
Show notesMost engineers stepping into leadership have the credentials. The degree, the certification, the years on the job. What they don’t have yet is earned credibility, and that gap is real whether they acknowledge it or not.
Show notesEngineers think they have a communication problem. They have a system problem. Every individual communication failure compounds into a predictive model that other people run of you, and that model is what gets used in ro
Show notesEngineers don’t fail in high-stakes rooms because their analysis is wrong. They fail because they’re answering in the wrong unit. A project manager walks a client through a scope change in hours; the client asks for doll
Show notesEngineers don't lie about what they don't know. They go quiet. That instinct is correct in technical work, where you don't sign off on a calc you haven't verified. It backfires in leadership, where silence isn't neutral
Show notesEngineers operate on a transmission model. You send, therefore you’ve communicated. But communication with people who have to act on the information isn’t a transmission. It’s a confirmed receipt. Chris breaks down a six
Show notesEngineers default to comprehensiveness because leaving something out feels wrong. In a design review or on a set of drawings, that instinct is correct. In leadership, it backfires. The person asking the question usually
Show notesEngineers can have every leadership mechanic in place and still be invisible to the people who matter. The problem isn’t the quality of work. It’s an undesigned signal path between that work and the people making decisio
Show notesEngineers treat conflict like a system fault — find the root cause, fix it, restore steady state. In human systems, that instinct doesn’t resolve conflict. It suppresses it, and suppressed conflict doesn’t disappear. It
Show notesEngineers trying to influence peers, contractors, and cross-functional teams face a total authority gap — and they handle it badly. The default moves are logic and persuasion, which creates resistance, or avoidance, whic
Show notesMost engineers are deliberate about the signal they send downward and sideways. The upward signal gets left to chance — not because it seems unimportant, but because “managing up” sounds like politics. This episode refra
Show notesMost engineers apply the same level of analytical rigor to every decision regardless of what it actually requires. That’s not thoroughness — it’s a mismatch, and it signals to everyone watching that you don’t trust the t
Show notesMost engineers stepping into leadership already know what they should do differently. This episode is about why they don’t do it consistently — and it’s not a discipline problem. The solve-it reflex persists because iden
Show notesEngineers don’t avoid performance conversations because they’re conflict-averse. They avoid them because they misclassify them as irreversible. They wait until the pattern is undeniable, the evidence is airtight, and the
Show notesMost engineers trying to create alignment are optimizing the output without understanding the inputs. This episode breaks influence down as a system with three inputs: sequencing context before conclusions, lowering the
Show notesIn this conversation, Chris Stasiuk explores the challenges engineers face when transitioning into leadership roles, particularly the pitfalls of over-relying on logic. He emphasizes that while correctness is crucial in
Show notesIn this episode, Chris Stasiuk discusses the challenges engineers face when transitioning into leadership roles, particularly around decision-making. He introduces the concept of 'decision stall,' where leaders hesitate
Show notesSummary In this conversation, Chris Stasiuk explores the transition from engineering to leadership, highlighting the fundamental differences in mindset and approach required. He discusses how engineers often struggle wit
Show notesSummary In this episode, Chris Stasiuk explores the transition engineers face when stepping into leadership roles, highlighting the common feelings of uncertainty and self-doubt that arise. He emphasizes the distinction
Show notesThis conversation explores the challenges engineers face when performance becomes the primary strategy, leading to feelings of frustration and misalignment. It discusses how engineers often rationalize staying in roles t
Show notesSponsor detection runs nightly. Check back soon.
No public pitch examples yet for this show.
Generate your own personalised pitchBased on semantic analysis of episode topics and host coverage, this show is a strong guest fit for executives in:
Industry fit is computed by PitchCentric using vector embeddings of the show's episode catalog.
Shows with the most semantically similar episode content. Pitch one, pitch all; producers cluster.
To pitch Re:Engineered, visit https://chrisstasiuk.com/podcast for contact information, then craft a tight one-paragraph hook that ties your expertise to a gap in their recent business coverage.
Re:Engineered is hosted by Unknown Host. The show is categorised under Business (careers) and has published 23 episodes.
Re:Engineered has published 23 episodes.
Re:Engineered regularly covers Business, Careers. It sits in the Business category, with a careers focus.
Re:Engineered is accessible for guests with genuine business expertise. A personalised, episode-aware pitch will still outperform a generic one every time.
Re:Engineered hasn't explicitly signalled guest openness in recent episodes. That doesn't rule out pitching. your hook just needs to be especially compelling and relevant to their recent content.
Episodes of Re:Engineered average 8 minutes. a focused format where a clear narrative arc and tight preparation matter most.
Our data rates Re:Engineered's guest bar at 81/100 (Premium tier). Established thought leaders with verified media credentials. Sign in to PitchCentric to see how your own Pod Score compares against this show.
Methodology. Booking Probability™ blends Listen Score, 30-day Virality, open-to-guests detection, and Apple ratings. Data refreshed every 60 minutes. Listen Score and Booking Probability are calculated by PitchCentric. Last enriched 5 days ago.
