<?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 Abhiram Kaushik on Medium]]></title>
        <description><![CDATA[Stories by Abhiram Kaushik on Medium]]></description>
        <link>https://medium.com/@abhiram.viswamitra?source=rss-e909c0d59562------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*6EEGn40S5mtIuQUIo7K_bg.jpeg</url>
            <title>Stories by Abhiram Kaushik on Medium</title>
            <link>https://medium.com/@abhiram.viswamitra?source=rss-e909c0d59562------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 03:10:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@abhiram.viswamitra/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[Navigating 1:1s]]></title>
            <link>https://medium.com/@abhiram.viswamitra/navigating-1-1s-2468a11b2400?source=rss-e909c0d59562------2</link>
            <guid isPermaLink="false">https://medium.com/p/2468a11b2400</guid>
            <category><![CDATA[engineering-management]]></category>
            <category><![CDATA[1-on-1]]></category>
            <dc:creator><![CDATA[Abhiram Kaushik]]></dc:creator>
            <pubDate>Sat, 11 Sep 2021 17:33:21 GMT</pubDate>
            <atom:updated>2021-09-11T17:33:21.175Z</atom:updated>
            <content:encoded><![CDATA[<p>One of the main traits of being a good Engineering Manager is to know the pulse of your team. You need to know how your team is doing as a unit, and also how each individual is doing. Catching up with your team regularly will give the manager a fair idea about the team, and also help establish a connect with them. In this post, I discuss some points about 1:1s and this is both for Engineering Managers and Team Members.</p><h3>Who owns the 1:1s</h3><p>1:1s isn’t just the manager’s responsibility. It is equally the team’s responsibility as well. Both the team and the manager can drive the agenda of the 1:1. Although a format or a structure would definitely help in coming up prepared for the 1:1. The team members shouldn’t assume that it’s completely manager’s responsibility to drive the meeting. This meeting is a two way street.</p><h3>What gets discussed in a 1:1</h3><p>1:1s shouldn’t become only boring project updates, they should also be the forum to discuss beyond work. It can be a peek into your personal life as well. Knowing the personal side of a team member can make you more empathetic as a manager. My 1:1s are set for 20–30 minutes each, I do a quick discussion of how things are going at work, and then I leave the next 10–15 minutes to discuss anything under the sun.</p><h3>My 1:1 format</h3><p>I do 1:1s with my team members once every two weeks. I keep track of my 1:1s with a sheet shared with all my team members. For example, if my team member is A, I’d share a sheet with them titled <em>A/Abhiram</em>, where I keep track of ongoing 1:1s with A. Keeping all 1:1s as a timeline will give both me and the team member A a view into the progress we have made so far. Here are the things I usually discuss in my 1:1.</p><ul><li><strong>Project/Product updates</strong>: Quick update on how things are going, any blockers or callouts.</li><li><strong>Engineering &amp; Process updates</strong>: Get feedback on how the team is doing with respect to the engineering practices set in the team, to identify any scope for improvements and contributions.</li><li><strong>Feedback</strong>: Straight and candid feedback, if the feedback is given because of a specific incident in mind, then letting them know that it is the case. Basically be straight forward and open about feedback. Also this is also an opportunity to get feedback from the team as well.</li><li><strong>Action Items</strong>: Action items that need to be done by both parties to address the feedback mentioned above.</li><li><strong>Others</strong>: Any other items, that needs to be discussed.</li></ul><p>I encourage the team to keep adding notes in the document and we can discuss them during our 1:1s. Catching up with the team is not just limited to these meetings, however a consistent cadence needs to be set to get the momentum going.</p><h3>Frequency</h3><p>There is no set frequency for the 1:1s. Set up something that works for both of you. Ideally there should be a meeting at least once a month. Being consistent is important. Once in a while, you may not be able to make it, and that is fine. But if you see either cancelling the meetings, then call it out.</p><p>No matter what your structure is for doing 1:1s, if you keep them consistent, it is a great way to keep in touch with the team. If you have any other format or structure that you see has worked for you, let me know in the comments.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2468a11b2400" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beyond Interviews]]></title>
            <link>https://medium.com/@abhiram.viswamitra/beyond-interviews-1f45c0a632fd?source=rss-e909c0d59562------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f45c0a632fd</guid>
            <category><![CDATA[developer-stories]]></category>
            <category><![CDATA[tech-culture]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[interview]]></category>
            <dc:creator><![CDATA[Abhiram Kaushik]]></dc:creator>
            <pubDate>Mon, 31 Aug 2020 18:53:49 GMT</pubDate>
            <atom:updated>2020-09-02T05:36:45.811Z</atom:updated>
            <content:encoded><![CDATA[<p>There are so many Software Engineer interview preparation posts and courses available in the internet/social media platforms for freshers. Almost all of them deal with how to to crack the interview process (Problem Solving, Data Structures, Algorithms, Machine Coding, System Design &amp; Architecture) and get your dream job.</p><p>But what lies beyond? What does it take to do well at your job as a Software Engineer? These are some of the points that I believe can help you become a better Software Engineer.</p><h4>Be Nice</h4><p>This is rule #1. Do not be an asshole. Be nice to your team mates, be nice to fellow employees, and be nice to the people you work with. Toxic “10x” engineers destroy teams in the long run. Building great software is a team effort, and is seldom accomplished alone.</p><p>The more you grow and gain experience, the more important it is for you to NOT be an unpleasant person to work with. Be kind to your fellow team members, be empathetic, and help out when someone reaches out to you without condescending or belittling them.</p><h4>Communicate</h4><p>One of the primary skills that you need to pick up on the job is how to communicate well with others. Based on your scope and responsibilities, you will have to deal with a wide spectrum of stakeholders ranging from fellow engineers in your team to external product stakeholders. Learning to express your thoughts clearly in mails or in meetings will help get the point across.</p><h4>Understand the bigger picture</h4><p>The day to day work of a software engineer, does not involve solving disparate input/output problems, the likes of which you would have prepared on various competitive programming platforms. While it hones a specific necessary skillset, it is not sufficient.</p><p>Whenever you are solving a problem, always try to understand the intent behind solving it, and what impact it has on your consumers and stakeholders. Most of the fresh engineers try to immediately jump to solving the problem to the spec. Sometimes we have to resist the itch to immediately get into problem solving mode, but rather take a step back and see the bigger picture.</p><h4>Automate/Make things better</h4><p>The underlying overarching principle in building software is automation. Look out for opportunities and identify processes where you think you or your systems are spending time doing repetitive tasks. Figuring out ways to automate these tasks and then sharing these with the team will boost your productivity, and enable you to focus on things that are more important. Always try to leave things better than you find them.</p><h4>Contribute beyond your team</h4><p>If you have some free time in your hands after sufficiently tending to your team, look for opportunities to contribute at an organisational level. Pick up projects that help give you perspective beyond your team. Working with diverse set of stakeholders and verticals is a wealth of experience in itself. Try to branch out as much as possible and experiment and do things that catch your eye.</p><h4>Don’t look for instant gratification</h4><p>One thing that fresh out of college hires have is a massive prejudice about what teams/work is fancy and what is boring. Patience. It is quite natural to want to be a part of the team that does the best work. However, you would soon realise that all the teams have interesting problems to solve, and the avenues to learn are everywhere. You can contribute to making things better in any team, and each team has it’s own learning curve. Be patient and try to get learnings from all sorts of experiences.</p><p>This list is by no means exhaustive. These are the lessons I learnt that I found worth sharing. Let me know if there is something that helped you become a better Software Engineer!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f45c0a632fd" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>