<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Anurag Atri on Medium]]></title>
        <description><![CDATA[Stories by Anurag Atri on Medium]]></description>
        <link>https://medium.com/@atrianurag?source=rss-e41b949e22be------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Ss6XNbeGuI6LQyJBH1Ai-g.jpeg</url>
            <title>Stories by Anurag Atri on Medium</title>
            <link>https://medium.com/@atrianurag?source=rss-e41b949e22be------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:19:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@atrianurag/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Baby steps into Leadership]]></title>
            <link>https://atrianurag.medium.com/baby-steps-into-leadership-f5b3e4f41bcb?source=rss-e41b949e22be------2</link>
            <guid isPermaLink="false">https://medium.com/p/f5b3e4f41bcb</guid>
            <category><![CDATA[tech-leadership]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[influence]]></category>
            <dc:creator><![CDATA[Anurag Atri]]></dc:creator>
            <pubDate>Mon, 25 Apr 2022 21:05:15 GMT</pubDate>
            <atom:updated>2022-04-25T21:05:15.917Z</atom:updated>
            <content:encoded><![CDATA[<h4>Behaviours of budding leaders</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/0*No4IJ9sJjEMRBTCb" /></figure><p>Leadership, whether through leading projects, or in actually leading people is expected in software engineering roles. However, in the absence of guidance on what leadership means, it could be frustrating to find out what you are missing. In this post I talk about what leadership looks like at junior levels (&lt;5 years of experience) in software engineering. I intend this as a guide for engineers to develop leadership attributes, and for managers to identify and coach budding leaders.</p><p>For each leadership attribute below, we will first look at the mindset behind it. This mindset is a core belief that remains unchanged across levels of leadership. We will then discuss which behaviours driven by this mindset that are shown by budding leaders.</p><h3>#1: Leaders bring ideas</h3><h4>Mindset</h4><p>To lead, one first needs to know where they are going. <br>While it is necessary in any technical domain to know “how” to build something, the first sign of a pivot to leadership is having an opinion on “what” to build. What at senior levels of leadership becomes a “vision for the future” starts as small ideas about how to improve things.</p><h4>Behaviours</h4><ul><li>Budding leaders differentiate themselves by developing either a deep technical knowledge, or a deep understanding of user needs. Both of these help them generate ideas, start projects and create a space for themselves to lead.</li><li>Much before they start to influence what their team or organisation does, leaders start to influence their own work. They generate and vouch for ideas they want to work on. Influencing what they work on, instead of just implementing others’ ideas is a key pivot into leadership.</li></ul><h3>#2: Leaders assume broad responsibility</h3><h4>Mindset</h4><p>Leaders are results oriented. They care so deeply about the overall end result that they aren’t satisfied with delivering just their part. Instead, leaders get involved and assume responsibility of any area that needs help.</p><h4>Behaviours</h4><p>In addition to their assigned responsibilities, budding software engineering leaders:</p><ul><li>are often found working in the space where two software components (e.g. client and server), or teams interface. This space often does not have well defined responsibilities, and leaders step up to fill the gap.</li><li>build a mental model of how the whole system works. This equips them with the knowledge necessary to root cause issues, especially when they lie outside of their defined scope.</li></ul><h3>#3: Leaders delegate, with empathy</h3><h4>Mindset</h4><p>Leaders understand that meaningful results are achieved not by individuals, but by teams. While strong engineers usually have high personal throughput, it is the realisation that they cannot do everything, and the understanding of which parts to delegate that sets budding leaders apart. Delegation often starts as a necessity. Budding leaders need to delegate parts of projects to make space for the broader responsibility they assume.</p><p><em>Delegation could be tricky, especially for budding leaders who don’t have formal authority. Use this as a compass to guide your decisions: When done right, delegation creates a win-win scenario. It frees up space and time for the delegator, and creates a growth opportunity for the delegatee.</em></p><h4>Behaviours</h4><ul><li>Budding leaders build good rapport with their team and are often already seen as “mentors” by other engineers. This trust that their team places in them gives them informal authority, which they leverage to delegate effectively.</li></ul><h3>Summary</h3><p>To build leadership muscle:</p><ul><li>Develop deep knowledge and <strong>use it to generate ideas</strong></li><li>Vouch for ideas and <strong>influence your team’s plans</strong></li><li>Hold yourself accountable not just for personal deliverables, but for the <strong>success of the wider effort</strong></li><li>Build rapport and <strong>delegate parts that are beneficial to other team members</strong>.</li></ul><h3>More?</h3><p><em>I’m a tech lead and manager at Google and I write about software engineering, management, leadership and influence. [</em><a href="https://atrianurag.medium.com/about-me-486dfa4ba910"><em>About me</em></a><em>]<br>Please reach out on </em><a href="https://www.linkedin.com/in/atrianurag/"><strong><em>LinkedIn</em></strong></a><em> if you have thoughts on these topics, feedback on this post or any questions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f5b3e4f41bcb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Unique Value: How to get noticed at work]]></title>
            <link>https://atrianurag.medium.com/unique-value-a15eee76d5f2?source=rss-e41b949e22be------2</link>
            <guid isPermaLink="false">https://medium.com/p/a15eee76d5f2</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Anurag Atri]]></dc:creator>
            <pubDate>Sat, 22 Jan 2022 18:54:34 GMT</pubDate>
            <atom:updated>2022-01-24T15:59:13.015Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xya5sJu8v9_1QsvUTJllTA.jpeg" /><figcaption>Get noticed at work by adding unique value</figcaption></figure><p>I joined Google in 2014 as a software engineer on one of the Ads teams in London. As I started to get to know the three other people on my team, one thing quickly became clear. See if you can guess my feelings from the notes I took about my team:</p><p><strong>John</strong>: Tech lead. Bootstrapped this team. Widely regarded as the area expert.<br><strong>Aleksy</strong>: Senior engineer. Wrote a Haskell compiler last weekend (literally)<br><strong>Igor</strong>: Started last quarter. About to ship his first project. ICPC world finalist from Belarus.</p><p><strong>Anurag</strong>: <em>Overwhelmed as fuck.</em></p><p>Naturally, I struggled to find my footing in the team. The other engineers on the team were not only very smart, but also established experts in our area and tech stack. There was hardly any occasion where I could answer a question, or share an opinion without someone else doing so in a much more refined manner.</p><p>Until… About three months after my joining, my team decided to hold a two day hackathon to build a proxy for intercepting browser requests, needed to run some automated tests. One of the tasks in the project was to process a large text file of URLs, and remove the timestamp from each URL that belonged to Google.</p><p>E.g:<br><a href="http://subdomain.ourdomain.com/queryParams/timestamp/filename.js">http://subdomain.domain.com/file.js/queryParams&amp;<strong>timestamp</strong>&amp;params</a></p><p>My TL created a task to write a processor in Java, and they estimated that it would take ~4 hours to do this end to end.</p><p>Now, I had a little secret. My team didn’t know that I have a black belt in regular expressions. Since getting introduced to them in college, I always found them interesting, and applied them wherever I could, sometimes even when I shouldn’t have!<br>Almost everyday I used to give myself text processing puzzles, and would solve them using regexes. So much so that when I typed ‘r’ into Chrome’s address bar, the top suggestion was regex101.com, and not reddit!</p><p>My eyes lit up as soon as I saw the URL conversion problem, and combined with a few GNU utilities came up with this one liner to solve it:</p><pre>cat urls |\ <br>grep -E &quot;https{0,1}:\/\/[a-z]*\.?google\.com&quot; |\ <br>sed -E &#39;s/[&amp;?]?timestamp=[0-9]+//g&#39; &gt; converted_urls</pre><p>It’s been more than eight years, and I still remember Aleksy saying “<em>that’s a scary one-liner you have there</em>”. He found it scary! The person who wrote a Haskell compiler as a side-project last weekend found it scary!</p><p>My team was expectedly happy that I saved them a few engineering hours, but this isn’t really a “happily ever after” kind of a story, and I had to continue working hard to establish myself.</p><p>However, something changed that day. I started to grow more confident in the skillset I brought to the table, and other engineers started to come to me with their Linux/Bash scripting /text processing questions. This happened because I had a <strong>unique</strong> and <strong>valuable</strong> skill.</p><h3>Adding unique value</h3><p>The skills you use to add unique value will depend on your team and project. Since the things you are already good at might not be unique in your situation, use the following tips to find how to add unique value:</p><h4>1. Ask your team / manager</h4><p>Simply asking <em>“What skills could our project/team benefit from”</em> is a great start. Don’t be surprised if people go into thinking mode because teams rarely stop to think about the skills they lack as a group. Your initiative would undoubtedly be appreciated.</p><h4>2. Build ancillary skills</h4><p>Having a repertoire of ancillary skills will significantly increase your chances of adding unique value in many different situations. Here are a few examples of such skills for software engineering like roles:</p><ol><li><strong>Data processing</strong>: Even basic SQL proficiency is surprisingly rare at junior levels, and problems that require SQL rarely have elegant solutions otherwise.</li><li><strong>Documentation</strong>: Tech companies, especially established ones rely heavily on documents to communicate designs and decisions. Ability to produce succinct and helpful documents will quickly get you noticed.</li><li><strong>Release infrastructure</strong>: Above average functional knowledge of your release infrastructure and tools would be a life-saver during rollout emergencies. Your colleagues won’t be able to thank you enough.</li></ol><p>There are many many more skills that supplement coding, the above three examples are just to get you thinking.</p><h4>3. Look for failure patterns</h4><p>History repeats itself, but often when there’s an underlying cause. Look for failure patterns in your team, and the skills it would take to prevent them. Here are a few examples of symptoms, and what skills might be lacking:</p><ol><li><strong>Delayed projects: </strong>Planning, estimation, good coding practices.</li><li><strong>User facing bugs</strong>: Unit/end-to-end testing, refactoring, pushing back on requirements.</li><li><strong>Hero culture</strong>: Documentation, knowledge sharing, mentoring.</li></ol><p><em>Starting on a new job, role or team is hard. An attitude of trying to add unique value has worked well for me at Google. Reach out on </em><a href="https://www.linkedin.com/in/atrianurag/"><em>LinkedIn</em></a><em> if you have other ideas on how to get noticed at work, feedback on this post, or any questions.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a15eee76d5f2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[About me]]></title>
            <link>https://atrianurag.medium.com/about-me-486dfa4ba910?source=rss-e41b949e22be------2</link>
            <guid isPermaLink="false">https://medium.com/p/486dfa4ba910</guid>
            <dc:creator><![CDATA[Anurag Atri]]></dc:creator>
            <pubDate>Fri, 21 Jan 2022 19:05:43 GMT</pubDate>
            <atom:updated>2022-01-21T19:06:30.981Z</atom:updated>
            <content:encoded><![CDATA[<p>Who am I and what am I doing here</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6QT7LycWR29LnEfb" /><figcaption>Lunch at the Google London office on one of the four sunny days of 2021</figcaption></figure><p><strong>What do I do at Google<br></strong>Currently I’m a tech lead and manager on one of the Android Security engineering teams in London.</p><p><strong>Why am I writing on Medium<br></strong>In January 2022 I completed eight years of working at Google. In this time, I have worked in two locations (Hyderabad and London), on four teams (Ads, Play, Payments, Android Security) and in three roles (Software Engineer, Site Reliability Engineer, Tech lead and Manager). Due to moving around so much, I had the privilege of working with many smart and passionate people.<br>Meeting, working with and learning from these people has been the most rewarding part of my journey and I want to share with more people the things I have learnt.</p><p><strong>What topics would I write on<br></strong>Mostly on the things I have learnt at Google. Engineering and management, navigating corporate culture, mentoring, leadership and influence.</p><p><strong>Questions?<br></strong>Yes, please! Feel free to reach out on <a href="https://www.linkedin.com/in/atrianurag/">LinkedIn</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=486dfa4ba910" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>