<?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 Nadia Alramli on Medium]]></title>
        <description><![CDATA[Stories by Nadia Alramli on Medium]]></description>
        <link>https://medium.com/@nadiana?source=rss-baae1765e034------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*HmZ5WTzpaW8aUQ4uSbblHg.jpeg</url>
            <title>Stories by Nadia Alramli on Medium</title>
            <link>https://medium.com/@nadiana?source=rss-baae1765e034------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:45:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nadiana/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[Is Management Right for Me? An Engineer’s Guide to Choosing a Career Path]]></title>
            <link>https://medium.com/hubspot-product/is-management-right-for-me-an-engineers-guide-to-choosing-a-career-path-a61ff17046c1?source=rss-baae1765e034------2</link>
            <guid isPermaLink="false">https://medium.com/p/a61ff17046c1</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[leadership-development]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[career-advice]]></category>
            <dc:creator><![CDATA[Nadia Alramli]]></dc:creator>
            <pubDate>Mon, 08 Nov 2021 16:09:05 GMT</pubDate>
            <atom:updated>2021-11-08T16:09:05.668Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="A figure weighing two question marks, one in each hand" src="https://cdn-images-1.medium.com/max/692/1*j7_-0LUy26HFXJ4JioLPQg.png" /></figure><p><strong>Forget the common wisdom about the skills you need to be a good manager or individual contributor. Instead, ask yourself two questions:</strong></p><ol><li><strong>Do you enjoy helping others fulfill their potential?</strong></li><li><strong>Are you willing to do what it takes to build high-performing teams?</strong></li></ol><p>I came up against the individual contributor (IC) vs. manager choice early in my career.</p><p>I was a senior software engineer who just loved building software. I couldn’t get enough of it. I was a tech lead of a small team when my boss offered me a great promotion opportunity.</p><p>“Do you want to become an engineering manager or a software architect?” he asked.</p><p>I was unsure, but ultimately my boss discouraged me from choosing management, saying it was a waste of my technical skills. He recommended I become an architect. With my technical skills and love of building software, he thought I’d make a solid one.</p><figure><img alt="Individual Contributor Track (Senior Eng to Senior Eng 2 to Staff Engineer to Principle Engineer) vs Management Track (Senior Engineer to Team Lead to Engineering Manager to Director of Engineering)" src="https://cdn-images-1.medium.com/max/453/0*a2-8mQT6GUWZpwXg.png" /></figure><p>Fast-forward to today. I’m a Senior Engineering Director at a fast-growing software company and I manage a team of four managers who together lead a total of 70 engineers. Everyday, I leverage both my technical skills and my ability to help others grow in their careers and do their best work.</p><p>If I’d taken it as absolute truth that my technical skills would be wasted in management, I may have missed out on critical growth and opportunities in my own career. So, how do you make the right decision for yourself?</p><h3>Skill gaps: The false dilemma</h3><p>There are a lot of misconceptions about what it takes to be successful in IC vs. manager roles.</p><p>The most glaring? That you should become an IC if you lack the confidence to take on a leadership role, and conversely, that you should consider management if you aren’t deeply technical and aren’t good at solving challenging technical problems.</p><p>In my experience, this mutually exclusive outlook isn’t accurate, and can lead engineers to stray from the path that would actually bring them the most joy.</p><p>Data backs up the argument against mutual exclusivity, too ⁠ — take this <a href="https://journals.sagepub.com/doi/abs/10.1177/0019793916650451">2017 report on root causes of worker well-being</a>.</p><p>Report authors surveyed 35,000 employees about what factors most impacted their happiness levels at work. Choices ranged from salary, to tenure, to the specific field in which they worked.</p><p>As it turned out, though, the researchers found that the number one indicator of happiness was none of these things.</p><p>It was ‘the boss tech competency.’</p><p>Aka, your boss is capable of doing your job.</p><p>This gets right to the heart of the most common misconception about engineering managers: that they choose this path because they’re not good programmers. If anything, this survey shows that engineers who are skilled <a href="https://product.hubspot.com/blog/hubspots-engineering-leadership-philosophy-part-1?_ga=2.40910944.31801057.1633438983-1572304663.1633438983">programmers make <strong>better managers</strong></a>. This is a truth I experienced firsthand when <a href="https://product.hubspot.com/blog/external-eng-onboarding?_ga=2.40910944.31801057.1633438983-1572304663.1633438983">I embedded directly with our engineers</a> before officially starting my new role at HubSpot as Director of Engineering in 2019.</p><p>When you dig deep enough, you find that the skills required to be a stellar IC and those that make you a remarkable manager are much closer to each other than you think: tech competency, leadership, high-level thinking, problem solving.</p><p>The reality is, a lot of these skills are necessary as you progress in both career tracks, and if you want to advance in both careers you absolutely need to demonstrate some elements of all of these skills. None of them is unique to either path.</p><p>Does that mean that both paths are the same? Of course not!</p><p>Does it mean that if you can do one you can do the other? Also no.</p><p>They are different specializations and will require you to work in different ways. However, <strong>making your choice based on what skills you may or may not have at the moment isn’t the way to choose.</strong></p><p>So, how to choose? It’s all about knowing what questions to ask.</p><h3>Career growth questions</h3><p>First, start with two prerequisite questions:</p><ul><li><strong>Are you a strong performer in your current role?</strong></li></ul><p>Before anything else, if you are not a strong performer at your current role, then the question of career progression is irrelevant. If you are struggling with your current role as a software engineer then your first course is to <a href="https://product.hubspot.com/blog/eight-questions-to-ask-your-manager-to-get-better-feedback">ask for feedback from your manager</a> and address any existing skill and performance gaps.</p><ul><li><strong>Are you ready to take on bigger responsibilities?</strong></li></ul><p>If the answer to this question is no, then it’s too early to think about career progression right now. Whatever path you choose will likely require you to take on bigger projects with higher impact as a first step, so if the idea of taking on more responsibilities makes you uncomfortable right now, then it’s fine to wait.</p><p>However, consider carefully whether your hesitation is coming from a lack of confidence or imposter syndrome. If so, I recommend you find a mentor who can support you on your journey as you build up your confidence. A day will come when you feel more ready to dive in.</p><p>It’s also worth noting that at many companies, trying out a management role is not a one-way street (this is certainly true at HubSpot). It’s common for people at HubSpot to transition from management to IC roles and back again over the course of their career.</p><p>If you can answer both of these questions with a clear yes, then you’re ready to move onto the next set of questions.</p><h3>‘Are you ready to be a manager?’ questions</h3><ul><li><strong>Do you enjoy helping others fulfill their potential? </strong>Do you enjoy helping others grow and find it just as rewarding or even more rewarding than doing the work yourself? This is a key question to consider and a definite requirement for being a manager. If you haven’t tried mentoring others before, you may not know the answer to this, so it’s worth taking on some mentoring opportunities for more junior engineers to find out.</li><li><strong>Are you willing to do what it takes to build high-performing teams?</strong>Are you willing to make hard decisions, deliver tough or awkward feedback and be emotionally available to support your team? Are you willing to do what it takes to build and maintain a high-performing team? No one enjoys having to fire someone, but are you willing to do it if it’s the right thing to do for your team? How you answer this set of questions will show you which career path would be more fulfilling for you. Some example answer combinations, and what they might mean for your preferences, are below:</li><li><strong>If your answer to both questions is YES</strong>, you have the potential to be successful as a manager. If you’re unsure if you would prefer it to an IC role, I recommend you give management a try and see if you enjoy it. You can always switch back if you don’t. There are career levels that run in parallel between management and IC tracks, so there is actually no risk in going to either career path and then switching to a different one later. It’s even a good idea to experiment a bit in the beginning to see what suits you best. At HubSpot, we expect our engineers to switch back and forth between management and IC roles to find what they enjoy the most. A lot of people think they need to be in management to have a big impact or make big decisions, but that’s not true! At the right company you can have just as big of an impact in the senior IC track as in management.</li><li><strong>If you enjoy helping others fulfill their potential but you are not willing or interested in taking on the direct responsibility of maintaining a high performing team,</strong> then I recommend you take on mentoring other engineers (ask your manager for mentoring opportunities and they can find you opportunities even outside the team). Use your mentoring talent to step up your influence and impact as an IC and grow in that career track.</li><li><strong>If you are willing to do what it takes to build a high performing team but don’t enjoy helping others fulfill their potential and grow</strong>, then I would stay away from management roles. It wouldn’t be fair to you or your future team. However, you can leverage your candor and willingness to do what it takes even if it is difficult in your IC work and projects to grow your impact.</li><li><strong>If your answer is NO to both questions</strong>, then the management role isn’t a good fit for you. However, you can have the potential to grow in the IC track as long as you continue to grow your technical skills over time and increase the scope of your projects and their technical complexity. The actions I recommend in the next section also apply to you growing in the IC track.</li><li><strong>If you don’t know the answer to any of these questions</strong>, perhaps you need a bit more time to build more experience, get motivated, and find good role models for the types of roles you’re interested in. You need to find your passion first before considering career progression.</li></ul><h3>Taking action on next steps</h3><p>Once you decide on a career path, what comes next? No matter which path you eventually choose, the recommended steps here are the same.</p><ol><li><strong>Make your intention clear to your manager.</strong> Don’t assume your manager can read your mind. If you have decided to try and grow in a certain direction, make your intention clear to your boss. They are there to help you achieve it. Give them heads up before the conversation that you plan to talk to them about growth so that they can prepare their advice. Ask them to help you identify the areas where you need to work for progression, and ask them for feedback regularly. I suggest scheduling a regular career-focused 1:1 on at least a quarterly basis, maybe even monthly. Work with your manager to create a long-term plan to reach your goals.</li><li><strong>Take on bigger project ownership and responsibility.</strong> No matter what career path you choose, you almost always need to take on bigger projects to progress further. This doesn’t mean you need to work longer hours. It means that the type of projects you are taking on require bigger responsibilities from you. Maybe the project requires working with other teams or solving difficult technical challenges. Or maybe it has a bigger impact or scope. Ask your manager for the type of projects that will help you with your career target.</li><li><strong>Share your learnings with others.</strong> Give talks to your teammates or to other teams about lessons learned, and how your takeaways can be valuable to them, too. Write posts, answer questions, etc. Of course the first benefit of a practice like this is that you’re helping others on their journey, which is amazing. The other hidden benefit is that by sharing your learning you are also making your progression and work more visible to a wider network, including your manager, and increasing your value and impact by helping others. Help others, help yourself.</li></ol><h3>To recap:</h3><p>Your career checklist:</p><ul><li>Are you ready?</li><li>Are you willing to do what it takes for each path?</li><li>To progress:</li><li>State intention,</li><li>Take bigger responsibilities,</li><li>Share learning.</li></ul><p>Implement these practices, and you can break a complex process down into manageable chunks that allow you to make it to the next level in your role, no matter what you want that to look like.</p><p><em>This article originally appeared on </em><a href="https://product.hubspot.com/blog/is-management-right-for-me-an-engineers-guide-to-choosing-a-career-path"><em>HubSpot’s Product Blog</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a61ff17046c1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hubspot-product/is-management-right-for-me-an-engineers-guide-to-choosing-a-career-path-a61ff17046c1">Is Management Right for Me? An Engineer’s Guide to Choosing a Career Path</a> was originally published in <a href="https://medium.com/hubspot-product">HubSpot Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Candidates with Personal Programming Projects Stand Out. Here’s How to Start Your Own]]></title>
            <link>https://medium.com/hubspot-product/candidates-with-personal-programming-projects-stand-out-heres-how-to-start-your-own-d89dbeffc6f6?source=rss-baae1765e034------2</link>
            <guid isPermaLink="false">https://medium.com/p/d89dbeffc6f6</guid>
            <category><![CDATA[projects]]></category>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[career-development]]></category>
            <dc:creator><![CDATA[Nadia Alramli]]></dc:creator>
            <pubDate>Thu, 28 May 2020 14:38:42 GMT</pubDate>
            <atom:updated>2020-05-28T14:38:42.276Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iQsMkODoXkaZJBDRORfp5A.png" /></figure><p>Over six thousand.</p><p>That’s how many internship and co-op candidates we review every year for <a href="https://www.hubspot.com/careers/product-engineering">HubSpot’s Product &amp; Engineering team</a>. We seek a diversity of experience and interests in choosing our final cohort, but there is one thing most of our successful applicants have in common: personal programming projects.</p><p>These projects can take on any form. An app to find the time your next bus is arriving. A chrome extension to hide spoilers for your favorite tv show. The topic doesn’t matter. The initiative it takes to create something does.</p><p>With that in mind, let’s get building! Here are some suggested steps for embarking on your own personal programming project.</p><p><strong>Step 1: Choose Something You Love to Do</strong></p><p>Side projects aren’t only for early-career engineers. Take me, for example.</p><p>In my free time, I love to crochet, which is the art of creating textiles using a hook. But one of the main challenges I faced in the beginning was the human-error factor in crochet pattern designs. Sometimes the directions don’t lead to the desired end result.</p><p>Instead of accepting this as an unavoidable reality of crocheting, I turned to my own experience as an engineer. I could use the tools I had mastered in my everyday work to help me with my hobby. I wrote a Python application that could parse, validate, and generate <a href="https://www.craftybunnybun.com/">crochet patterns</a>, saving me time by catching mistakes before I published them.</p><p>Here’s an example of one of the patterns I created using the code I wrote:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/472/1*vn79pQRTELo8lTJPKzhF_w.png" /></figure><p>This particular pattern is for a specific size of crocheted cube, which, once I stuff it, looks something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/292/1*6hGRm1xkzUGK16xNnhdRLA.jpeg" /></figure><p>Add a few flourishes, and voilá!</p><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/0*-GfRGR3exsVRVR3l" /></figure><p>The final product might seem like it has nothing to do with coding, but writing that application saved me tons of time and trouble. I took something and made it better with engineering.</p><p>So, what do you enjoy doing outside of work? Chances are, there’s a repetitive or error-prone part somewhere in there that you can use your coding skills to improve. Even better, got a cause or a local charity that you support? How about renovating their website or building them a cool mobile app or helping the cause with a project? You would be both supporting your favorite cause and investing in your career!</p><p><strong>Step Two: Find Your Tools and Your Community</strong></p><p>First, set yourself up with a public <a href="https://github.com/">GitHub</a> account (if you’re new to it, here’s a <a href="https://product.hubspot.com/blog/git-and-github-tutorial-for-beginners">guide to getting started with git and GitHub</a>), and start filling it with projects you’ve already completed. If you’re still in college, this is a perfect place for school projects to live. Next, find yourself a community of fellow coders, whether it’s a group of friends or something more formal than that. While it’s perfectly legitimate to work on projects solo, being part of a community can raise your game in ways you might not realize. Being able to bounce ideas off of one another and give each other advice and support can be invaluable.</p><p>If you’re not sure where to start, research hackathons and workshops offered in your area (for when social distancing is over, of course). Several of them have online options, including HubSpot’s <a href="https://product.hubspot.com/blog/building-your-first-web-app-free-coding-course">Build Your First Web App Workshop</a>.</p><p><strong>Step Three: Don’t Be Afraid to Get Started</strong></p><p>Remember, the product you’re building can be anything. It’s not the “what” that matters so much as the “how.” Here are some examples of what teammates of mine have built:</p><ul><li>A blog to to teach beginners how to program</li><li>A chrome extension to hide Game of Thrones spoilers from your Facebook feed</li><li>A scraper to track Netflix watch history and a web app to find the best movies from your favorite actor or actress</li><li>An app to find the time your bus is arriving at the stop nearest you</li></ul><p>Most importantly, your project doesn’t need to be perfect. And here’s a little secret: it doesn’t even need to work. Even a failed project is better than no project. The lessons you learn from that failed project and the fact that you attempted to do it especially if it’s a difficult task make you stand out.</p><p>So get going⁠ — it’s never too late! Spending time on personal projects shows that you’re passionate about learning and growing your programming skills.</p><p>You have boundless potential. It’s time to tap into it.</p><p><em>If working with a team that’s always interested in learning and growing sounds great to you, check out our </em><a href="https://www.hubspot.com/careers/product-engineering"><em>open Product &amp; Engineering positions</em></a><em>.</em></p><p>This piece originally appeared on the <a href="https://product.hubspot.com/blog/personal-programming-projects-beginners-guide">HubSpot Product Blog</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d89dbeffc6f6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hubspot-product/candidates-with-personal-programming-projects-stand-out-heres-how-to-start-your-own-d89dbeffc6f6">Candidates with Personal Programming Projects Stand Out. Here’s How to Start Your Own</a> was originally published in <a href="https://medium.com/hubspot-product">HubSpot Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Became A Director of Engineering at HubSpot]]></title>
            <link>https://medium.com/hubspot-product/how-i-became-a-director-of-engineering-at-hubspot-3b26c71b4dab?source=rss-baae1765e034------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b26c71b4dab</guid>
            <category><![CDATA[recruitment]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[onboarding]]></category>
            <category><![CDATA[leadership-development]]></category>
            <dc:creator><![CDATA[Nadia Alramli]]></dc:creator>
            <pubDate>Mon, 23 Sep 2019 14:07:18 GMT</pubDate>
            <atom:updated>2019-09-23T14:07:18.942Z</atom:updated>
            <content:encoded><![CDATA[<h4>(By Becoming A Software Engineer Again)</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*13XBSsW0BGuxVNLsreppZQ.png" /></figure><p>Before joining HubSpot, I had been at my previous job for 11 years. I had worked my way up from software engineer to senior director of product engineering. During that time, I benefited from all of the technical expertise and context that growing in the same company for over a decade affords you. I had truly helped build the products there from the ground up.</p><p>When I was approached about the position at HubSpot, I was excited about the idea of doing things differently and learning something new. At the same time, I was concerned about starting in a leadership role at a different company where I didn’t have the strong technical domain experience that I’d leaned on before. It wasn’t until I was further along in the application process, though, that I got truly hooked on the idea of working for HubSpot.</p><p>That was when I learned about <a href="https://product.hubspot.com/blog/onboarding-external-engineering-leaders">HubSpot’s engineering onboarding process</a>. Every external engineering leader hired at HubSpot goes through an “Embedding Process” for their first several months. During that period, they are treated exactly the same as any software engineer joining the team. No privileged access to information, no managerial responsibilities, no expectations beyond being a software engineer. They take the same training courses and go through the same onboarding process as everyone else. After that, they’re “embedded,” working as a software engineer switching between different teams and disciplines for time periods ranging from a couple of months to a couple of weeks. The whole process takes five to six months.</p><p>When I was hired, I was excited to go through this experience, though not without a healthy dose of nerves. I’d heard of other companies like Google and Facebook approaching leadership hiring in this way, but I’d never been through a process even remotely similar.</p><p>Now, I’m on the other side. I’m finished with my embedding and am transitioning into my role as an engineering director. Through the process, I had the chance to work with eight teams over a six month period, both in my home office in Dublin and in HubSpot’s headquarters in Cambridge. I met amazing engineers across the company and learned a lot about who I wanted to be as a leader at HubSpot.</p><p>Here are some of my takeaways.</p><h4>Be Curious</h4><p>In the beginning of the process, the hired engineering lead only has access to the same information as their software engineer peers on the team. No leadership documents or slack channels, no email exchanges between directors. At first, this was difficult to get used to. From my old job, I was used to looking at things from a leadership level and trying to solve for the team. The engineering SVP running the embedding program told me, “You’re going to itch to take on leadership responsibilities, but don’t do it. The team needs you to be where you are right now.”</p><p>That made an impression on me. There was a lot to be learned, it turned out, from being cut off from the leadership information flow in the beginning. It made it clear to me where engineers’ blindspots were. It also meant that I was truly starting at square one. On a scale of zero to ten, my curiosity meter is at a 15 at all times, so I needed to get my information elsewhere, and that meant my teammates. Every person on the teams I worked with mentored me and answered my questions. I found that they grew more comfortable with me as soon as they saw that every question I asked came from a place of genuine curiosity and a desire to get better.</p><p>My curiosity often took me on the hunt for information. It didn’t stop with my teams or projects, either. I had a wonderful journey learning from people in various functions — from shadowing customer support calls, to learning about UX design and product management best practices. I would come to every meeting with a list of questions and often leave with a list of names for people I could contact to learn more about each topic.</p><p>This endless curiosity proved essential to my embedding process and I continued to carry it with me after settling into my leadership role.</p><h4>Resist imposter syndrome</h4><p>One of the hard truths of embedding is that, even though you’re a strong engineering leader and that’s why you’ve been hired, you’re not necessarily going to be a great engineer.</p><p>For most of us going through this process, it’s been a long time since we started our careers as software engineers. My specialty is backend distributed systems, and here I was embedding with frontend teams just as often as backend ones. Everything has changed so much in the frontend space over the past 10 years that what little experience I do have there was irrelevant.</p><p>That was a huge struggle for me. I was ok with making some mistakes, but I wanted to show that I was pulling my weight for my team and getting everything done. There were times when I felt like I didn’t know anything. When those hard times hit, my team was always there for me. They’d say, “Nadia, we’ve all gone through the same troubles before. It took us a long time to get around problems like this, too.”</p><h4>It’s not all about the tech stack</h4><p>Maybe the biggest misconception about an experience like this is that companies do it because they want external engineering hires to spend time in the trenches learning the tech stack.</p><p>While this is one of the reasons behind the embedding process, it’s far from the most important. Yes, my embedding experience was a great way for me to learn the intricacies of HubSpot’s tech stack, and the time spent learning our product details and guiding principles was incredibly helpful. But the most invaluable part of the experience was the relationships I built with my fellow engineers.</p><p>By the end of each embedding, the engineers on my team weren’t intimidated by me. I was one of them. They corrected my mistakes, they taught me things I didn’t know. I made close friendships where people could be honest with me, joke with me, mess around. Most importantly, I have an empathy for them that I’m going to carry into my leadership role. If I’d been thrown into my role right away, we wouldn’t have had the time to build that trust.</p><h4>Go out of your comfort zone</h4><p>As I mentioned earlier, my experience before HubSpot was on backend distributed systems. So naturally I was most comfortable when embedding on backend teams. However, I resisted the temptation to stay in my comfort zone. That meant going out of my way to ensure that I was embedding on an equal number of frontend teams where possible and taking on a variety of tasks to ensure as much exposure to new challenges as possible.</p><p>In some cases, I bit off more than I could chew, and on one occasion I had to give up the task that was assigned to me. However, that didn’t stop me from pushing over and over again to challenge myself in new areas with varied projects. It was important to me to experience as much as I could during that period, including the use of our various development tools and experiencing any challenges or difficulties first hand.</p><p>All in all, I could not be more grateful to have gone through this process for my first six months at HubSpot. As a leader here, you’re responsible for a large span of projects, and specific domain expertise is not necessarily relevant to the problem at hand. It’s important to have a handle on the whole tech ecosystem at the company so you’re able to innovate from within the pre-existing infrastructure, and it’s also priceless to spend the time on the ground as a member of the team in order to build trust with the people you’re eventually going to be managing.</p><p>The fact that HubSpot is making such an investment in onboarding engineering leaders is a testimony to how it strives to create an excellent employee experience at all levels. New managers go through a more thoughtful, in-depth training experience coming in, and employees get a more empathetic and adaptive leader as a result.</p><p>You may be coming in as an expert, but there’s so much more to learn.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b26c71b4dab" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hubspot-product/how-i-became-a-director-of-engineering-at-hubspot-3b26c71b4dab">How I Became A Director of Engineering at HubSpot</a> was originally published in <a href="https://medium.com/hubspot-product">HubSpot Product</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>