
Insights from recent episode analysis
Audience Interest
Podcast Focus
Publishing Consistency
Platform Reach
Insights are generated by CastFox AI using publicly available data, episode content, and proprietary models.
Most discussed topics
Brands & references
Est. Listeners
Based on iTunes & Spotify (publisher stats).
- Per-Episode Audience
Est. listeners per new episode within ~30 days
25,001 - 50,000 - Monthly Reach
Unique listeners across all episodes (30 days)
25,001 - 75,000 - Active Followers
Loyal subscribers who consistently listen
15,001 - 40,000
Market Insights
Platform Distribution
Reach across major podcast platforms, updated hourly
Total Followers
—
Total Plays
—
Total Reviews
—
* Data sourced directly from platform APIs and aggregated hourly across all major podcast directories.
On the show
From 11 epsHost
Recent guests
Recent episodes
The Fundamentals You Need to Know About AI Coding (Microsoft Trainer)
Apr 29, 2026
47m 29s
AI Engineering Fundamentals You Need to Know To Succeed As Software Engineer (Microsoft Trainer)
Apr 29, 2026
Unknown duration
How to Master Your Skills and Get Hired Without Applying (Terraform Core Contributor)
Apr 22, 2026
37m 49s
Software Expert: This Is How You Design Systems That Survive
Apr 15, 2026
53m 36s
Top Microsoft Advisor: "Coding Is Cheap, Software Is Expensive." You're Focused on the Wrong Thing
Apr 8, 2026
46m 06s
Social Links & Contact
Official channels & resources
Official Website
Login
RSS Feed
Login
| Date | Episode | Topics | Guests | Brands | Places | Keywords | Sponsor | Length | |
|---|---|---|---|---|---|---|---|---|---|
| 4/29/26 | ![]() The Fundamentals You Need to Know About AI Coding (Microsoft Trainer)✨ | AI coding toolsengineering fundamentals+5 | Rob Bos | AI coding toolsLLM+4 | — | AIcoding+6 | — | 47m 29s | |
| 4/29/26 | ![]() AI Engineering Fundamentals You Need to Know To Succeed As Software Engineer (Microsoft Trainer) | Most engineers are using AI coding tools without understanding what they actually are and it's costing them. Microsoft Certified Trainer Rob Bos has trained thousands of engineers on AI tooling, and he sees the same gaps in fundamentals show up again and again, regardless of seniority. This is what you need to know:What an LLM actually is (and why understanding this changes how you use it)Why prompt engineering isn't optionalHow AI magnifies your existing technical debt instead of fixing itThe 6-month learning curve nobody warns you aboutWhy your role as an engineer was never about writing codeThe environmental cost behind every promptWhether you're skeptical of AI tools or already living in agent mode, these are the fundamentals that separate engineers who get real value from those who get burned by the hype.Connect with Rob:https://www.linkedin.com/in/bosrobReferences:Token tracker: https://marketplace.visualstudio.com/items?itemName=RobBos.copilot-token-trackerDev survey: https://www.activestate.com/wp-content/uploads/2019/05/ActiveState-Developer-Survey-2019-Open-Source-Runtime-Pains.pdfTimestamps:00:00:00 - Intro00:00:43 - The #1 Thing Engineers Get Wrong About AI00:02:09 - How Much LLM Theory Do You Actually Need?00:03:58 - Why Pair Programming Is Still the Best Way to Learn AI00:05:26 - Why Rob Skips Tab Completion and Lives in Agent Mode00:07:03 - The "AI Doesn't Increase Productivity" Debate00:08:29 - Why Your Real Job Was Never Writing Code00:09:14 - The 2-Hours-of-Coding Problem No One Talks About00:11:02 - More Code = More Pressure on Your Review Process00:12:21 - Why AI Magnifies Existing Technical Debt00:13:39 - The Customer Who Couldn't Start AI With Developers Yet00:15:11 - The Future Engineer: Reviewer, Not Writer00:17:00 - Convincing the AI Skeptic Who Tried It Years Ago00:19:17 - LLMs Explained Without Visuals (Attention & Semantics)00:22:41 - Why Prompt Engineering Actually Matters00:24:20 - From Zero to Hero: The 6-Month Learning Curve00:26:18 - Is This Confrontational for 20-Year Veterans?00:29:30 - Becoming a Better Engineer by Thinking in Systems00:31:26 - Will AI Stop Working as Innovation Slows?00:34:26 - The Lost Art of Pair Programming with AI00:35:44 - Tribalism in AI Tools (And Why It's Pointless)00:37:33 - Tool Agnostic: Start With the Foundations00:39:40 - Is the IDE Still Relevant?00:40:50 - The Bluescreen Story That Changed His Mind00:41:47 - The Hidden Environmental Cost of AI Coding00:44:15 - 36 Million Tokens in 30 Days: What Does It Mean?00:45:47 - Running LLMs at the Edge to Cut the Footprint00:46:48 - Why You Should Be Allowed to Wait Five Minutes Longer00:47:05 - Outro#githubcopilot #aicoding #softwareengineering | — | ||||||
| 4/22/26 | ![]() How to Master Your Skills and Get Hired Without Applying (Terraform Core Contributor)✨ | open sourcecareer development+3 | Bruno Schaatsbergen | TerraformHashiCorp | — | open source contributionspull request strategies+3 | — | 37m 49s | |
| 4/15/26 | ![]() Software Expert: This Is How You Design Systems That Survive✨ | software designsystem architecture+3 | Nico Krijnen | Peter Naur's Theory Building | — | software engineeringteam composition+3 | — | 53m 36s | |
| 4/8/26 | ![]() Top Microsoft Advisor: "Coding Is Cheap, Software Is Expensive." You're Focused on the Wrong Thing✨ | developer productivityAI adoption+4 | Suzanne Daniels | MicrosoftGitHub | — | coding speeddeveloper productivity+5 | — | 46m 06s | |
| 4/1/26 | ![]() AI Expert: Most Software Engineers Aren't Ready for What's Coming✨ | AIsoftware engineering+4 | Dennis Vink | Xebia | — | software engineerAI+5 | — | 47m 37s | |
| 3/25/26 | ![]() If You've Been At The Same Company 3+ Years, You're Already In A Box✨ | career growthsenior engineers+4 | Ian Miell | Container Solutions | — | career ceiling30% rule+4 | — | 1h 00m 55s | |
| 3/18/26 | ![]() How to Battle Complexity Before It Kills Your Software (30-Year Veteran's Take)✨ | software architecturecoding practices+3 | Dennis Doomen | — | — | software architecturecodebase rot+3 | — | 52m 14s | |
| 3/11/26 | ![]() Uber Engineering Manager on Scaling Systems, Career Trade-offs, and Why Clarity Beats Seniority✨ | system designengineering management+3 | Sendil Nellaiyapen | Uber | — | scaling systemsengineering management+5 | — | 44m 46s | |
| 3/4/26 | ![]() Lead Software Engineer: Why You Can Write the Code in a Day but Ship in a Month✨ | Developer Experiencefuture-proofing+4 | — | — | — | developer experiencesoftware architecture+5 | — | 39m 56s | |
Want analysis for the episodes below?Free for Pro Submit a request, we'll have your selected episodes analyzed within an hour. Free, at no cost to you, for Pro users. | |||||||||
| 2/25/26 | ![]() How Senior Software Engineers Balance Speed and Quality (Scale-Up Lessons)✨ | software engineeringtechnical excellence+4 | Alessandro Mautone | AquabluWeTransfer | — | senior software engineertechnical debt+3 | — | 47m 09s | |
| 2/18/26 | ![]() How to Think About Software Engineering (CTO's Perspective)✨ | software engineeringAI in coding+3 | Joris Conijn | AWSXebia | — | software engineeringAI coding+3 | — | 46m 38s | |
| 2/11/26 | ![]() How to Build the Best Platforms for Software Engineers | Is your internal developer platform actually improving velocity, or is it a bottleneck? We discuss why platform teams building "cool" abstractions is a red flag, and you should aim to create the best platform for software engineers.In this episode, we cover:Why "Golden Paths" can turn into roadblocks for developers.The danger of Shadow IT and why it’s a symptom of a failed platform.How to measure if your platform is saving time.Connect with Adnan Alshar:https://www.linkedin.com/in/adnanmalshar92Connect with Jelmer de Jong:https://www.linkedin.com/in/jelmerdejong-xebia00:00:00 - Intro 00:00:54 - Is DevOps Dead? The Truth About Platform Engineering 00:03:07 - Why Developers Are Drowning in Complexity Today 00:04:37 - Why Having No Platform Is Better Than a Bad Platform 00:07:20 - Treating Software Engineers as Customers of the Platform 00:11:26 - The Exact Moment You Should Start Building a Platform 00:14:18 - Who Should Be on Your First Platform Team? 00:17:33 - Turning Your Angriest Developers Into Platform Evangelists 00:18:57 - Key Metrics: How to Measure Platform Engineering Success 00:21:01 - Why 60% of Companies Don't Measure Platform Success00:23:35 - Why No Metrics Is the Biggest Red Flag00:25:23 - The Disconnect Between Executives and AI Readiness 00:31:34 - Integrating AI Tools and Large Language Models Securely 00:34:22 - Shadow IT: The Symptom of a Broken Platform 00:38:03 - How to Scale Without Becoming a Bottleneck 00:41:45 - Don’t Forget the Business Side of Platform Engineering#PlatformEngineering #DevOps #DeveloperProductivity | — | ||||||
| 2/4/26 | ![]() Career Advice I'd Give Every Software Engineer Right Now | Engineering hasn't become easier, writing code has just become faster. Time to stop fighting symptoms and start thinking in systems. In this Q&A, I break down the career advice I'd give to any engineer, from mastering architecture to knowing when to quit a high-paying job.In this episode, we cover:How "Systems Thinking" can be applied in practiceThe "Golden Handcuffs": Why high salaries keep engineers in toxic jobsHow to transition into leadership without waiting for a titleTimestamps00:00:00 - Intro 00:00:58 - How to innovate in stubborn legacy companies 00:04:49 - The "Golden Handcuffs": Money vs. Mental Health 00:07:27 - Stop solving symptoms: Systems Thinking explained 00:13:10 - Transitioning from Senior Engineer to Solutions Architect 00:15:08 - Communicating technical risks to non-technical bosses 00:17:48 - Proving leadership before you have the title 00:22:25 - My strategy for dealing with Imposter Syndrome 00:26:12 - Creating a "Zettelkasten" to retain technical knowledge 00:29:12 - The mindset that makes me stress-proof at work 00:33:10 - Learning to code with a product/design background 00:38:40 - Working with international remote teams 00:40:35 - Career Pivot: Software Engineering to Cyber Security 00:43:20 - Solopreneur opportunities in the "Education Gold Rush" 00:51:50 - Future Predictions: Vibe Coding vs. Vibe Engineering#SoftwareEngineering #CareerAdvice #SystemsThinking | — | ||||||
| 1/28/26 | ![]() The Skills That Matter When AI Writes Your Code | The software engineering landscape is shifting rapidly. Coding is becoming "cheap" because of tools like Claude Code, Codex, Gemini, Cursor etc. Interviews are evolving to focus on system design over syntax. In this Q&A, I break down exactly which skills matter now, how to negotiate the salary you deserve, and how to deal with difficult personalities on your team.In this episode:How juniors can leverage AI tools to reach senior-level outputReal-world salary negotiation tactics from my experienceWhy coding skills matter less in modern interviews (and what matters more)Handling "brilliant jerks" and toxic team cultureWhether you are looking for your first job with no experience or you are a mid-level dev trying to break into a Staff Engineer role, this session is packed with actionable career advice.Timestamps: 00:00:00 - Intro 00:01:06 - Handling Brilliant Jerks: Toxic Culture vs. High Performance 00:04:13 - How Juniors Can Use AI to Outperform Seniors 00:07:10 - The Future of Coding Interviews: System Design and AI 00:11:20 - The Real Difference Between Good and Great Developers 00:13:00 - One Mistake Mid-Level Developers Make That Stalls Growth 00:15:58 - Salary Negotiation Tactics: How I Got Two Raises in One Year 00:23:44 - Questions You Should Ask to Crush Your Tech Interview 00:27:42 - What Actually Moves the Needle: Side Projects vs. Experience 00:31:05 - Don't Wait for a Perfect Portfolio to Start Applying 00:32:25 - Finding Jobs: Why LinkedIn and Meetups Beat Job Boards 00:35:16 - Should Frontend Developers Worry About Learning Backend Skills? 00:37:39 - Do Tech Certifications Actually Help You Get Hired? 00:39:07 - Mastering Soft Skills: Training Budgets vs. Real Experience#softwareengineering #careeradvice #techinterviews | — | ||||||
| 1/21/26 | ![]() Google & AWS Veteran: How To Become a Great Software Architect | "Architects shouldn't try to be the smartest people in the room, they should make everybody else smarter."In this episode, Gregor Hohpe (ex-Google & AWS, author of "The Software Architect Elevator") breaks down exactly how to transition from software engineer to architect. He shares the mental models used at Big Tech to handle complexity, visualize systems, and navigate office politics without losing your technical edge.We cover:- Why "lowering risk" is the architect's real value proposition- The "Phantom Sketch Artist" technique to visualize unclear requirements- How to gain "political capital" to push back on bad decisions- Why simple architectures are often the hardest to buildIf you want to move beyond just writing code and start designing systems that scale, this conversation is for you.Connect with Gregor:https://www.linkedin.com/in/ghohpe00:00:00 - Intro 00:01:15 - How to Spot Bad Architects vs. Great Amplifiers 00:03:44 - Why Architects Are Actually Risk Managers in Disguise 00:06:13 - The Truth About Complexity and Simplicity at Scale 00:09:55 - How to Resolve Technical Disagreements Without Arguments 00:13:57 - Why You Should Use Pen and Paper for Architecture 00:17:24 - Mastering the Left-Right Brain Ping Pong Technique 00:20:42 - The "Architect Elevator": Connecting Code to Strategy 00:23:06 - The Rubber Duck Test: Are You a Good Architect? 00:25:41 - The "Phantom Sketch Artist" Method for System Design 00:30:37 - Stop Being a Cartographer, Start Being a Scout 00:34:47 - How to Keep Your Technical Skills Sharp as an Architect 00:44:37 - Navigating Office Politics using the "Court Jester" Strategy 00:48:08 - How to Earn and Spend Political Capital Wisely 00:53:17 - Why the "Big Ball of Mud" Might Be a Good Architecture 00:57:08 - How Executives Spot Gaps in Your Technical Logic 01:00:00 - Why Using AI for Architecture is a Dangerous Trap#SoftwareArchitecture #SystemDesign #SeniorDeveloper | — | ||||||
| 1/14/26 | ![]() Own Your Engineering Career (No One Else Will) | Are you waiting for a promotion that never comes? In this episode, we break down why relying on your manager to define your growth is a career-limiting mistake and how you can take full ownership of your professional path.In this episode, we cover: Why hard skills get you hired but won't get you aheadHow to create growth opportunities when your company has no clear pathUsing RACI to own decisions and increase your visibilityConnect with Zanina:https://www.linkedin.com/in/zaninakatiraReferences: RACI - https://en.wikipedia.org/wiki/Responsibility_assignment_matrixTimestamps:00:00:00 - Intro 00:00:51 - Why hard skills get you hired but soft skills make you thrive 00:04:17 - How to connect your code to actual business results 00:06:44 - The art of storytelling for technical professionals 00:09:16 - Balancing execution speed with team collaboration 00:11:57 - The problem with forcing engineers into management roles 00:15:13 - Surviving when technology outgrows your current skillset 00:17:59 - Using the RACI method to clarify ownership and decisions 00:21:23 - What to do when your manager has no answers for your growth 00:24:40 - Why you should value scope of work over job titles 00:28:39 - How to pitch and negotiate impactful projects to leadership 00:33:00 - Expanding your perspective by networking outside your team 00:35:35 - Visualizing your ambition and defining what success looks like 00:39:16 - Overcoming the fear of asking for constructive feedback#careergrowth #softwareengineering #softskills | — | ||||||
| 1/7/26 | ![]() The AI Skills Software Engineers Need to Learn Now | Software engineers often think adding AI is just a simple API call, but moving from a Proof of Concept to a stable production system requires a completely different mindset. Maria Vechtomova breaks down the harsh reality of MLOps, why rigorous evaluation is non-negotiable, and why autonomous agents are riskier than you think.In this episode, we cover:The essential MLOps principles every software engineer must learnHow to bridge the gap between a demo and a production-grade solutionStrategies for evaluating agents and detecting model driftThe security risks of customer service agents and prompt injectionPractical tips for using AI tools to boost your own productivityConnect with Maria:https://www.linkedin.com/in/maria-vechtomovaTimestamps: 00:00:00 - Intro 00:01:25 - Why the AI Hype Was Actually Good for Monitoring 00:03:07 - Real-World AI Use Cases That Deliver Actual Value 00:05:16 - MLOps Basics Every Software Engineer Needs to Know 00:08:08 - The Hidden Complexity of Deploying Agents to Production 00:12:02 - Minimum Requirements for Moving from PoC to Production 00:15:41 - Step-by-Step Guide to Evaluating AI Features Before Launch 00:18:08 - How to Handle Data Labeling and Drift Detection 00:21:55 - Why You Likely Need Custom Tools for Monitoring 00:24:56 - Why Engineers Build AI Features They Don't Need00:26:01 - How Software Engineers Can Learn Data Science Principles 00:31:36 - The Dangerous Security Risks of Autonomous Customer Service Agents 00:34:44 - Why Human-in-the-Loop is Essential for Avoiding Reputational Damage 00:36:18 - Boosting Developer Productivity with Opinionated AI Prompts 00:39:20 - Using Voice Notes and AI to Organize Your Life#MLOps #SoftwareEngineering #ArtificialIntelligence | — | ||||||
| 12/31/25 | ![]() Why Mediocre Engineers Get Promoted Over Great Ones (CEO Explains) | Are your technical skills actually holding your career back? In this conversation with Anand Sahay, Global CEO of Xebia, we explore the controversial reality that "mediocre" engineers often climb the corporate ladder faster than technical wizards. And what you need to do to change that trajectory.In this episode, we cover:Why simplicity and business value beat complex code every timeThe specific mindset shift required to move from Senior Engineer to ExecutiveHow to maintain technical intuition and manage risk without micromanagingThe hidden arrogance that stops great engineers from becoming great leadersThis discussion is essential for software engineers, architects, and technical managers who want to break through the "tech ceiling" and understand how decisions are really made at the top.Connect with Anand:https://www.linkedin.com/in/ansahayTimestamps:00:00:00 - Intro 00:01:28 - How to Pitch to Executives (And Not Get Rejected) 00:03:42 - The #1 Trait of Elite Engineering Leaders 00:06:15 - Why AI Answers Destroy Your Credibility 00:10:11 - Why Mediocre Engineers Get Promoted Over Great Ones 00:14:15 - The Truth About the "Individual Contributor" Track 00:16:16 - The Arrogance Trap: Why Devs Fail at Business 00:22:08 - Stop Being a "One Man Army" (Unless You Do This) 00:25:32 - From Developer to CEO: The Uncommon Path 00:29:07 - Why Most Engineering Teams Are Structured Wrong 00:32:17 - How to Spot a Toxic Tech Culture 00:34:44 - Will AI Replace Senior Engineers? 00:38:40 - Maintaining Technical Intuition Without Coding Daily 00:41:53 - When to Approve "Bad" Ideas for Team Morale 00:48:41 - The "Hard Part First" Rule for Innovation#SoftwareEngineering #TechLeadership #CareerGrowth | — | ||||||
| 12/24/25 | ![]() How to Build Skills That Outlast Any Tool (From Data Analyst to AI Lead) | Tools change and frameworks die, but your career doesn't have to. Marijn Markus joins the show to explain why "Don't be a fool with a tool" is the single most important piece of advice for modern software engineers and data professionals.In this episode, we cover:The "Meta-Skill" of learning how to learn new technologiesWhy real innovation often originates in "dark" industries like crime and warfareHow to future-proof your career against AI agents and automationWhy understanding the business problem is more valuable than writing the codeThis conversation is essential for engineers who want to move from memorizing syntax to mastering the skills that actually last.Connect with Marijn Markus:https://www.linkedin.com/in/marijnmarkusTimestamps:00:00:00 - Intro00:01:01 - Realizing That Data Science Can Actually Save Lives00:04:36 - Predicting Refugee Movements With Hamburger Prices00:07:05 - Why You Should Try Different Roles Early in Your Career00:12:37 - Learning in Banking to Eventually Help Non-Profits00:15:38 - Why Certifications Are Compensation for Lack of Experience00:18:36 - The Single Most Important Skill in the Tech Field00:21:39 - "If They Understood the Problem, They Wouldn't Hire You"00:25:48 - Why Innovation Comes From War, Crime, and Adult Industries00:31:16 - The Danger of AI Agents and Automated Social Engineering00:35:03 - Focus on Skills That Do Not Have Expiration Dates00:39:47 - How to Navigate Truth in the Era of Deepfakes00:41:30 - Don't Be a Fool With a Tool (The Selenium Trap)00:45:25 - Rising Above the Tools to Become an Expert#SoftwareEngineering #CareerAdvice #Technology | — | ||||||
| 12/17/25 | ![]() Why Coding Skills Won’t Get You To Staff Engineer | Are you just executing tickets, or are you driving business impact?In this episode, Praveen Murugesan (VP of Engineering at Samsara) breaks down why the best engineers don't just write code and why "coding skills" alone won't get you there.He explains the critical shift from "software engineer" to "product engineer," why you shouldn't wait for permission to solve problems, and how to de-risk high-stakes projects like a true owner.In this episode, we cover:The difference between a "Ticket Taker" and a Product Engineer Why Product Managers should NOT be doing project management How to grow to Staff Engineer without managing a large team The exact interview questions to ask to test a company’s culture A real story of an engineer telling a VP: "That's not an important problem"Connect with Praveen Murugesan:https://www.linkedin.com/in/praveenmurugesanTimestamps: 00:00:00 - Intro 00:01:55 - Product Engineer vs. Software Engineer: What’s the Difference? 00:06:20 - Why Product Managers Should Not Do Project Management 00:11:06 - The Danger of "Flying Blind" Without Business Context 00:15:24 - Why Curiosity Is the Ultimate Leverage in the AI Era 00:25:06 - Why the Best Ideas Must Win Regardless of Hierarchy 00:27:43 - The #1 Interview Question to Test for Engineering Ownership 00:32:12 - How to Test a Company’s Culture Before You Join 00:36:04 - Why You Don't Need to Be Senior to Be a Product Engineer 00:40:46 - Managing High-Stakes Projects and De-risking Failure 00:43:56 - What I Learned From Breaking Production at Salesforce 00:48:29 - The Myth About Staff Engineering and Managing Teams 00:51:59 - The Engineer Who Told the VP: "That's Not an Important Problem"#SoftwareEngineering #StaffEngineer #CareerGrowth | — | ||||||
| 12/10/25 | ![]() Forward Deployed Engineer: The Role Up 800% (And How to Get It) | Traditional software engineering job listings have dropped by 70%, yet Forward Deployed Engineer (FDE) roles have exploded by over 800% this year. We sit down with Mo Fagir, Principal Technical Consultant at ServiceNow, to break down exactly why this shift is happening and how you can pivot your career to ride this AI adoption wave.In this episode, we cover:The massive market shift: Why "pure coding" jobs are declining while FDEs are booming.The exact technical stack and soft skills required to land these high-paying roles.How to overcome imposter syndrome and build a portfolio that gets you hired, even as a junior.Why this isn't just a trend, but the future of how engineering delivers value.Connect with Mo Fagir:https://www.linkedin.com/in/mo-nour-tarigTimestamps:00:00:00 - Intro00:01:14 - Why software jobs dropped 70% while FDEs grew over 800%00:02:55 - Why companies can't implement AI without Forward Deployed Engineers00:05:36 - Is this career path safe for traditional software engineers?00:07:54 - The exact technical stack you need to master today00:10:48 - Moving from engineering scope to product centric thinking00:16:15 - Can juniors and early career devs get hired as FDEs?00:19:12 - How to build a portfolio that gets you hired00:22:17 - Why passion and attitude beat experience in the AI era00:24:33 - How to train yourself to have a sense of urgency00:29:05 - Can introverts succeed in client facing engineering roles?00:32:17 - Lessons learned from interning at NASA and researching AI00:35:09 - Are we in an AI bubble that will burst soon?00:40:34 - Does becoming an FDE risk vendor lock-in for your career?00:43:36 - Final advice for engineers entering the 2025 job market#ForwardDeployedEngineer #FDE #SoftwareCareers | — | ||||||
| 12/3/25 | ![]() AI Won't Replace Software Engineers, But This Might (CEO Perspective) | If you think your value as a software engineer comes just from writing code, you're already at risk.In this episode, Outsystems CEO Woodson Martin reveals why AI isn't the real threat to your career. Irrelevance is. He explains that writing code is now only 20% of the job, and the engineers who thrive are the ones who master the other "80% that matters."We cover:The billions of lines of ungoverned code AI is creatingWhy the "Forward Deployed Engineer" model is changing team structuresThe 80% of engineering work that AI cannot replaceHow to shift from coder to problem solver who drives business revenueA CEO's advice for building a lasting engineering careerThis is a reality check for developers, tech leads, and architects who want to stay relevant as agentic AI reshapes the industry.Connect with Woodson:https://www.linkedin.com/in/woodsonmartinTimestamps:00:00:00 - Intro00:00:56 - How Agentic AI keeps the human in the loop00:01:55 - Real-world example: Automating the grunt work00:04:17 - How engineers are using agents internally00:05:52 - Blending Low-Code and High-Code for complex systems00:08:28 - Is a Low-Code career a trap for engineers?00:10:50 - Will AI make software engineering obsolete?00:12:09 - The 80/20 Rule: Why code is only 20% of your job00:13:14 - Layoffs vs. the rise of the solo entrepreneur00:15:18 - Career advice for a volatile tech market00:17:02 - How to retain top talent and keep them happy00:20:10 - Why we radically changed our engineering team structure00:24:33 - The "Forward Deployed Engineer" model explained00:27:08 - Outsystems vs. OpenAI: The future of platform building00:31:45 - The tech debt problem no one's talking about00:34:23 - The one thing that keeps you from becoming irrelevant#SoftwareEngineering #CareerAdvice #AIAgents | — | ||||||
| 11/26/25 | ![]() How We Get More Done with Fewer Engineers | What if you could build a multi-million dollar software company where only 10% of your employees are developers? AFAS, a company with hundreds of millions in revenue, does exactly that with a lean team of just 70 engineers. In this episode, Engineering Manager Michiel Overeem pulls back the curtain on their unconventional strategies for achieving massive productivity with a surprisingly small team.In this episode, we cover:Why standardization is their secret weapon for efficiency.How they thrive without traditional Scrum ceremonies.The two distinct types of engineers they hire for success.The surprising details of their 4-day work week (paid for 5).This video is for engineering leaders and software developers who want to learn proven, counter-intuitive strategies to build hyper-effective teams and get more done, regardless of team size.Connect with Michiel:https://www.linkedin.com/in/movereemTimestamps:00:00:00 - Intro00:01:22 - The "10% Engineering" Paradox at a €100M+ Company00:03:20 - How Standardization Allows a Small Team to Do More00:04:27 - The Two Types of Engineers Every Successful Company Needs00:06:46 - Why Feeling Responsible is More Powerful Than Being Responsible00:09:33 - The Secret Sauce of High-Performing Engineering Teams00:11:52 - A Simple Method to Keep Engineers Connected to Customers00:14:22 - What We Look For When Hiring New Engineers00:17:09 - The #1 Red Flag That Will Get You Rejected in an Interview00:19:33 - Why We Don't Use Scrum (And What We Do Instead)00:22:51 - The Power of Strong, Decisive Leadership00:24:13 - How Our 4-Day Work Week Actually Works00:26:55 - Our Approach to Adopting AI Tools like Copilot00:28:19 - Final Advice: The Best Way to Grow Your Career#EngineeringCulture #Productivity #SoftwareDevelopment | — | ||||||
| 11/19/25 | ![]() GitHub Senior Engineer: How to Think About System Design | System design interviews often focus on theoretical complexity, but how do Senior Engineers at GitHub actually approach scaling? In this episode, Bassem Dghaidi breaks down how to think about system design when real business impact is on the line.We discuss why "simple is complicated enough," the dangers of premature scaling, and why vertical scaling often beats complex distributed systems. If you want to bridge the gap between theory and practice, and understand how to design software that actually serves the business, this conversation is for you.In this episode, we cover:- The "Order of Magnitude" rule for scaling systems- Why GitHub often runs millions of requests on simple architecture- How to communicate technical constraints to non-technical stakeholders- Why 90% of Bassem's code is now written by AI agentsConnect with Bassem Dghaidi:https://www.linkedin.com/in/bassemdghaidyTimestamps:00:00:00 - Intro00:00:48 - Theory vs. Practice in System Design00:02:06 - The Startup That Almost Failed via Kubernetes00:03:33 - How GitHub Scales (It's Simpler Than You Think)00:05:20 - The Underrated Power of Vertical Scaling00:08:23 - Why Big Tech Interviews for Scale You Don't Need Yet00:10:39 - Software Evolves, It Isn't Just "Built"00:11:53 - Only Design for the Next Order of Magnitude00:15:39 - Stop Building Generic Frameworks00:18:17 - "Hacking" the System Design Interview00:21:29 - Translating Tech Problems to Business Risks00:27:37 - Layoffs & Engineering Efficiency00:29:41 - Proving Your Impact with Numbers00:31:00 - Professional Engineering vs. Hobby Coding00:32:19 - "Simple is Complicated Enough"00:35:03 - The Rise of AI Coding (The Motorcycle Analogy)00:37:30 - "90% of My Code is Written by AI Agents"00:41:04 - How to Become a Great Engineer#SystemDesign #SoftwareEngineering #GitHub | — | ||||||
Showing 25 of 249
Sponsor Intelligence
Sign in to see which brands sponsor this podcast, their ad offers, and promo codes.
Chart Positions
4 placements across 4 markets.
Chart Positions
4 placements across 4 markets.
























