<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress.com" -->
<urlset xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation="http://www.sitemaps.org/schemas/sitemap/0.9 http://www.sitemaps.org/schemas/sitemap/0.9/sitemap.xsd"
	xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
	xmlns:news="http://www.google.com/schemas/sitemap-news/0.9"
	xmlns:image="http://www.google.com/schemas/sitemap-image/1.1"
	>
<url><loc>https://atozofsoftwareengineering.blog/2026/04/26/engineering-leadership-playbook-build-systems-that-scale-%f0%9f%9a%80-engineeringleadership-systemdesign-techleadership/</loc><news:news><news:publication><news:name>A to Z of Software Engineering</news:name><news:language>en</news:language></news:publication><news:publication_date>2026-04-26T05:51:36+00:00</news:publication_date><news:title>Engineering Leadership Playbook: Build Systems That Scale 🚀 #EngineeringLeadership #SystemDesign #TechLeadership</news:title><news:keywords>software development, Cloud Computing, technology, information technology, software engineering, devops best practices, it, software, software developer, software engineer, developer productivity, engineering management, technical leadership skills, engineering leadership, system design leadership, high performance engineering teams, software delivery optimization, team topologies, product engineering execution, reducing technical debt, software engineering systems thinking, scalable software architecture, microservices vs monolith decision, engineering velocity improvement</news:keywords></news:news><image:image><image:loc>https://atozofsoftwareengineering.blog/wp-content/uploads/2026/04/a-to-z-of-software-engineering-69eda687830e7.png?w=150</image:loc></image:image></url></urlset>
