
Advertise on podcast: Beyond Coding
Rating
5from
This podcast has
277 episodes
Language
EnglishPublisher
Patrick AkilExplicit
No
Date created
2021/06/15
Latest episode
2026/11/18
Average duration
45 min.
Release period
7 days
Description
For software engineers ready to level up. Learn from CTOs, principal engineers, and tech leaders about the skills beyond coding: from technical mastery to product thinking and career growth. Created by Patrick Akil
Unlock Beyond Coding podcast Email contact info,
Listeners & Audience details
Email contact information
Direct podcast contact details

Listeners
Audience numbers & engagement insights

Audience details
Podcast Insights

Podcast episodes
Check latest episodes from Beyond Coding podcast
Platform Architect: What Engineers Need to Know About Kubernetes
2026/11/18
Platform architect Thomas Schuetz explains how much Kubernetes engineers need to know. In his experience the software itself rarely broke: most of the problems he hit were ones he caused himself. We also talk about automating infrastructure end to end and building internal platforms without trapping developers in a golden cage.
In this video, we cover:
How much Kubernetes software engineers need to know when a container can run anywhereCloud native first principles: automate everything, tear down and rebuild clusters, and let only automation touch the clusterHome labs and offloading AI coding agents from your laptopPaved roads vs. golden cages: developer experience and agent experience with APIs and MCP serversBuilding platforms from the applications down, and fixing platform pain through pull requestsThis episode is for software engineers who deploy on a platform every day and want to understand what sits underneath it, and for platform engineers who want developers to choose their platform.
Timestamps:00:00:00 - Intro00:00:45 - Why His Home Lab Now Runs 24/700:01:48 - Teaching Kubernetes: Students vs Skeptical Companies00:03:10 - Running AI Coding Agents in Sandboxes and Home Labs00:05:05 - The #1 Cloud Native Rule: Automate Everything00:07:30 - Tearing Down and Rebuilding Clusters Every Day00:09:10 - Why Kubernetes Rarely Broke for Him00:10:14 - How Much Kubernetes Should Software Engineers Know?00:12:53 - Why People Think Kubernetes Is Too Complex00:15:29 - How to Learn Kubernetes Without Getting Overwhelmed00:17:37 - Handling the Pressure of Infrastructure at Scale00:19:59 - When a Golden Path Becomes a Golden Cage00:25:43 - Designing Platforms for AI Agents With APIs and MCP00:27:54 - Build Platforms From Applications, Not the Tool Landscape00:32:05 - Will AI Agents Turn Every Developer Into an Architect?00:35:29 - Platform Pain? Open a Pull Request
Guest: Thomas Schuetz, Cloud Native Architecthttps://www.linkedin.com/in/thschue
#Kubernetes #PlatformEngineering #SoftwareEngineering
What Coding Agents Need From Engineers to Be Trusted
2026/11/11
What do coding agents need from engineers to be trusted? AI consultant Fausto Albers builds production software with agents and doesn't believe anyone still reads the code line by line. Here is what he relies on instead.
We cover:
Why newer models are "eating the harness", and the shift from context engineering to loop engineeringThe state a coding agent should be in before it runs for hours, and the gates its output has to passObservability with open-source MLflow when you can't read every traceA shared ontology and a three-layer memory stack: a Karpathy-style Markdown wiki in Obsidian, graph memory and a local vector database in DockerDisposable vs durable software, and why software built by intent threatens traditional SaaSWhy AI makes attacks cheaper than defenseThis episode is for software engineers and tech leads who want to give coding agents real autonomy without giving up responsibility for what gets built.
Timestamps:
00:00:00 - Intro
00:00:49 - Why Newer Models Keep Eating the Harness
00:02:26 - Will SaaS Survive the Next Ten Years?
00:03:39 - From Sociology to Cocktail Bartender to Restaurant Owner
00:07:19 - Why Human Preference Can't Be Reduced to Data
00:10:10 - What I Learned From a Failed Restaurant Chatbot
00:14:16 - Learning Faster With AI and Who Gets Left Behind
00:18:38 - What State Should Your Coding Agent Be In?
00:22:09 - Building a Shared Understanding Before Kicking Off a Loop
00:26:58 - Why Nobody Really Reads AI Code Line by Line
00:31:34 - The Real Reason Engineers Push Back on AI
00:33:48 - Sloppy, Disposable or Durable: How to Judge Code
00:35:18 - A Three-Layer Memory System for Coding Agents
00:39:44 - Why Domain Experts Matter When Execution Gets Cheap
00:42:23 - How AI Makes Attacks Cheaper Than Defense
Guest: Fausto Albers, AI consultant at Wonder Why
https://www.linkedin.com/in/stepintoliquid
#codingagents #softwareengineering #aiagents
The Most Future-Proof Engineering Skill Nobody Wants to Learn
2026/11/04
What is the most future-proof engineering skill to learn now with AI and Coding agents? Time is up for traditional development cycles as Agents shrink vulnerability exploit windows from 200 days to just 18 hours.
In this video, IBM HashiCorp Field CTO Anna McDougall shares why brilliant engineers have been avoiding the single most resilient career path in tech and how it's time to change that. It's now part of what software engineering is becoming:
Why 20% of software engineers are grieving hands-on IDE coding (and why manual code is becoming like carpentry)The #1 future-proof engineering specialty that protects your career as AI agents write more codeHow to stand out in interviews using the "Pumpkin" CV strategy, high-signal personal achievements, and human networkingWhy non-deterministic coding agents ignore skills.md files and why 88% of breaches come down to credentialsHow engineering leaders can implement deterministic runtime guardrails, workload identity, and scoped credentials at scaleWhether you are looking to future-proof your career or a software engineer navigating agentic workflows, you will walk away with a clear roadmap for what comes next.
This episode was recorded at TechLead Conference. Join for the next edition of the event in Amsterdam on May 20: https://techleadconf.com
Guest - Anna Mcdougall:https://www.linkedin.com/in/annajmcdougall
Timestamps:00:00:00 - From 200 Days to 18 Hours: Why Time Is Up00:00:47 - What a Field CTO Actually Does Every Day00:03:53 - Why 20% of Engineers Are Grieving Hands-On Coding00:06:55 - Why Hand-Crafted Code Is Becoming Like Carpentry00:08:26 - The Most Future-Proof Engineering Skill Nobody Wants00:10:53 - How to Network by Becoming the Connective Tissue00:13:55 - How to Stand Out When AI Writes Every Resume00:18:31 - The "Pumpkin" Strategy to Be Remembered in Interviews00:22:25 - Why Brilliant Engineers Avoid This Career Path00:26:42 - Why Skills Files Are Not Enough for Coding Agents00:31:10 - Building Deterministic Guardrails Without Slowing Teams00:36:32 - Finding Your People in Engineering Leadership
#SoftwareEngineering #CareerAdvice #AIEngineering
Meta Staff Engineer: What the Best Engineers Do Differently
2026/10/28
Meta Staff Engineer Sajal Rustagi reveals what Staff Engineers do that most don't and what the best engineers do differently to reach the top. While foundational behaviors like proactivity and ownership still separate growing engineers from stuck ones, leveling up today requires a completely new set of staff skills built around agents.
In this video, we cover:
The behavioral shift from IC4 and IC5 (Senior) to IC6 (Staff Engineer) at MetaHow top engineers treat on-call firefighting as a system-wide ownership opportunityWhy rotating between Engineering Manager (EM) and Staff IC sharpens your business and technical influenceTransitioning from Developer Experience (DX) to Agent Experience (AX) using MCP, Claude, and markdown contextThis conversation is for software engineers, senior ICs, and tech leads who want to learn the new staff skills required to multiply their impact and get promoted now.
This episode was recorded at TechLead Conference, a conference for engineering leaders on adopting AI.
Timestamps:
00:00:00 - The New Staff Engineer Skills
00:00:44 - 2 Behaviors That Separate Mediocre and Staff Engineers
00:02:16 - How the Best Engineers Build an Ownership Mindset
00:04:26 - What Staff Engineers Do Differently During On-Call
00:06:26 - Senior vs. Staff Engineer: Expanding Your Sphere of Influence
00:09:56 - Why Switching Between Manager and Staff IC Builds Better Engineers
00:14:04 - Why Unblocking Engineers Now Means Unblocking Agents
00:16:41 - Managing Multi-Agent Handoffs Without Losing Control
00:19:02 - Shifting from Developer Experience to Agent Experience
00:21:47 - Why the Empty Engineering Backlog Is Still a Myth
00:25:03 - How to Build Custom Agent Workflows and Reusable Skills
00:28:31 - The #1 New Skill Software Engineers Must Build Today
00:31:10 - How Meta Engineering Culture Compares to Startups
Guest - Sajal Rustagi, Staff Engineer at Meta: https://www.linkedin.com/in/sajalrustagi
#StaffEngineer #SoftwareEngineering #EngineeringLeadership
How Senior Engineers Use Coding Agents On Prod Infrastructure
2026/10/21
How do senior engineers use coding agents on prod infrastructure when “make no mistakes” is just a polite request? Kerim Satirli (HashiCorp, an IBM company) explains why prompt rules don’t hold in production, and what he runs instead.
In this video, we cover:
How Infrastructure as Code (Terraform, Contentful, Datadog, Okta, Cloudflare providers) evolved from open-source PRs to automated agent harnessesWhy AI skills files and “make no mistakes” prompts are only requests, and what replaces them in production pipelinesHow AI-generated pull requests are overwhelming open-source maintainers (and why projects like cURL are pushing back)Personalized “software factories”, spec-driven development (GitHub Spec Kit), and cutting AI documentation noise with BLUF (Bottom Line Up Front)What open-source Rust clones of Adobe mean for the future of SaaSFor infrastructure engineers, DevOps practitioners, and software architects who want to move past one-shot prompting and run coding agents on production infrastructure without losing control.
Timestamps:
00:00:00 - Why “Make No Mistakes” Is a Polite Request
00:00:38 - How Open Source Terraform Changed Provisioning
00:01:59 - Why API-First Services Matter Beyond AWS and Azure
00:04:19 - How AI Agents Changed Terraform Provider Updates
00:07:03 - Why “Make No Mistakes” Won’t Stop Your Agent
00:10:31 - Bringing Determinism Back to Agentic Workflows
00:13:07 - How AI Pull Requests Are Overwhelming Open Source
00:15:41 - Why Every Engineer Is Building a Software Factory
00:18:52 - Why AI-Generated Documentation Slows Down Humans
00:23:12 - Using Agents to Filter Noise and Summarize Specs
00:27:02 - Escape Hatches for Automated Terraform Applies
00:29:03 - Where the Joy in Engineering Lives Now
00:31:24 - Spec-Driven Development and the Return of Architecture
00:34:51 - Open-Source Rust Clones, Reverse Engineering, and SaaS
00:38:19 - How to Build Software Products People Actually Want
Guest: Kerim Satirli, Senior Developer Advocate at HashiCorp, an IBM company.
https://www.linkedin.com/in/ksatirli
#Terraform #CodingAgents #DevOps
Lead Architect Reveals His Rules for Coding Agents
2026/10/14
Lead Architect Carlos Kelkboom shares his rules for coding agents and how great engineers architect software with AI. One of the great ones is: he throws away generated code the moment he doesn't understand it. He breaks down why coding agents fail at iterative changes, why his main agent never touches files, and how he scaffolds projects for one-shot execution.
In this video, we cover:
Why AI coding agents struggle with iterative changes (SlopCodeBench) and excel at one-shot executionHow to manually scaffold code, types, and folder boundaries before letting sub-agents runDesigning a distributed Markdown and indexed-search graph harness for progressive context disclosureUsing Git worktrees to run parallel coding agents and merge the best implementationsWhy dynamic memory and the heap need to disappear in favor of deterministic programming languagesHow AI bubbles and solo coding impact junior engineers and team collaborationThis episode is for software engineers, tech leads, and system architects who want to move beyond "vibe coding" and build maintainable, deterministic production software with AI agents.
Connect with Carlos:
https://www.linkedin.com/in/carlos-k-4016b8225
Timestamps:00:00:00 - Why Carlos Throws Away Working AI Code00:00:53 - Why Pull Requests and Team Collaboration Are Dying00:03:50 - The Trap of Starting Projects You Never Finish00:06:06 - Escaping the Solo AI Developer Bubble00:11:54 - How to Scaffold Code Before Using AI Agents00:15:54 - Learning New Programming Languages With AI Agents00:21:14 - Why We Must Get Rid of the Heap00:28:32 - Building a Shared Language Across Engineering Teams00:31:31 - Vibe Coding vs Deep Software Engineering00:40:12 - Code Is Cheap: Git Worktrees for Parallel Agents00:41:45 - How Deep to Scaffold Before the Agent Runs00:45:09 - Democratizing Software, Missing Juniors, and the AI Bubble00:53:33 - Designing a Graph Harness for AI Agent Context00:58:18 - Why His Main Agent Never Touches Files01:03:07 - Throw Away Code You Don't Understand01:06:25 - Rethinking Code Reviews and Mutation Testing for AI
#CodingAgents #SoftwareEngineering #AgenticEngineering
What the Best Engineers Built for Their Coding Agents
2026/10/07
What happens when coding agents see your entire system: code, services, infrastructure and live traffic, all connected? Most agents are blind to everything outside the repo. Adyen Staff Engineer Mat Jones explains what changed once theirs weren't, and why he calls it somewhat scary.
In this video, we cover:
Running five or six coding agents in parallel with git worktrees and Atrium, an internal tool that lets agents coordinate and share memoryArchitect: nine connected graphs in Neo4j covering services, code, DNS, data stores and infrastructureIngesting 7 million trace spans a second with Kafka and Apache Flink, and what collapsed on the first trySentinel: anti-pattern monitoring, with agents that raise the fix as a merge requestMCP vs APIs vs CLI tools, and how to deal with tool bloatThis episode is for software engineers and platform teams who want coding agents to reason about real systems, not just the repo in front of them. You'll leave with a concrete place to start and an honest view of the risks.
00:00:00 - Intro
00:00:42 - Running Five Coding Agents in Parallel
00:01:35 - Atrium: How Agents Avoid Stepping on Each Other
00:06:57 - Why Graphs Save Coding Agents Tokens
00:12:25 - What Is Architect? Nine Graphs in One Database
00:16:54 - What Broke at 7 Million Spans a Second
00:20:37 - The Timeline From Proof of Concept to Production
00:27:59 - Tracing Code Changes to Critical Payment Flows
00:30:26 - How to Start: Build Scrappy, Then Earn Buy-In
00:35:07 - Making a Codebase Agent Friendly With Skills and Hooks
00:42:07 - Why You Should Start With a Service Graph
00:44:46 - The Downside of Everyone Seeing Everything
00:48:34 - Sentinel: Agents That Find and Fix Anti-Patterns
00:53:01 - Are We Going Too Fast With AI?
01:01:55 - Two Engineers, Four Months: Why Big Bets Got Cheaper
01:07:11 - MCP vs CLI Tools and the Tool Bloat Problem
Guest: Mat Jones, Staff Engineer at Adyen
https://www.linkedin.com/in/mathewwjones
#codingagents #softwareengineering #platformengineering
Why Coding Agents Keep Making Your Codebase Worse
2026/09/30
HumanLayer CEO Dexter Horthy, who coined "context engineering", on why AI agents degrade codebases over time. He breaks down a benchmark that measures AI code quality across features, and how his team ships with agents without drowning in slop.
In this video, we cover:
SlopCodeBench, SWE-bench and which coding benchmarks to trustToken maxing, dark factories and the "Instagram phase" of AI engineeringWhy 2-4x productivity beats chasing 100xPull requests, design docs and how engineers build taste nowDex's agentic engineering workflow: one-shots, overnight janitor bots and research-design-planFor engineers and engineering leaders adopting AI coding agents who want to know what's real and what works in teams at scale.
Timestamps:00:00:00 - The Man Who Coined the Term: Context Engineering00:00:54 - SlopCodeBench: Proof AI Makes Codebases Worse Over Time00:05:49 - Background Agents and the Enterprise Friction Problem00:08:13 - Why You'll Never One-Shot a Big Feature00:11:18 - Scaling Agentic Engineering to 1,000 Engineers00:16:19 - Dark Factories, Fake Hype and Token Maxing00:19:55 - Why 2-4x Faster Beats Chasing 100x00:21:31 - Should Teams Stop Doing Pull Requests?00:24:20 - Can Deterministic Tools Replace Code Review?00:27:37 - How to Build Engineering Taste When AI Writes Code00:33:05 - Dex's Agentic Workflow: One-Shots and Janitor Bots00:35:18 - Research, Design, Plan: Shipping Big Features With Agents00:38:35 - Why Overnight Agents and Heavy Parallelism Backfire00:40:10 - Subscription Maxing vs Paying Per Token00:42:40 - Parallelize Like Poker, Not a Slot Machine
Dex Horthy: https://x.com/dexhorthyDex's talks and deep dives: https://aithatworks.bold.video
#AgenticEngineering #AICoding #SoftwareEngineering
How Amp Ships 50 Times a Day With AI Agents
2026/09/23
Amp ships to production around 50 times a day with AI agents, but the change that makes their team ship faster isn't AI at all. Dario Hamidi, AI engineer at Amp, makes the case that pull requests are holding your team back, and explains what replaces them.
In this video, we cover:
Why Amp works without pull requests or feature branches, and how to try it with your own teamAgent permissions, approval fatigue, and building environments where you can trust agentsOrbs: remote agent execution, parallelism, and multiplayer sessionsShort-lived credentials and workload identity federation for cloud agentsTriaging 60+ bug reports a day with agents without frying your brainFor engineers and engineering leads who want to ship faster with AI agents and are ready to question the workflows they've always used.
Timestamps:00:00:00 - Is It Time to Kill the Pull Request?00:00:45 - What Happens If Every PR Gets Auto-Closed Tomorrow00:05:04 - Pull Requests Were Built for Strangers, Not Teammates00:07:20 - Does Dropping PRs Hurt Quality at Scale?00:08:53 - Agent Permissions: Why No Default Makes Everyone Happy00:12:42 - Don't Juggle Knives: Building Environments You Can Trust00:14:56 - The Hidden Hard Parts of Cloud Agents00:16:39 - What's an Orb? Remote Agent Execution Explained00:19:10 - How to Give Agents Credentials Without Leaking Secrets00:22:51 - Why Orbs Live Forever (and Multiplayer Orbs)00:25:49 - The State Management Problem Nobody Talks About00:29:22 - When Will Everyone Have Remote Dev Environments?00:32:23 - Orbs That Spawn Orbs: Orchestrating Agents at Scale00:34:42 - How Dario Triages 60 Bug Reports a Day With Agents00:39:23 - Avoiding Burnout When Agents Remove the Ceiling
#AIAgents #SoftwareEngineering #PullRequests
How Top Engineers Still Get Hired When Most Get Ghosted
2026/09/16
How do top engineers still get hired in 2026 when most applicants get ghosted, 120,000 people have been laid off this year, and hiring managers say they can't find talent? A recruiter, a hiring lead, a career coach and an open source engineer explain why your resume is dead on arrival when every CV looks the same, and what actually gets you in the room instead.
In this episode, we cover:
Why 120,000 tech layoffs and 60,000 open engineering roles exist at the same timeWhy only 20% of LinkedIn messages get a reply, and how to write the ones that doWhy one hiring team bans AI tools in interviews and is building an agentic coding session insteadAdaptability and resilience: the two soft skills that keep you in the roomGetting hired through GitHub, referrals and open source when your CV can't stand outWhether junior engineers still have a path, and which engineering cohort is at risk in 3 to 5 yearsTitles vs scope: how to grow when your title never changesFor software engineers, students about to graduate, and anyone in tech who wants to know what recruiters and hiring managers are actually filtering on right now.
Timestamps:00:00:00 - Intro: 1,000 Layoffs a Day00:00:47 - How Bad Is the Tech Job Market in 2026?00:02:05 - Why 120K Layoffs and 60K Open Jobs Don't Add Up00:03:40 - Why AI Tools Are Banned From Interviews00:06:28 - Hard Skills Get You In, Soft Skills Keep You There00:09:20 - "I'm a University Dropout": How GitHub Got Me Hired00:10:18 - CVs Are Too Good Now: Why Referrals Win00:13:04 - How to Get Your Open Source PR Merged00:15:02 - Why 80% of Your LinkedIn Messages Get Ghosted00:16:51 - How Open Source Led to a HashiCorp Job Offer00:19:15 - Is There Still a Place for Junior Engineers?00:22:00 - The Engineers Who'll Be Obsolete in 3 to 5 Years00:24:20 - Should You Contribute to Open Source at All?00:26:05 - AI Skills Required, Algorithms Still Tested00:27:54 - Stop Chasing Titles: Scope, Impact and Owning Your Career
#softwareengineering #techjobs #careeradvice
Why an Ex-Googler Bet Everything on an Open-Source Database
2026/09/09
Jordan Tigani helped create Google BigQuery, then got fired as Chief Product Officer on a Friday morning. He planned to hack on DuckDB to learn Rust. Investors offered to fund it before he'd decided to start a company. That company became MotherDuck
In this episode, we cover:
The DuckDB Labs partnership: why MotherDuck gave the open-source creators a co-founder share instead of going open-coreFrom alpha to paid product: 11 founders, 3 to 4 months to alpha, two years to something people would pay forAI on top of the data warehouse: vibe-coded dashboards (Dives), pipelines (Flights), a context layer (Guides), and why business users catch mistakes analysts missAre dashboards dead? Jordan wrote "Big Data Is Dead"; his answer on dashboards is differentCareer advice: why you shouldn't want to work on the query optimizer, and the skill Jordan says matters moreFor engineers curious about database and infrastructure companies, open-source business models, and how AI is changing who gets to ask questions of data.
Timestamps:
00:00:00 - Intro
00:00:32 - Fired on a Friday: how MotherDuck accidentally started
00:04:50 - Giving DuckDB Labs a co-founder share of the company
00:07:43 - Why most open-source SaaS products are just "managed"
00:09:31 - Why VCs said yes: Snowflake, DuckDB, and BigQuery credibility
00:10:50 - The 11-person founding team that skipped the wrong designs
00:12:20 - Alpha in 4 months, beta in a year, paid in two
00:15:20 - Vibe-coded BI: Dives, Flights, Guides, and an agent harness
00:20:10 - The questions business users ask that analysts never do
00:24:14 - Are dashboards dead in the age of agents?
00:27:57 - Everybody wants to work on the optimizer (don't)
00:31:23 - The engineer superpower most engineers look down on
00:33:20 - Writing: the one skill Jordan would learn (and still hates)
00:36:05 - Does contributing to DuckDB get you hired at MotherDuck?
00:37:20 - Why a database company leaned into the duck
#MotherDuck #DuckDB #SoftwareEngineering
How the Best Engineers Build a World Model (Google Earth Creator & Niantic Spatial CTO)
2026/09/02
Niantic Spatial CTO Brian McClendon on how the best engineers solve problems most give up on — from a 4D model of the world to shipping research in months. He built Google Earth and ran Google Maps for over a decade, and he's been there, done that. What he's building now is harder, and it's already live for customers. Along the way: who makes it on his team and who doesn't, and the one piece of advice he'd give every engineer using AI.
In this video, we cover:
- The 4D model of the world: visual positioning, change detection, and treating a pile of photos like a database
- Gaussian splats and real-to-sim: capturing a room and loading it into Nvidia Isaac to train robots
- Turning a research idea into a production service in six months
- What Google Maps taught him about building for robots instead of humans
- Designing problems AI can self-check, and why token maxing is a waste
For engineers and engineering leaders who want to work on problems that don't have a known answer yet — and who want to know what a CTO who's built the definitive product in his field looks for in the people he hires.
Recorded at the AI4 conference 2026.
Timestamps:
00:00:00 - Google Earth? Been There, Done That
00:00:46 - Turning a Research Idea Into Production in 6 Months
00:02:37 - How Any Photo Gets Located Within Half a Meter
00:06:37 - The Long-Term Goal: A 4D Model of the World
00:08:37 - Treating a Pile of Photos Like a Database
00:11:58 - What Google Maps Taught Him About Training Robots
00:15:22 - Gaussian Splats Explained in Plain Terms
00:17:42 - The Unsolved Problem: Scale and Semantic Change
00:20:34 - Why Google Earth Is Good Enough
00:22:09 - Who Makes It on His Team and Who Doesn't
00:23:38 - Designing Problems AI Can Self-Check
00:26:03 - The Insights Hidden in the Physical World
00:28:18 - Digital Twins, Cities, and Ready Player One
00:31:35 - Visual Positioning When GPS Gets Spoofed
00:33:24 - Token Maxing Is B******t: Advice for Engineers
Guest: Brian McClendon, CTO at Niantic Spatial. The engineer behind Google Earth; ran Google Maps for over a decade.
https://www.linkedin.com/in/brianmcclendon
#NianticSpatial #GoogleEarth #SoftwareEngineering
How New Staff Engineers Build Judgment Without Years of Experience
2026/08/26
How do new staff engineers build judgment without the years of experience that used to come with the role? Mallika Rao, engineering leader in big tech, explains why the data-structures-and-algorithms foundation everyone was trained on is no longer enough on its own, and where the complexity has actually shifted now that AI writes the implementation.
In this video, we cover:
Why "how does AI affect engineers" is the wrong question, and what to ask insteadRehearsing multiple futures: what judgment looks like in a staff engineerThe case method: building judgment from incident reports and system design history instead of waiting years for itCognitive coordination, code review load, and the surprise ask for more meetings at staff levelTiger teams vs scaled teams, trust as architecture, and building evals from a spreadsheetSplitting planning from execution so engineers stop falling behind with agentsTaste vs judgment, and how to build both outside of softwareIf you've just made staff, or you're about to, this conversation gives you a frame for what the level actually demands now and how to grow into it faster than the old apprenticeship allowed.
Recorded at the AI4 conference 2026.
Timestamps:
00:00:00 - How AI Is Changing Senior Engineering Careers
00:00:41 - Why "How Does AI Affect Engineers" Is the Wrong Question
00:03:26 - What Judgment Actually Is: Rehearsing Multiple Futures
00:05:24 - Why Data Structures and Algorithms Are No Longer Enough
00:07:22 - Learning Judgment From Incident Reports Like the 2017 S3 Outage
00:11:13 - The New Staff Engineer's Core Challenge: Cognitive Coordination
00:14:48 - What Managers, Universities, and Shakespeare Each Owe You
00:17:55 - Code Review Load, Meeting Notes, and the Surprise Ask for More Meetings
00:23:59 - Trust as Architecture: Why Evals Started as a Spreadsheet
00:27:09 - Tiger Teams vs Big Teams: Product Managers Reviewing Code
00:32:39 - Why Some Engineers Can't Keep Up With Agents
00:35:46 - Local AI Champions and Splitting Planning From Execution
00:38:38 - Go Deep or Go Broad? Search in a World of Agents
00:44:12 - Taste vs Judgment: Thinking in 50 Layers
Guest: Mallika Rao, engineering leader in big tech.
Rehearshing the Future framework
If by Rudyard Kipling
Amazon AI Lead: What Differentiates The Best AI Coding Models
2026/08/19
How does Amazon build its agentic AI? Michael Giannangeli, Head of Product for Amazon Nova and Agentic AI, breaks down evals, RL gyms, and model routing.
He also explains why the bottleneck in software has shifted away from engineering hours and what takes its place.
In this video, we cover:
The eval lifecycle: building from real failure modes, saturation, and why 100% means deleteRL gyms: training models on real environments like migrations, DevOps, and pen testingModel routing, cost-per-token trade-offs, and why routing isn't solvedThe agent stack of an Amazon product lead: Claude Code, Codex, and KiroAutonomous migrations, trust, and how much human-in-the-loop survivesFor engineers and product people building with AI agents who want to see how a frontier lab actually closes its feedback loops.
Recorded at the AI4 conference 2026.
Timestamps:
00:00:00 - Intro
00:00:36 - The Agents an Amazon Product Lead Uses Daily
00:03:36 - Why Nobody's Heard of Amazon Nova
00:04:55 - Model Costs and the Routing Problem
00:08:10 - Why Building Good Evals Is So Hard
00:10:05 - When Evals Saturate and Get Deleted
00:12:17 - Turning Real Failure Modes Into Hundreds of Evals
00:15:26 - Improving Models Without Training on Customer Data
00:18:26 - If Everyone Uses Agents, You Need Agents
00:20:22 - The Bottleneck Is No Longer Engineering Hours
00:23:20 - Ship Fast to Validate the Right Thing
00:26:44 - Staying at the Frontier Amid Constant Noise
00:29:37 - Spend 10-20% of Your Time Experimenting
00:32:54 - RL Gyms: How Models Learn From Failure
00:37:09 - Will Migrations Become Fully Autonomous?
Guest: Michael Giannangeli - Head of Product, Agentic AI & Amazon Nova at Amazon
#AmazonNova #AgenticAI #AIEngineering
Wes Bos: How Developers Stand Out When AI Writes the Code
2026/08/12
AI is changing what developers build, but code alone is no longer enough to prove what you can do. Wes Bos explains why engineers need to solve problems beyond syntax, how agent workflows are reshaping software development, and what still requires human thinking.
In this conversation:
The limits of generative UI and AI-generated designAgent loops, harnesses, and cheaper AI modelsThe rising cost of AI coding and the case for local hardwareWhy developer education is shifting from syntax to problem-solvingPersonal branding, conferences, newsletters, and AI-generated contentFor developers navigating AI-assisted coding, this episode explores the skills and signals that still help you stand out.
This podcast was recorded at JSNation, the key web dev conference.
OUTLINE
00:00:00 - Code Is Not Enough for Developers
00:00:32 - Why Generative UI Still Feels Unfinished
00:04:35 - How Agent Loops Improve AI Coding
00:07:06 - When Agent Workflows Become Standard Tools
00:08:19 - Are Cheaper AI Models Good Enough?
00:10:44 - Can AI Coding Costs Stay Sustainable?
00:12:24 - What Engineers Need To Learn Now
00:14:23 - Why Fundamentals Matter Beyond Syntax
00:15:34 - How Non-Coders Are Building Production Tools
00:16:21 - Why In-Person Conferences Still Matter
00:18:11 - Personal Branding When Code Isn't Enough
00:20:37 - Can Newsletters Beat The Attention Crisis?
00:22:02 - Why AI-Generated Content Feels Insulting
00:24:12 - Use AI To Scaffold, Not Think
Podcast reviews
Read Beyond Coding podcast reviews
YourCTO 2025/06/04
Beyond the Terminal: Real-World Growth for Engineers
Beyond Coding is one of those rare podcasts that manages to be both tactical and genuinely inspiring. Patrick Akil consistently brings clarity to the ...
Podcast sponsorship advertising
Start advertising on Beyond Coding relevant audience podcasts
You may also like to advertise on these Podcasts

4.959992000
Legal AF by MeidasTouch
MeidasTouch Network

4.7292862000
The Michael Knowles Show
The Daily Wire

4.930912000
The Quote of the Day Show | Daily Motivational Talks
Sean Croxton

4.9248151467
Unashamed with the Robertson Family
Tread Lively

4.897071458
The Graham Allen Show
Graham Allen

4.7278982000
The Matt Walsh Show
The Daily Wire

4.7106622000
FantasyPros - Fantasy Football Podcast
iHeartPodcasts

4.762622000
The Lawfare Podcast
The Lawfare Institute

4.858251936
Sara Gonzales Unfiltered
Blaze Podcast Network

4.6221762000
Mark Levin Podcast
Cumulus Podcast Network