<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Engineering-Management on {IT}</title><link>https://igortkanov.com/people/engineering-management/</link><description>Recent content in Engineering-Management on {IT}</description><generator>Hugo</generator><language>en-us</language><copyright>Copyright © 2026 {IT}. All rights reserved. Unless otherwise stated, all text, images, diagrams, and other original content on this blog may not be reproduced, distributed, or used without prior written permission.</copyright><lastBuildDate>Thu, 12 Jun 2025 14:27:01 +0000</lastBuildDate><atom:link href="https://igortkanov.com/people/engineering-management/index.xml" rel="self" type="application/rss+xml"/><item><title>A pint with Jimothy: on fear, ego, and hiring smarter</title><link>https://igortkanov.com/a-pint-with-jimothy-on-fear-ego-and-hiring-smarter/</link><pubDate>Thu, 12 Jun 2025 14:27:01 +0000</pubDate><guid>https://igortkanov.com/a-pint-with-jimothy-on-fear-ego-and-hiring-smarter/</guid><description>&lt;p&gt;☕️ We started with coffee, like most chats do. Black for me, cappuccino for Jimothy (he actually prefers Jim, or James). Corner terrace, Singelgracht. One of those confusing Amsterdam afternoons where the sky can’t decide – sunlight breaks through the clouds, then ducks back behind them. Just long enough to let a few leaves blow across the wet stone.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://igortkanov.com/a-pint-with-jimothy-on-fear-ego-and-hiring-smarter/DSC04367-copy-1024x396.jpg" alt="Autumn leaves" loading="lazy"&gt;&lt;/p&gt;
&lt;p&gt;Jim’s good at what he does. Senior technical manager at a mid-sized SaaS company. Knows the systems, understands the roadmap, has decent rapport with his engineers. But somewhere between the first sip and the second, he leans in and says quietly:&lt;/p&gt;</description></item><item><title>When Slack starts to feel like a DDoS attack</title><link>https://igortkanov.com/when-slack-starts-to-feel-like-a-ddos-attack/</link><pubDate>Wed, 07 May 2025 16:53:49 +0000</pubDate><guid>https://igortkanov.com/when-slack-starts-to-feel-like-a-ddos-attack/</guid><description>&lt;p&gt;In software engineering, we often rely on “exponential back-off” when retrying failed network requests – a technique where each subsequent attempt is spaced out further in time &lt;strong&gt;to avoid overloading the system&lt;/strong&gt;. Oddly enough, I’ve found myself applying a similar concept to human communication.&lt;/p&gt;
&lt;p&gt;As an Engineering lead, I’m frequently on the receiving end of an unrelenting stream of requests:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A Slack ping about a pressing issue&lt;/li&gt;
&lt;li&gt;A pull request to review&lt;/li&gt;
&lt;li&gt;A CV from a recruiter&lt;/li&gt;
&lt;li&gt;Another CV for a completely different role&lt;/li&gt;
&lt;li&gt;A message from customer support about an urgent user complaint&lt;/li&gt;
&lt;li&gt;An escalation from the Security team&lt;/li&gt;
&lt;li&gt;A calendar invite&lt;/li&gt;
&lt;li&gt;A last-moment meeting reschedule&lt;/li&gt;
&lt;li&gt;A &lt;em&gt;quick question&lt;/em&gt; (this one’s my favorite)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;All of this happens while I’m trying to carve out focused time to work on broader goals: improving team processes, ensuring teams have clear direction, and writing progress reports or strategic documentation. Even with AI-assisted tools, writing takes time – because effective communication requires tailoring the message to its audience. Tone matters. Clarity matters. Accuracy matters.&lt;/p&gt;</description></item><item><title>AI for Engineering managers: adapt now or trail behind</title><link>https://igortkanov.com/engineering-managers-the-future-is-here/</link><pubDate>Sat, 19 Apr 2025 15:43:11 +0000</pubDate><guid>https://igortkanov.com/engineering-managers-the-future-is-here/</guid><description>&lt;blockquote&gt;
&lt;p&gt;Remember when a five‑digit Stack Overflow score was a flex?&lt;/p&gt;
&lt;p&gt;Today that, and a vintage 2022 playbook will buy you precisely &lt;em&gt;zero&lt;/em&gt; leverage.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;hr&gt;
&lt;h2 id="yesterdays-job-tomorrows-irrelevance"&gt;Yesterday&amp;rsquo;s job, tomorrow&amp;rsquo;s irrelevance&lt;/h2&gt;
&lt;p&gt;Many Engineering managers still run on three rituals:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Status ✨astrology✨&lt;/strong&gt; or endless forecasting of ticket constellations. Hours massaging burndown charts, Jira dashboards, stand‑up forecasts – cargo‑cult evidence that the sprint is &amp;ldquo;on track&amp;rdquo;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Stakeholder &lt;del&gt;appeasement&lt;/del&gt; management&lt;/strong&gt;: slide decks, project reviews, &amp;ldquo;quick syncs&amp;rdquo; to keep exec egos fed and legal teams comfy.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;People babysitting&lt;/strong&gt; – counting story points, asking to update Jira, tolerance checks for burnout, sniffing out AI-powered &lt;em&gt;overemployment&lt;/em&gt;. By the way, did you know of &lt;a href="https://www.reddit.com/r/overemployed/" target="_blank" rel="noopener noreferrer"&gt;r/overemployed&lt;/a&gt;?&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;However, none of those moves the product faster. Meanwhile, AI agents are quietly doing code reviews, generating boilerplate, even writing RFCs. The org chart hasn&amp;rsquo;t noticed – yet.&lt;/p&gt;</description></item><item><title>The unboring NIST SP 800-190</title><link>https://igortkanov.com/the-unboring-nist-sp-800-190/</link><pubDate>Tue, 18 Mar 2025 05:14:00 +0000</pubDate><guid>https://igortkanov.com/the-unboring-nist-sp-800-190/</guid><description>&lt;p&gt;&lt;figure class="alignright" style="max-width:200px"&gt;&lt;img src="https://igortkanov.com/the-unboring-nist-sp-800-190/File_drawing_105-1.png" alt="" width="200" loading="lazy"&gt;&lt;/figure&gt;&lt;/p&gt;
&lt;p&gt;When most of us hear “NIST guidelines”, our first reaction might be “&lt;em&gt;another boring PDF I’ll never open again&lt;/em&gt;”.&lt;/p&gt;
&lt;p&gt;My first encounter with NIST Special Publication 800-190 happened when I was studying for the &lt;a href="https://www.sans.org/cyber-security-courses/cloud-security-devsecops-automation/" target="_blank" rel="noopener noreferrer"&gt;GIAC GCSA&lt;/a&gt; exam, which is focused on DevSecOps and container security. The SP 800-190 is &lt;strong&gt;refreshingly&lt;/strong&gt; &lt;strong&gt;different&lt;/strong&gt;. It isn’t just another checkbox compliance document – it genuinely provides practical, actionable steps to enhance container security posture.&lt;/p&gt;</description></item><item><title>Before you lead: honest questions for aspiring managers</title><link>https://igortkanov.com/before-you-lead-honest-questions-for-aspiring-managers/</link><pubDate>Mon, 13 Jan 2025 04:33:00 +0000</pubDate><guid>https://igortkanov.com/before-you-lead-honest-questions-for-aspiring-managers/</guid><description>&lt;p&gt;So you&amp;rsquo;ve spent years honing your craft as an individual contributor (IC), and now you&amp;rsquo;re &lt;strong&gt;considering a transition to a leadership position&lt;/strong&gt;. The appeal is obvious: greater influence, more responsibility, and a unique chance to shape your organization&amp;rsquo;s trajectory. However, stepping into a lead role comes with challenges that aren&amp;rsquo;t always highlighted in the job description.&lt;/p&gt;
&lt;p&gt;One of the most significant hurdles is the &lt;strong&gt;shift in mindset&lt;/strong&gt; that this move demands. Instead of focusing your energy on perfecting technical solutions or improving your own output, you&amp;rsquo;ll need to foster team dynamics, resolve interpersonal issues, and guide others to success.&lt;/p&gt;</description></item><item><title>Managing time as an Engineering manager</title><link>https://igortkanov.com/managing-time-as-an-engineering-manager/</link><pubDate>Tue, 24 Dec 2024 05:14:00 +0000</pubDate><guid>https://igortkanov.com/managing-time-as-an-engineering-manager/</guid><description>&lt;p&gt;Every Engineering manager knows &lt;em&gt;the feeling&lt;/em&gt;: you wake up already juggling a thousand thoughts, your calendar is a battlefield, and Slack notifications seem endless. It&amp;rsquo;s a chaotic yet rewarding role, one where the pressure to deliver is only rivaled by the satisfaction of seeing your team succeed.&lt;/p&gt;
&lt;p&gt;In 2024, my days as an Engineering manager (EM) were a constant balancing act. I want to share what those days looked like, the challenges I faced, and how I&amp;rsquo;ve since discovered a helpful framework for managing time better in Aviv Ben-Yosef&amp;rsquo;s &amp;ldquo;The Tech Executive Operating System&amp;rdquo; book.&lt;/p&gt;</description></item><item><title>Planning with confidence: high-level estimates in software projects</title><link>https://igortkanov.com/planning-with-confidence-high-level-estimates-in-software-projects/</link><pubDate>Sun, 27 Aug 2023 16:55:26 +0000</pubDate><guid>https://igortkanov.com/planning-with-confidence-high-level-estimates-in-software-projects/</guid><description>&lt;p&gt;It is not always easy or pleasant to talk about estimates. On the one hand, it&amp;rsquo;s a fun activity of trying to look far enough into the future. On the other hand, high-level estimates are often taken as a commitment. It gets shared with the bigger org, the sales organization (read &lt;em&gt;customers&lt;/em&gt;), and ultimately with the company leadership.&lt;/p&gt;
&lt;hr&gt;
&lt;p&gt;High-level estimates in software engineering are &lt;strong&gt;preliminary projections of the time, effort, and resources required to complete a software project&lt;/strong&gt;. These estimates provide a broad overview during the initial planning phase and help stakeholders understand the general scope and feasibility of the project before delving into detailed planning, commitments to customers, and execution. High-level estimates also guide decision-making and resource allocation, setting the foundation for the project&amp;rsquo;s direction and expectations.&lt;/p&gt;</description></item><item><title>The engineering manager role explained</title><link>https://igortkanov.com/the-engineering-manager-role-explained/</link><pubDate>Mon, 26 Sep 2022 22:20:54 +0000</pubDate><guid>https://igortkanov.com/the-engineering-manager-role-explained/</guid><description>&lt;p&gt;Explaining the engineering manager role is not a new subject. Nevertheless, the EM function is often defined differently depending on the company, its size, and even the market it operates. In this post, I offer my version of it, in an attempt to provide a new, valuable perspective.&lt;/p&gt;
&lt;p&gt;&lt;em&gt;Fun fact:&lt;/em&gt; this is the first piece on this blog featuring hand-drawn graphics ✏️&lt;/p&gt;
&lt;h2 id="who-will-find-it-useful"&gt;Who will find it useful&lt;/h2&gt;
&lt;p&gt;The information in this blog post will be helpful to people who collaborate with Engineering managers at work, willing to learn more about the role. For example, software engineering and recruitment professionals, SaaS sales experts, and individuals interested in becoming an EM.&lt;/p&gt;</description></item></channel></rss>