<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Career-Transition on guy@secdev.uk</title>
    <link>https://www.secdev.uk/blog/tags/career-transition/</link>
    <description>Recent content in Career-Transition on guy@secdev.uk</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <copyright>Guy Dixon | guy@secdev.uk</copyright>
    <lastBuildDate>Mon, 28 Jul 2025 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.secdev.uk/blog/tags/career-transition/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The Accidental Manager: Leading When You Didn&#39;t Plan To</title>
      <link>https://www.secdev.uk/blog/leadership/2.10-the-accidental-manager/</link>
      <pubDate>Mon, 28 Jul 2025 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/2.10-the-accidental-manager/</guid>
      <description>&lt;p&gt;Not every manager chose to be one. Sometimes the team grows around you and suddenly you&amp;rsquo;re the most senior person. Sometimes your manager leaves and someone needs to fill the gap. Sometimes the company is too small to hire a dedicated manager, and you&amp;rsquo;re the engineer who seems most capable of doing it alongside your technical work.&lt;/p&gt;&#xA;&lt;p&gt;However it happens, you find yourself managing people without ever having made a deliberate decision to pursue management. And the question you&amp;rsquo;re left with is: now what?&lt;/p&gt;</description>
    </item>
    <item>
      <title>When You Miss Writing Code</title>
      <link>https://www.secdev.uk/blog/leadership/2.9-when-you-miss-writing-code/</link>
      <pubDate>Mon, 07 Jul 2025 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/2.9-when-you-miss-writing-code/</guid>
      <description>&lt;p&gt;There&amp;rsquo;s a particular kind of melancholy that hits engineering managers around the six-month mark. You&amp;rsquo;re in your fourth meeting of the day, you&amp;rsquo;ve just spent an hour on a spreadsheet, and you glance over at your team, heads down, headphones on, deep in the flow state you remember so well. And you think: I miss that.&lt;/p&gt;&#xA;&lt;p&gt;I still feel it. After all these years, there are days when I&amp;rsquo;d trade every meeting on my calendar for four uninterrupted hours with a codebase and a problem to solve. The feeling doesn&amp;rsquo;t go away. But understanding it, what it actually is, and what to do with it, makes it manageable.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Trap of Doing Two Jobs</title>
      <link>https://www.secdev.uk/blog/leadership/2.7-the-trap-of-doing-two-jobs/</link>
      <pubDate>Mon, 26 May 2025 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/2.7-the-trap-of-doing-two-jobs/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve fallen into this trap more than once. You get promoted, you take on the new responsibilities, and you keep doing the old ones too. Not because anyone asked you to, but because the old work is familiar, you&amp;rsquo;re good at it, and there&amp;rsquo;s a voice in your head saying &amp;ldquo;if I don&amp;rsquo;t do this, it won&amp;rsquo;t get done right.&amp;rdquo;&lt;/p&gt;&#xA;&lt;p&gt;That voice is wrong. Or rather, it might be right in the short term, but it&amp;rsquo;s catastrophically wrong in the medium term. Doing two jobs doesn&amp;rsquo;t make you indispensable, it makes you a bottleneck, and it prevents your team from growing into the space you&amp;rsquo;re supposed to have vacated.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Managing Former Peers</title>
      <link>https://www.secdev.uk/blog/leadership/2.6-managing-former-peers/</link>
      <pubDate>Mon, 05 May 2025 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/2.6-managing-former-peers/</guid>
      <description>&lt;p&gt;There&amp;rsquo;s a particular kind of awkwardness that comes with being promoted above people you used to sit next to as equals. Yesterday you were peers, debating technical approaches over coffee. Today you&amp;rsquo;re their boss, responsible for their performance reviews, their career development, and potentially their continued employment. The relationship has fundamentally changed, and pretending otherwise is the worst thing you can do.&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been on both sides of this, promoted above peers, and managed by someone who used to be my equal. Neither side is comfortable, and both require deliberate effort to navigate well.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Your First 90 Days as an Engineering Leader</title>
      <link>https://www.secdev.uk/blog/leadership/2.5-your-first-90-days-as-an-engineering-leader/</link>
      <pubDate>Mon, 14 Apr 2025 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/2.5-your-first-90-days-as-an-engineering-leader/</guid>
      <description>&lt;p&gt;The first 90 days in a new leadership role are simultaneously the most important and the most disorienting period of your tenure. Everything feels urgent. Everyone has opinions about what you should focus on. And the temptation to prove yourself by making immediate changes is almost irresistible.&lt;/p&gt;&#xA;&lt;p&gt;Having started new leadership roles at both start-ups and large corporates, I can tell you that the single most valuable thing you can do in those first 90 days is slow down. Not because urgency isn&amp;rsquo;t real, but because acting on incomplete understanding almost always creates more problems than it solves.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Learning to Delegate (and Why It Feels So Wrong)</title>
      <link>https://www.secdev.uk/blog/leadership/2.4-learning-to-delegate/</link>
      <pubDate>Mon, 24 Mar 2025 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/2.4-learning-to-delegate/</guid>
      <description>&lt;p&gt;Early in my management career, I had a team of six engineers and I was still the person who knew the most about every part of the system. When something urgent came up, I&amp;rsquo;d fix it myself. When a design decision needed making, I&amp;rsquo;d make it. When a PR needed reviewing, I&amp;rsquo;d review it. I was efficient, responsive, and completely unsustainable.&lt;/p&gt;&#xA;&lt;p&gt;It took a holiday, a proper two-week break where I was genuinely unreachable, for me to see the problem. The team didn&amp;rsquo;t fall apart while I was away. But they didn&amp;rsquo;t move forward either. They&amp;rsquo;d been waiting for me on three separate decisions, and nobody felt empowered to make them without my input. I&amp;rsquo;d created a team that was dependent on me, and I&amp;rsquo;d done it by being &amp;ldquo;helpful.&amp;rdquo;&lt;/p&gt;</description>
    </item>
    <item>
      <title>What Nobody Tells You About Being a Tech Lead</title>
      <link>https://www.secdev.uk/blog/leadership/2.2-what-nobody-tells-you-about-being-a-tech-lead/</link>
      <pubDate>Mon, 10 Feb 2025 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/2.2-what-nobody-tells-you-about-being-a-tech-lead/</guid>
      <description>&lt;p&gt;The tech lead role is one of the most misunderstood positions in engineering. It&amp;rsquo;s not a title, it&amp;rsquo;s a set of responsibilities. It&amp;rsquo;s not a promotion, it&amp;rsquo;s a lateral move into a fundamentally different kind of work. And it&amp;rsquo;s where most engineers first discover whether they enjoy leadership, or whether they&amp;rsquo;d rather stay deep in the code.&lt;/p&gt;&#xA;&lt;p&gt;I&amp;rsquo;ve been a tech lead multiple times across my career, and I still think it&amp;rsquo;s the hardest role in engineering. Not because the problems are the most complex technically, but because you&amp;rsquo;re pulled in three directions simultaneously and nobody tells you how to balance them.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Identity Crisis of Becoming a Manager</title>
      <link>https://www.secdev.uk/blog/leadership/2.1-the-identity-crisis-of-becoming-a-manager/</link>
      <pubDate>Mon, 20 Jan 2025 00:00:00 +0000</pubDate>
      <guid>https://www.secdev.uk/blog/leadership/2.1-the-identity-crisis-of-becoming-a-manager/</guid>
      <description>&lt;p&gt;The day I officially became a manager, I still wrote code. The day after that, I still wrote code. For weeks, I kept writing code, attending the same standups, reviewing the same PRs, and fitting &amp;ldquo;management stuff&amp;rdquo; into the gaps. It took me an embarrassingly long time to realise that I hadn&amp;rsquo;t actually changed what I was doing. I&amp;rsquo;d just added a new title to the old job.&lt;/p&gt;&#xA;&lt;p&gt;That&amp;rsquo;s the trap, and nearly everyone falls into it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
