Managing Engineers

Diving into the subtle art of managing (software) engineers with Si Jobling and Neil Younger.

Épisodes

  1. -1 J

    What the metrics?

    Metrics are meant to help. But sometimes they just perform. In this episode, we explore the difference between measurement that drives insight and measurement that becomes theatre. From counting test cases and commit history, to DORA metrics and Monte Carlo forecasting, we unpack how numbers can guide teams - or quietly distort behaviour  . We reflect on how metrics have evolved over the past 25 years, how Agile shifted the way we think about delivery and value, and why modern teams now have more data than ever but not always more clarity. We also challenge a few uncomfortable truths: When a metric becomes a target When dashboards replace conversations When velocity gets mistaken for predictability When comparing teams causes more harm than insight When “healthy culture” is reduced to a number At its best, a metric is an invitation to a conversation. At its worst, it is theatre. What we cover Early career metrics: counting test cases and “how many did you do?” Commit counts, leaderboards and accidental gamification From CD releases to cloud shipping and real time telemetry DORA and the four key delivery metrics SPACE Framework and measuring beyond output Monte Carlo method vs story point velocity Confidence levels and how to talk about uncertainty with stakeholders Goodhart’s law and the danger of turning measures into targets Pulse surveys, fatigue and the limits of yearly sentiment snapshots The challenge: if you could only pick one metric, what would it be? Useful links Monte Carlo method https://en.wikipedia.org/wiki/Monte_Carlo_method https://medium.com/@benjihuser/an-introduction-and-step-by-step-guide-to-monte-carlo-simulations-4706f675a02f Actionable Agile for Jira https://www.55degrees.se/products/actionableagileanalytics DORA research https://dora.dev/research/ SPACE Framework https://www.youtube.com/watch?v=O2rbekHpG4Q Goodhart’s law https://en.wikipedia.org/wiki/Goodhart%27s_law Moving beyond velocity https://docondev.com/escape-velocity PETALS Measuring team health across Productivity, Enjoyment, Teamwork, Learning and Serenity https://petals.team https://app.petals.team Chapter markers 00:00:07 - Intro and over engineering an EV charger box 00:02:16 - Why metrics matter and how they can mislead 00:03:27 - Counting test cases and early vanity metrics 00:05:45 - Commit counts and gamified leaderboards 00:09:57 - DORA metrics and delivery performance 00:13:07 - SPACE and measuring people, not just output 00:16:02 - Time to learn vs time to earn 00:20:03 - Monte Carlo forecasting vs velocity 00:24:35 - Pulse surveys, fatigue and psychological safety 00:30:03 - What averages hide 00:35:05 - Goodhart’s Law and when metrics go wrong 00:45:07 - If you could only choose one metric 00:50:56 - Wrap up and listener challenge Hosts Connect with us on LinkedIn… Neil Younger - https://www.linkedin.com/in/neil-younger/ Simon Jobling - https://www.linkedin.com/in/sijobling/ What do you measure? What have you stopped measuring? And what has backfired spectacularly?

    52 min
  2. 4 FÉVR.

    Working remotely or remotely working

    We’ve reached the halfway point of our 10-part season, which felt like the right moment to step back and talk about one of the most persistent topics in modern engineering teams - remote and hybrid working. In this episode, Si and Neil explore what working from home actually means when you’re managing software engineers. Not the policies, perks, or perfect desk setups, but the lived reality. What changed during lockdown, what stuck, what didn’t, and what still feels unresolved. The conversation spans office-first teams, fully remote organisations, and hybrid models, touching on privilege, trust, inclusion, junior development, boundaries, and the invisible rules that often go unspoken. There’s talk of sheds, spare rooms, surveillance software, walk-and-talk one-to-ones, and why “just get people back in the office” is rarely the full answer. As ever, there’s no silver bullet. Just two engineering managers comparing notes, challenging assumptions, and trying to design better ways of working on purpose. Chapters 00:00 – Mid-season check-in and why this topic keeps coming up 02:00 – Life before lockdown and the shift to hybrid working 05:30 – Fully remote by design vs remote by reaction 10:15 – Privilege, space, and the uneven reality of home working 15:10 – Choice vs circumstance and how it affects teams 19:45 – Making office days intentional, not performative 24:40 – Trust, transparency, and working in the open 30:00 – Cameras, connection, and staying human at a distance 34:00 – Surveillance tools, productivity myths, and broken trust 40:00 – What actually matters in a home working setup 47:00 – Boundaries, rituals, and knowing when the day is done 52:00 – Juniors, missed context, and unwritten rules 54:00 – Trust as the foundation and what we’d revisit next

    57 min
  3. 21 JANV.

    From QA to quality engineering

    They explore the journey from “tester” to QA, quality engineer, and quality coach, and why job titles still shape perception, influence, and when people are invited into the room. KEY THEMES Why quality is not just testing at the end, but shaping ideas from discovery through to delivery How different titles like tester, QA, quality engineer, and quality coach change expectations and behaviours The power of early involvement, questioning, and exploring unknowns before code is written Why exploratory testing still matters, even with strong automation and pipelines The role of QA as enablers and coaches, not gatekeepers or sign-off roles Lessons from teams that removed QA roles, and why many later reintroduced them How communities like Ministry of Testing helped shape modern quality practices Why humans still matter in a world of automation and AI, especially when it comes to curiosity, judgement, and risk Practical ways teams without dedicated QA roles can improve quality today Neil also shares real-world stories from his career, including the impact of renaming testing roles, the long-running “test is dead” debate, and why discovering what you don’t know is where quality really adds value. This episode is for engineering managers, developers, testers, and anyone thinking about how teams build better software together. CHAPTERS 00:00 – Risk, ladders, and an accidental intro to quality thinking 03:00 – From testers to QA to quality engineers – why names evolved 07:30 – Why job titles change behaviour and influence 12:00 – Testing early, discovery, and reducing risk before code 15:20 – Ministry of Testing and the power of community 19:10 – From tester to quality coach – an evolving role 24:00 – “Test is dead” and what it really meant 28:20 – Do modern teams still need dedicated QA roles? 32:10 – Exploratory testing and finding the unknowns 42:00 – Practical ways teams can improve quality today LINKS Ministry of Testing https://www.ministryoftesting.com/ Exploratory Testing – Martin Fowler https://martinfowler.com/bliki/ExploratoryTesting.html Explore It! by Elisabeth Hendrickson https://www.oreilly.com/library/view/explore-it/9781941222584/ Agile Testing Quadrants (Lisa Crispin) https://lisacrispin.com/2024/10/11/the-agile-testing-quadrants/ “Test Is Dead” talk https://www.youtube.com/watch?v=X1jWe5rOu3g “Test Is Dead” – 8 years later https://www.youtube.com/watch?v=oLpmtSS9JQM What is a Quality Coach? (Anne Marie Charrett) https://www.annemariecharrett.com/what-is-a-quality-coach/ Modern Testing Principles https://www.moderntesting.org/ This podcast is powered by Pinecast. Read transcript

    50 min
  4. 03/12/2025

    How hands on are you?

    How hands-on should an engineering manager be, and what do we lose or gain as we move away from the code? In this episode we dig into the messy middle between technical work, people leadership and the hunt for that spark that keeps us excited. Using our own careers as the backdrop, we unpack what “hands-on” really means. Is it code, system thinking, process, delivery, people, or all of it at once? We talk about losing technical confidence, finding excitement again, navigating vulnerability, and working out when you’re still adding value… or just getting in the way. And yes, unicycles somehow made it into the episode. If this sparks any thoughts, tell us what you think about the episode or about being hands-on yourself. You can find us both on LinkedIn. Chapters 00:00 – Intro and what we mean by “hands-on” 01:23 – Code, contribution and confidence 04:35 – Technical work beyond coding 08:39 – Losing old skills and chasing excitement 11:54 – Enabling engineers and knowing who to bring in 18:51 – Vulnerability, updates and not knowing the detail 22:22 – Learning complexity over time 26:39 – EMs without engineering backgrounds 29:56 – Missing hands-on work and finding balance 31:52 – EM archetypes and where we fit 45:42 – Staying technical through side projects 48:03 – What we miss, what excites us and takeaways 53:46 – How to share feedback and keep the chat going Links Pat Kua’s 5 Engineering Manager Archetypes: https://www.patkua.com/blog/5-engineering-manager-archetypes/ Simon Wardley - From here to there and back again: https://www.youtube.com/watch?v=hEjjCI3kTM4 Connect with us Tell us what you think about the episode or about being hands-on yourself: Si on LinkedIn: https://www.linkedin.com/in/sijobling Neil on LinkedIn: https://www.linkedin.com/in/neilyounger Credits Created by Si Jobling and Neil Younger Recorded and edited in Descript Hosted on Spotify, Apple Podcasts and YouTube Produced, artwork and publishing by Unstyled Studios Check out our podcast host, Pinecast. Start your own podcast for free with no credit card required. If you decide to upgrade, use coupon code r-b0b82e for 40% off for 4 months, and support Managing Engineers. Read transcript

    55 min
  5. 19/11/2025

    Always learning

    In this episode, Si and Neil dive into learning as engineering managers, how they approach it personally, how teams respond to it, and why it’s weirdly hard to make time for something everyone claims to value. They chat about learning budgets, 10 percent time, hackathons, internal conferences, external speakers, audiobooks, Blinkist, reflection time, and why inspiration often hits when you’re nowhere near your laptop. They unpack different learning styles, the pressure to deliver, how to support engineers who don’t know what to learn next, and why rest is just as important as active learning. Links mentioned in the episode Here are the references we talked through: Wardley Mapping: https://learnwardleymapping.com LeadDev Conference: https://leaddev.com Blinkist: https://www.blinkist.com LinkedIn Learning: https://www.linkedin.com/learning Agile Cambridge: https://agilecambridge.net R&D tax credits: https://www.gov.uk/guidance/corporation-tax-research-and-development-rd-relief Connect with us Tell us what you think about the episode or learning yourself: Si on LinkedIn: https://www.linkedin.com/in/sijobling/ Neil on LinkedIn: https://www.linkedin.com/in/neil-younger/ Chapters [00:00] Setting up episode two and the learning theme [01:39] Why learning matters to us as engineering managers [03:30] Budgets, 10 percent time and the reality of making space [07:14] Internal learning, conferences and hackathons [09:01] External training, facilitators and different learning styles [13:14] Conferences, insights and the value of being in the room [17:51] Making learning visible and building a culture around it [20:20] Books, audiobooks, Blinkist and how we actually consume content [25:18] Reflection time, walking, swimming and idea generation [33:03] Helping people choose what to learn next (including AI pressure) [34:25] Rest, burnout, and why taking breaks is part of learning [44:05] Community budgets, experts and learning that sticks [47:09] What we both learned this episode and wrapping up Credits Produced by Unstyled Studios Hosted by Si Jobling & Neil Younger Audio editing by Si Jobling Made with Descript Hosted on Pinecast Check out our podcast host, Pinecast. Start your own podcast for free with no credit card required. If you decide to upgrade, use coupon code r-b0b82e for 40% off for 4 months, and support Managing Engineers. Read transcript

    49 min
  6. 05/11/2025

    Version 2 - The Pilot

    In this pilot episode, Si and Neil get to know each other on mic for the first time. They chat about how they got into software engineering, the early days of web and testing communities, and how their careers shifted into management. There are stories about deleting databases, breaking websites, rediscovering in-person meetups, and what it really means to learn and lead. They also touch on AI, inclusion, and the joy (and nerves) of starting something new. WE'D LOVE YOUR FEEDBACK! Got thoughts on this episode, ideas for future topics, or just want to say hello? Connect with us on LinkedIn: Si - https://www.linkedin.com/in/sijobling/  Neil - https://www.linkedin.com/in/neil-younger/  CHAPTERS [00:00] Setting up and getting comfortable [01:00] Work schedules and the nine-day fortnight [02:00] Who we are and how we got here [08:00] Biggest mistakes in tech (and what we learned) [12:00] Early tech influences and first computers [17:00] The importance of community in tech [20:00] Online vs in-person events [26:00] Skill swaps and learning together [30:00] The power of community in learning [32:00] Talking about AI in software engineering [37:00] How we actually use AI day to day [39:00] The future of AI and education [41:00] What we’re trying to achieve with this podcast [44:00] Learning new tech and making the space comfortable [46:00] Diversity, privilege, and representation in tech [49:00] Planning the first 10 episodes and asking for feedback [52:00] Wrapping up and where to reach us Find out more at http://podcast.managingengineers.net Read transcript

    53 min

À propos

Diving into the subtle art of managing (software) engineers with Si Jobling and Neil Younger.

Plus de contenus par Unstyled Productions