Beyond Coding

Are you over-engineering for a future that might never come? In this episode, we explore why "future-proofing" often leads to wasted time and sunk costs, and how shifting your mindset from opinions to hypotheses can drastically improve your Developer Experience (DevEx). In this episode, we cover: If you are a software engineer or tech lead tired of the "Sacred Cloud Committee" and slow processes, this deep dive into DevEx is for you. Connect with Bas de Groot: https://www.linkedin.com/in/bas-de-groot-635013100 Timestamps: 00:00:00 - Intro 00:01:00 - The Danger of "Future-Proofing" Your Architecture 00:03:18 - Why You Should Use Hypotheses Over Opinions 00:05:32 - "Shift Left Until There's Only Sh*t Left" 00:08:19 - At What Size Do You Need a DevEx Team? 00:11:02 - How to Measure Developer Friction Effectively 00:15:43 - Using Data to Fix Slow CI/CD Pipelines 00:17:26 - Why Surveys Beat DORA Metrics for Context 00:19:52 - The "Sacred Cloud Committee" Blocking Deployments 00:24:51 - How to Get Buy-In for DevEx Initiatives 00:28:56 - The Role of Hands-On Coding in DevEx 00:31:47 - Will AI Agents Fix Bad Processes? 00:34:44 - You Are Still Responsible for AI-Generated Code #developerexperience #softwarearchitecture #techlead

The difference between a junior and a senior engineer isn't coding speed, it's knowing when to say "no." "The best code you can write is the code you don't write." In this episode, I sit down with Alessandro Mautone (Senior Software Engineer at Aquablu, ex-WeTransfer) to discuss the reality of engineering at a scale-up: how do you maintain technical excellence when the business demands speed? We break down why delivering features "fast" pays your salary, but how to negotiate deadlines so you don't drown in technical debt later. If you want to move from writing code to owning product decisions, this conversation is for you. In this episode, we cover: - How to push back on features and negotiate deadlines without upsetting stakeholders - Why chasing "perfect code" can hurt a company in growth mode - The Generalist vs. Specialist career path: Which one is right for you? - The potential pitfalls of using AI for unit tests without proper oversight Timestamps: 00:00:00 - Intro 00:01:06 - Balancing Technical Excellence With Delivery Speed 00:04:11 - Why Delivering Features Pays Your Salary 00:06:51 - The Importance of Ownership and "Skin in the Game" 00:08:59 - Leaving WeTransfer: When Company Direction Shifts 00:11:49 - The Generalist vs. Specialist Career Path Debate 00:16:46 - How to Attract Top Engineering Talent to Your Team 00:18:50 - Is LeetCode the Right Way to Hire for Scale-Ups? 00:23:16 - Learning to "Say No" is a Sign of Seniority 00:25:17 - Negotiating Scope Without Burning Bridges 00:26:02 - When AI Generates Bad Unit Tests 00:28:14 - Never Compromise on Tests, Even in "Code Red" 00:33:59 - Communicating Technical Concepts to Non-Tech Stakeholders 00:35:35 - The Never-Ending Battle Against Complexity 00:37:26 - When to Build for the Future vs. Ship Now 00:42:30 - A Real-World Example of Refactoring for Simplicity 00:46:48 - The Skill That Will Be Make or Break for Engineers #SoftwareEngineering #ScaleUp #TechnicalDebt

We are at a unique point in history where there is finally an alternative to human coding. If AI can write the code effectively, what is left for the software engineer? In this episode, Joris Conijn (AWS CTO at Xebia) argues that the era of "just coding" is over. We discuss why senior developers are safe (for now), why juniors are at risk of never learning the fundamentals, and how "Shadow AI" is forcing companies to change their security strategies. Most importantly, we break down the difference between a "Programmer" and a "Software Engineer" with the introduction of agentic tools. If you want to future-proof your career and move from writing lines of code to designing systems, this conversation is for you. In this episode, we cover: Connect with Joris Conijn: https://www.linkedin.com/in/jorisconijn TIMESTAMPS 00:00:00 - Intro 00:01:11 - What Keeps a CTO Excited About Tech? 00:02:58 - Stop Being the "Department of No" in Security 00:05:28 - The Real Risk of Banning AI at Work 00:06:32 - When Developers Hold the Organization Hostage 00:08:14 - The Hidden Dangers of Instant AI Code Fixes 00:09:50 - Will Future Devs Understand Object Oriented Programming? 00:11:36 - Using AI to Accelerate Learning vs Copy-Pasting 00:13:17 - Why Testing Matters More When AI Writes Code 00:16:42 - Automating the Boring Parts of the SDLC 00:19:06 - How to Turn Meeting Transcripts into User Stories 00:21:36 - The Critical Skill of Making Implicit Knowledge Explicit 00:23:10 - Why You Should Stop Obsessing Over Story Points 00:27:46 - The "A-Team" Approach to High-Trust Development 00:29:54 - Running Parallel Workflows with AI Agents 00:33:34 - Pro Tip: Check Your AI Agents into Git 00:35:52 - Balancing Autonomy and Governance in Large Teams 00:39:19 - There Is Finally an Alternative to Human Coders 00:41:07 - Programmer vs Software Engineer: What is the Difference? 00:44:45 - How to Teach Software Engineering in the AI Era #SoftwareEngineering #SystemDesign #AIAgents

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: Connect with Adnan Alshar: https://www.linkedin.com/in/adnanmalshar92 Connect with Jelmer de Jong: https://www.linkedin.com/in/jelmerdejong-xebia 00: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 Success 00:23:35 - Why No Metrics Is the Biggest Red Flag 00: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

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: Timestamps 00: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

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: Whether 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

"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 build If 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/ghohpe 00: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

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: Connect with Zanina: https://www.linkedin.com/in/zaninakatira References: RACI - https://en.wikipedia.org/wiki/Responsibility_assignment_matrix Timestamps: 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

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: Connect with Maria: https://www.linkedin.com/in/maria-vechtomova Timestamps: 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 Need 00: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

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: This 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/ansahay Timestamps: 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

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: This 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/marijnmarkus Timestamps: 00:00:00 - Intro 00:01:01 - Realizing That Data Science Can Actually Save Lives 00:04:36 - Predicting Refugee Movements With Hamburger Prices 00:07:05 - Why You Should Try Different Roles Early in Your Career 00:12:37 - Learning in Banking to Eventually Help Non-Profits 00:15:38 - Why Certifications Are Compensation for Lack of Experience 00:18:36 - The Single Most Important Skill in the Tech Field 00:21:39 - "If They Understood the Problem, They Wouldn't Hire You" 00:25:48 - Why Innovation Comes From War, Crime, and Adult Industries 00:31:16 - The Danger of AI Agents and Automated Social Engineering 00:35:03 - Focus on Skills That Do Not Have Expiration Dates 00:39:47 - How to Navigate Truth in the Era of Deepfakes 00: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

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/praveenmurugesan Timestamps: 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

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: Connect with Mo Fagir: https://www.linkedin.com/in/mo-nour-tarig Timestamps: 00:00:00 - Intro 00:01:14 - Why software jobs dropped 70% while FDEs grew over 800% 00:02:55 - Why companies can't implement AI without Forward Deployed Engineers 00:05:36 - Is this career path safe for traditional software engineers? 00:07:54 - The exact technical stack you need to master today 00:10:48 - Moving from engineering scope to product centric thinking 00:16:15 - Can juniors and early career devs get hired as FDEs? 00:19:12 - How to build a portfolio that gets you hired 00:22:17 - Why passion and attitude beat experience in the AI era 00:24:33 - How to train yourself to have a sense of urgency 00:29:05 - Can introverts succeed in client facing engineering roles? 00:32:17 - Lessons learned from interning at NASA and researching AI 00: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

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: This 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/woodsonmartin Timestamps: 00:00:00 - Intro 00:00:56 - How Agentic AI keeps the human in the loop 00:01:55 - Real-world example: Automating the grunt work 00:04:17 - How engineers are using agents internally 00:05:52 - Blending Low-Code and High-Code for complex systems 00: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 job 00:13:14 - Layoffs vs. the rise of the solo entrepreneur 00:15:18 - Career advice for a volatile tech market 00:17:02 - How to retain top talent and keep them happy 00:20:10 - Why we radically changed our engineering team structure 00:24:33 - The "Forward Deployed Engineer" model explained 00:27:08 - Outsystems vs. OpenAI: The future of platform building 00:31:45 - The tech debt problem no one's talking about 00:34:23 - The one thing that keeps you from becoming irrelevant #SoftwareEngineering #CareerAdvice #AIAgents

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: 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/movereem Timestamps: 00:00:00 - Intro 00:01:22 - The "10% Engineering" Paradox at a €100M+ Company 00:03:20 - How Standardization Allows a Small Team to Do More 00:04:27 - The Two Types of Engineers Every Successful Company Needs 00:06:46 - Why Feeling Responsible is More Powerful Than Being Responsible 00:09:33 - The Secret Sauce of High-Performing Engineering Teams 00:11:52 - A Simple Method to Keep Engineers Connected to Customers 00:14:22 - What We Look For When Hiring New Engineers 00:17:09 - The #1 Red Flag That Will Get You Rejected in an Interview 00:19:33 - Why We Don't Use Scrum (And What We Do Instead) 00:22:51 - The Power of Strong, Decisive Leadership 00:24:13 - How Our 4-Day Work Week Actually Works 00:26:55 - Our Approach to Adopting AI Tools like Copilot 00:28:19 - Final Advice: The Best Way to Grow Your Career #EngineeringCulture #Productivity #SoftwareDevelopment

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 agents Connect with Bassem Dghaidi: https://www.linkedin.com/in/bassemdghaidy Timestamps: 00:00:00 - Intro 00:00:48 - Theory vs. Practice in System Design 00:02:06 - The Startup That Almost Failed via Kubernetes 00:03:33 - How GitHub Scales (It's Simpler Than You Think) 00:05:20 - The Underrated Power of Vertical Scaling 00:08:23 - Why Big Tech Interviews for Scale You Don't Need Yet 00:10:39 - Software Evolves, It Isn't Just "Built" 00:11:53 - Only Design for the Next Order of Magnitude 00:15:39 - Stop Building Generic Frameworks 00:18:17 - "Hacking" the System Design Interview 00:21:29 - Translating Tech Problems to Business Risks 00:27:37 - Layoffs & Engineering Efficiency 00:29:41 - Proving Your Impact with Numbers 00:31:00 - Professional Engineering vs. Hobby Coding 00: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

What does it take to build a career as a mobile engineer when AI is changing everything? Pavel shares how he went from Java backend engineer to Head of Mobile, why he only joins mobile-first companies, and how AI-assisted development brought the joy back to his work. This isn't theory, it's real lessons from 15+ years in the field and now learning Android at a senior level. In this episode, we cover: AI-assisted mobile development workflow (the four-window tmux setup) Why mobile-first companies operate completely differently Hiring for strengths, not lack of weaknesses (lessons from Uber) Leading as a hands-on engineer who stays in the trenches Why React Native doesn't feel native and when to go fully native Whether you're building your mobile engineering career or figuring out how AI changes your workflow, this conversation offers practical perspectives on staying effective and making intentional career choices. Connect with Pasha: https://www.linkedin.com/in/kovpas TIMESTAMPS: 00:00:00 - Intro 00:01:13 - Using AI as Your Junior Engineer Teammate 00:02:33 - The Four-Window Tmux Setup for AI-Assisted Development 00:04:29 - Managing Multiple Features with Git Worktrees 00:05:52 - Why AI Makes You a Better Code Reviewer 00:08:07 - Setting Up Markdown Files for AI Context 00:11:54 - Small Teams vs Big Companies: Where Mobile Engineers Thrive 00:16:26 - The Mobile-First Company Filter That Shapes Every Career Move 00:18:31 - Being Nice: The Underrated Career Skill 00:20:29 - Pick Your Battles: When to Disagree and Commit 00:22:52 - Hire for Strengths, Not Lack of Weaknesses 00:25:16 - Is Software Engineering Still a Good Career Choice? 00:28:19 - How I Accidentally Became a Mobile Engineer 00:31:41 - Why I Only Work on Apps That Matter to People 00:35:08 - Joining Uber During the Big Mobile App Rewrite 00:39:12 - Leading Without Rank: Managing as a Hands-On Engineer 00:43:01 - How AI Changed Mobile Development in 12 Months 00:46:09 - The Communication Skills That Make or Break Engineers 00:49:59 - It's Okay to Say You Don't Understand 00:51:30 - Working on Payments: Building Critical App Infrastructure 00:53:25 - Why React Native Doesn't Feel Native (And What Works Better) 00:55:36 - Can You Switch Specializations Without Taking a Pay Cut? 00:57:02 - How Learning Android Brought the Joy Back

Worried about staying relevant as AI and new tools keep changing tech? The answer isn't chasing every new framework, it's treating your career like an engineering problem you can solve. In this episode, we cover: If you're an engineer who wants to take control of your career instead of letting it happen to you, this episode gives you the frameworks and tactics to do it. Connect with Özgen Güngör: https://www.linkedin.com/in/ozgengungor Timestamps: 00:00:00 - Intro 00:00:46 - The Biggest Challenge for Tech Careers Today 00:01:33 - How to Stay Relevant in the Age of AI 00:03:46 - The Coming Commoditization of Coding 00:05:29 - How to Move Up the Value Stream as an Engineer 00:07:35 - Your First Tech Job is a Throwaway (And That's OK) 00:09:24 - The Power of Breaking Down Your Career Plan 00:11:44 - You Work 13% of Your Life: Why Intentionality Matters 00:13:56 - I Have Too Many Career Options. What Do I Do? 00:15:34 - The "5 Whys" Exercise for Your Career 00:19:38 - How to Get Your Manager to Be Your Ally 00:22:15 - The Truth About Big Tech's Broken Promotion Process 00:24:43 - The #1 Person Who Cares About Your Career 00:28:48 - Why You MUST Keep a "Brag Doc" 00:34:08 - How to Avoid Falling Behind in Promotions 00:37:33 - What is a Competency Framework? 00:40:34 - How to Map Out Your Own Career Ladder 00:44:35 - The Silent Factor That Kills Engineering Performance 00:48:31 - Your Career Transcends Your Company 00:52:40 - The 5-Year Plan That Changed My Career 00:56:18 - 3 Essential Tools for Total Career Management #TechCareer #SoftwareEngineering #CareerAdvice

You asked, I answered. In this Q&A episode, I tackle the toughest career questions you submitted: from getting promoted when the process feels political, to negotiating salary, to leading projects as an IC. In this episode, we cover: * Holding peers accountable when you're not their manager * Navigating promotions when the process is political or unclear * Increasing your salary with strategic job offers * Building real authority and getting noticed by leadership * Staying relevant in the age of AI without burning out This is for software engineers who want practical strategies to level up their careers, increase their earning potential, and make real impact without the fluff. Join me at React Advanced and Tech Lead Conf in London: https://ti.to/gitnation/react-advanced-london-2025/discount/CODING10 Timestamps: 00:00:00 - Intro 00:00:19 - Holding Peers Accountable When Managers Won't Help 00:03:58 - The Surprising Truth About Code "Quality" 00:05:43 - Scaling Accountability Across Large Teams 00:07:50 - When Climbing the Career Ladder Feels Political 00:12:37 - How to Stay Relevant in Tech Without Burning Out 00:14:49 - The Key to Learning Without Feeling Overwhelmed 00:15:18 - The Real Difference for Engineers Working Globally 00:17:44 - What to Do When You Get a Better Job Offer 00:20:51 - Finding Motivation Beyond a Higher Salary 00:21:41 - How to Build Real Credibility and Authority 00:25:31 - The Advice I'd Give My Junior Developer Self 00:29:05 - The Art of Effective Delegation 00:31:47 - Why Delegation Is Really an Act of Trust 00:32:21 - Team Player vs. Individual Star: A False Choice? 00:34:43 - The #1 Personal Development Skill for Engineers 00:37:11 - The Hidden Dangers of Relying on AI Tools 00:40:08 - Is Volunteering at Tech Conferences Worth It? 00:42:50 - My Personal Struggle with Embracing Change 00:45:32 - The Career "Regret" I Don't Actually Regret 00:46:45 - How to Stay Productive While Dealing with Grief 00:49:08 - My Process for Finding Great Podcast Guests 00:50:48 - The Secret to Making Guests Feel Comfortable 00:52:06 - How Podcasting Transformed My Communication Skills 00:53:35 - Handling Guarded or Difficult Podcast Guests 00:56:11 - Final Thoughts & How to Support the Channel Got questions for the next Q&A? Drop them in the comments 👇 #SoftwareEngineering #CareerGrowth #TechLeadership

What's the real difference between a good software engineer and a truly great one? It’s more than just coding skill. It's a specific mindset, a disciplined approach to technology, and a deep understanding of core principles. This is the roadmap to leveling up your career. In this conversation with Sander Mak, Director of Technology at Picnic, we discuss the methods they use to train world-class engineers. You will learn: The "under the hood" knowledge that truly matters. Why great engineers often choose "boring," proven technology. The critical transition from being a coder to a product-focused engineer. The most common pitfall that holds good developers back. If you're a software developer looking to move beyond "good enough" and achieve greatness in your craft, this is the episode for you. Connect with Sander: https://www.linkedin.com/in/sandermak Timestamps: 00:00:00 - Intro 00:00:30 - Building Picnic's Tech Academy for New Engineers 00:04:37 - The Key Mindset of a Successful Junior Engineer 00:08:01 - A Look Inside the Engineering Training Curriculum 00:12:19 - The Common Pitfall of Copying Without Understanding 00:14:10 - How Deep "Under the Hood" Knowledge Should Go 00:17:41 - Why Great Engineers Value "Boring" Technology 00:21:44 - Improving Developer Experience and Team Productivity 00:30:02 - The Transition from Coder to Product Engineer 00:34:18 - Key Advice for Self-Taught Developers 00:35:41 - Using AI for Learning vs. for Code Generation #SoftwareEngineering #DeveloperCareer #Coding