<?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 Eric Rabinovich on Medium]]></title>
        <description><![CDATA[Stories by Eric Rabinovich on Medium]]></description>
        <link>https://medium.com/@erix999?source=rss-1ba0a0faf862------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*C6xS0u2UgsTSNMsPJmokVQ.jpeg</url>
            <title>Stories by Eric Rabinovich on Medium</title>
            <link>https://medium.com/@erix999?source=rss-1ba0a0faf862------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 16:14:47 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@erix999/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[How to measure and improve success in your engineering team]]></title>
            <link>https://erix999.medium.com/how-to-measure-and-improve-success-in-your-engineering-team-9322142484c7?source=rss-1ba0a0faf862------2</link>
            <guid isPermaLink="false">https://medium.com/p/9322142484c7</guid>
            <category><![CDATA[metrics]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[engineering-culture]]></category>
            <dc:creator><![CDATA[Eric Rabinovich]]></dc:creator>
            <pubDate>Sun, 24 Jan 2021 13:40:17 GMT</pubDate>
            <atom:updated>2021-01-24T13:40:17.318Z</atom:updated>
            <content:encoded><![CDATA[<p>As an engineering leader, senior developer, or founder of a new startup, I want you to take a minute and think — really think — about a project you are currently working on.</p><p>Now, let me ask you four questions about that project:</p><ol><li>What will you consider a huge success?</li><li>What will you consider a massive failure?</li><li>How do you know that you are currently on the right path towards success?</li><li>And my last question is, once finished, how can you tell if you nail what you wanted to achieve?</li></ol><p>As developers or engineering managers, we run many projects — including:</p><ul><li>Moving from one frontend framework to another;</li><li>Replacing our database with a new and shiny one;</li><li>Creating the killer feature that will give us the edge over our competitors.</li></ul><p>But while you are working on a project, how do you know it will actually make a difference? Why are you doing it? And how do you make sure that it won’t feel like wasted time and energy once finished?</p><p>Results-driven culture, impact-driven culture, data-driven development, etc. have the following three fundamental rules you must follow:</p><ol><li>Have a well-defined Key Performance Indicator (KPI);</li><li>Set a goal on that selected KPI;</li><li>Allow your team autonomy and give them ownership of the plan and the execution for reaching that goal.</li></ol><p>Sounds simple, right? And I bet you already have Objectives and Key Results (OKRs), KPIs, and goal-setting processes of some sort. But although these rules are all easy to achieve in a superficial way, they’re much harder to actually get right. For it to work, you need to nail all three of them. So, how can that be done?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*seEhUyV_-leofR3E1CYGwg.jpeg" /></figure><h3>Selecting the right KPI</h3><p>What is a KPI? They are a set of metrics that help you measure and track what you want to achieve.</p><p>However, there is one thing to remember about KPIs that is sometimes missed: remember the ‘K’ in KPI. It stands for ‘Key’. If you have multiple KPIs, then you have many things as your top priority. And if everything is a priority, then nothing is.</p><p>For a project, select only one KPI and aim to improve this metric and nothing else.</p><p>From my experience, successful KPIs follow the following six rules:</p><p><strong>Rule 1 — A KPI should be measurable.</strong> Don’t settle for boolean ‘yes or no’, or something amorphous that you can’t measure. Let’s say that you want to get into fitness. Let me ask you, what does ‘getting into fitness’ mean to you? Is it running a marathon? Is it cycling for three hours without stopping? Is it the ability to lift 50 kilograms? If you can’t measure it over time, or it only has two states of ‘yes or no’, you will not be able to track your progress. This means you cannot ensure that what you are doing is actually pointing you in the right direction.</p><p>When thinking about goals and KPIs, the first thing most people do is think about the goal they want to achieve. Really, you need to do the opposite. Think, instead, about what you want to <strong>change</strong> and how you can measure that. Great! You’ve found your KPI. Now you can attach a goal to it (which we will explore later in the article).</p><p>Let’s go back to the ‘get into fitness’ goal. Without thinking about what ‘getting into fitness’ means to you and how you can measure it, your goal is almost like a wish. There’s nothing wrong with this, but to be proactive in reaching your goals, think about your KPI first. Set a goal second.</p><p><strong>Rule 2 — The meaning of the metric’s direction on your KPI should be obvious.</strong> There should be a clear understanding that your KPI’s direction is either good or bad. It shouldn’t be vague.</p><p><strong>Rule 3 — Your KPI should reflect the value you are trying to bring and not the value’s outcome.</strong> Earnings are the outcome of a great product. Fewer pager duty alerts are the outcome of improved quality in design, code, and testing. Team velocity is the outcome of fewer dependencies and a smoother development experience. It is easy to set the KPI on the value’s outcome, but try to avoid this because the outcome can be achieved in different ways, and it can hide the thing you really want to change.</p><p><strong>Rule 4 — The metric on your KPI should frequently change, at best daily, but no more than weekly.</strong> This is so you can track what you’re doing, and react fast to adjust your plans when things aren’t going according to plan.</p><p><strong>Rule 5 — Your KPI’s metric should be something that you and your team members have the power to move</strong>. If your KPI depends on someone else, it will hurt your team’s ownership and accountability. Replace it with a KPI that has a metric you have direct influence over.</p><p><strong>Rule 6 — The KPI should lead to action and not staleness.</strong> For example, the best way to reduce the number of bad deployments is to not deploy at all. If you choose a defensive KPI, it will lead to fear and staleness, and will not drive your team into action.</p><p>Now, before you can move on to set a goal on your selected KPI, consider the following:</p><ul><li><strong>Check the current status: measure where you are now.</strong> Sounds obvious, right? But not everyone does it. Once you know where you <strong>really</strong> are, everything becomes much easier for you to see where you want to be, and in turn, this improves your goal-setting accuracy.</li><li><strong>Visualize the metric status as much as possible: one dashboard is worth a thousand words.</strong> A hundred ‘What is our current status?’ questions and several boring alignment meetings that waste time for you and the entire team. So put it everywhere. Send an automatic daily email or Slack message to everyone in your team and anyone else who cares and shares your KPI’s current metric status. If you are doing dailies, open the dashboard there as well. The more people that see it, refer to it, and take it into consideration, means the more alignment, commitment, and focus you will get.</li><li><strong>Don’t be afraid to change it if needed.</strong> Yes, you have given it a lot of thought, and you are sure you have found the right KPI — but things tend to change. People change, businesses change and focus shifts. The KPI should serve you, not the other way around. Following the wrong KPI is very disappointing; it’s better to, instead, replace the KPI from time to time and be more agile, than to work hard to move the metric on a KPI no one cares about.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mBxepndQSF2bhVAhJom0EA.jpeg" /></figure><h3>The subtle art of setting goals</h3><p>You have now selected the best KPI for your team that is measurable, and it encapsulates the value you are trying to achieve. So why is setting goals even necessary? Why is defining our KPI not enough?</p><p>The answer is: a KPI isn’t time-based, but a goal is. Time makes everything real and drives engineers to action.</p><h3>Examples</h3><ul><li>The KPI is weekly active users;</li><li>The goal is to double our current status by the end of the year.</li><li>The KPI is the number of completed story points each sprint;</li><li>The goal is to increase it by 30% in the next quarter.</li><li>The KPI is the percentage of our code coverage in new features;</li><li>The goal is to have 85% of code coverage for all new features in the next five deployments.</li></ul><p>Of course, the goal you select is unique to your organization, your business domain, and what <strong>you</strong> consider a success. However, there are some guidelines that can help you.</p><h3>Select a realistic goal</h3><p>Yes, we all want to be great and achieve as much as we can as fast as possible. However, setting unrealistic goals can devastate your team and your company culture. If the goals you are setting just can’t be achieved, two things will happen.</p><ol><li>Firstly, your team will be highly frustrated and will feel a sense of failure. An unrealistic goal will demoralize everyone and make them feel that their hard work is not enough.</li><li>In the long-term, the impact of this will be even worse. People will stop caring. Because you recruited smart people, they will realize that no goal you set can be achieved due to unrealistic expectations. Your team will lose faith and completely ignore your goals.</li></ol><p>Another pattern that has short-term benefits but in the long-term will backfire, is to think, ‘I’ll set a goal which is very high, but I won’t let the team know that if we just reach 50% of it, that would be great.’ This behavior might work for the short-term to achieve the current goal you are working on, but it hurts your team members and it will have the same negative implication on your team’s culture.</p><h3>Easy-to-achieve goals are as bad as unrealistic ones</h3><p>You set manageable goals, your team achieves them every time before the deadline, and everybody is happy, right? What is the problem with that? Well, easy-to-achieve goals have two significant downsides.</p><ol><li><strong>You need a paradigm shift and not more of the same. </strong>Let me explain this with an example. If you are looking to increase your team velocity and set the goal to increase it by 10%, it will merely lead to your team working 10% harder. This is not what you are after. Moving the needle isn’t about just working harder.<strong> </strong>If you really want to make something extraordinary, your goal should be scary at first glance. If you or your team are looking at a goal and immediately know how to achieve it, or your first reaction is ‘OK, we just need to work harder’, then it probably is not challenging enough. Aim for a paradigm shift that will move the needle and not simply result in an increase in hard work.</li><li><strong>No sense of doing something great</strong>. If your team manages to achieve their goal every time, then everything becomes routine and nothing is exciting. When aiming high, it means that sometimes you fail. But this will be worth it once you actually accomplish a challenging goal. Think about your team’s sense of accomplishment and pride, and how awesome you and your team members will feel. Don’t rob this from them. Now ask yourself — which company you would like to work at? A company that pushes you for out-of-the-box thinking and, at times, makes you feel like you are doing something outstanding? Or a company where everything is always fine?</li></ol><h3>Stretch goals are great</h3><p>Setting stretch goals allows you to challenge the team beyond your original and more-realistic goal. Stretch goals also have another vital benefit: the understanding that the better the results, the better the outcome. Most of the time, a goal is just a milestone for a specific time frame, and after reaching that goal, or the time frame passing, your team will continue in the same direction and you’ll set a new goal for the same KPI.</p><p>However, remember that a stretch goal is <strong>not</strong> the original goal. It doesn’t replace it. If your team has achieved the original goal, celebrate, and be as happy as if the stretch goal didn’t exist in the first place.</p><h3>Don’t expect it to rise linearly</h3><p>In most cases, once you ask your team members to do something extraordinary and reach a challenging goal, they may need to take steps back in order to move forward. In engineering terms, they may break things to ensure they run faster in the future. Due to this, it is entirely normal that progress on a graph will not be linear, and it might take some time before you can see the metrics improve. It may even decrease slightly at the start. But hopefully, after a short time, steady growth will be able to be seen.</p><h3>One size doesn’t fit all</h3><p>Suppose you are running three different projects or running four development teams — each with its own KPI. Don’t think that setting the same goal for each project will reduce friction. Some believe that setting the same goal, for example, a 50% increase in every team’s current status, is fair and removes bias. This is not true. Doing so will only lead to frustration and confusion. The difference between projects is too vast for you to set one goal for every team. The team’s members, the challenges they will face, and the team’s experience in solving challenging problems, will all affect the selected goal; so really, no one size fits all. Yes, it means more work for you, but this way, you will have a better chance to achieve what you are after.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dGxL8kAMIJBEaLEsPsHfzQ.jpeg" /></figure><h3>Your part as the leader</h3><p>You have selected a KPI and set a goal for your team to reach in a specific time frame. Now, what should you do to support this methodology and embrace this results-driven culture?</p><h3>Connect the team</h3><p>The first thing you need to do as a leader is to connect your team to the KPI and the goal once they’ve been set. Explain to your team members once, then twice (and even more if needed) why the KPI you selected is important for the company and the team, and why reaching the goal you set will actually be significant. Done right, you will see the excitement and engagement of the team, and this will make your job easier when it comes to motivating them and gearing them into action.</p><h3>Give ownership</h3><p>Giving ownership to the team and taking a step back might be the hardest thing leaders have to do, no matter how many years of experience they have in leadership. If you have recruited right and have confidence in your team’s skills, it is time to take a step back and let them face the challenges ahead. Don’t think you know best for every decision. Instead, use your experience to ask the right questions, and help steer them in the right direction.</p><h3>Support your team</h3><p>Taking a step back does not mean fade out. Ask for progress. Have your team present progress periodically and guide them. You can start with doing this once a week and stretch it as you gain confidence in them. Set proper milestones along the way and check-in with your team to make sure they are on track. Mentor your engineers in 1:1s and team meetings, and always offer them support.</p><h3>Demand accountability</h3><p>Ensure that the team understands that once you empower them with the ownership of how to get the job done and reach the goal, they are solely accountable for it. Don’t expect your team, especially if this is a new team, to understand this immediately. Tell them that they need to take into account all the things that might go wrong in the planning phase. Ensure they understand that excuses like ‘We would have reached our goal, but the DevOps team didn’t deploy my Cassandra table’ or ‘We were ready, but my dog ate the unit tests’ will not be accepted. It is on them if it fails or if it succeeds.</p><h3>Measure by the results</h3><p>Measure by the results and not by the effort invested; this is so much easier said than done. It took me a long time to achieve it, and I am still failing at it from time to time. The results set you where you want to be and what your team is trying to achieve. And this is what you should give the highest value while evaluating your team members’ performance. I’m not saying that other criteria doesn’t matter, but results lead to an impact that leads to success. With a KPI and goals in place, measuring your team members becomes a little bit easier.</p><h3>Give credit to the team</h3><p>Some people will find this one obvious. However, I am sure that at least once in your career, you worked so hard on something that then your boss got all the credit for. I bet you can still remember how much that sucked and how demoralized you felt. Don’t be that boss. Don’t take credit for your team’s work. Finding the right KPI and setting the goal are the first steps in the right direction to your project’s success. But the team members that are actually doing the hard work are the real heroes: they deserve the credit for it.</p><h3>Celebrate success!</h3><p>I can’t stress this one enough: don’t forget to celebrate a reached goal. Once we achieve a goal, a new one will be knocking on our door and we will rush to start working on it. Our work is never done and there is always too much to do in a small amount of time. However, it’s so important to stop and celebrate. If this is a project that you are working on by yourself, go and do something you always wanted to do and make this day a memorable one. If your team is working on it together, celebrating success will give everyone a sense of accomplishment, set the bar for future projects, and provide real meaning for all your team’s hard work. Make stupid T-shirts, hats, and stickers. Go and have a drink together. Sing karaoke. Whatever! It will have a hugely positive impact on your team’s culture.</p><h3>Conclusion</h3><p>Moving the needle is not easy. Making great things is not easy. Selecting the right, measurable KPI that captures the value you are trying to bring; setting a challenging yet realistic goal; understanding the leader’s part in this unique culture — none of this is easy. However, when done right (and hopefully this article helps you a bit), these factors can reshape the way you think about the success of your projects and how to measure them along the way. You can make a significant impact on your organization by focusing on your team and ensuring they are on the right path. Help you and your team achieve what <strong>really</strong> matters.</p><p>Good luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9322142484c7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ownership — the secret ingredient]]></title>
            <link>https://medium.com/sears-israel/ownership-the-secret-ingredient-bf01e2b50acb?source=rss-1ba0a0faf862------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf01e2b50acb</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[ownership]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[Eric Rabinovich]]></dc:creator>
            <pubDate>Sat, 14 Jul 2018 15:16:41 GMT</pubDate>
            <atom:updated>2018-07-16T15:23:30.369Z</atom:updated>
            <content:encoded><![CDATA[<p>Recruiting is a process that we take very seriously at our company. We strive to hire the best engineers, the best product managers, and the best designers, and guess what; almost every other company out there does too.</p><p>Last week I re-read a blog post by <a href="https://en.wikipedia.org/wiki/Joel_Spolsky">Joel Spolsky</a> in which he discusses his take on <strong>recruiting</strong>. In the post, <a href="https://www.joelonsoftware.com/2006/10/25/the-guerrilla-guide-to-interviewing-version-30/">The Guerrilla Guide to Interviewing</a>, he talks about how to interview and hire new engineers to your development teams and what you should look for <strong>while you hire</strong>. I believe that this is a must-read for every recruiter. In his post, he mentions only two things that he looks for in an interviewee:</p><ul><li>Is he <strong>smart?</strong></li><li>Can he <strong>get things done?</strong></li></ul><p>Simple right? Although I totally agree with these two key attributes, I will add one more; <strong>ownership. </strong>In this blog post I will try to explain why ownership is so important and how to spot it while recruiting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Cjz3EwM7DZ_FOQxXhtnypg.jpeg" /></figure><h3>So, why is ownership so important?</h3><h4><strong>If you own, you care</strong></h4><p>It is as simple as that. If you own something, whether it is your home, your TV, your technology domain, or that little piece of code you just wrote, you tend to care more about it than anything else. 99% of people will treat their own car better than the car they rent at the airport. People care more about a house they own over one they rent for a year. Once you own something, most likely, you will treat it better.</p><h4><strong>Ownership is about accountability</strong></h4><p>To put this in simple terms, an engineer that feels <strong>accountable </strong>for his deliveries and his domain and welcomes <strong>responsibility </strong>gladly, proves to have strong ownership skills. An engineer that does not do this, well he or she just doesn’t. If all you want to do is to run away from responsibility, or you’re afraid that someone will eventually blame you if something goes wrong, then you will never own anything and you will lack the accountability that your managers look for. <strong>Feeling accountable</strong> for a piece of code you just wrote and for domain you are in charge of makes you walk the extra mile. Here are a few examples of what I consider <em>walking the extra mile:</em></p><ul><li>Improving performance a little more, just because you don’t want your users waiting an <strong>extra half a second.</strong></li><li>Fixing that <strong>annoying bug</strong> that never seems to get priority but bothers you so much.</li><li>Making the user experience awesome even if something breaks by being extra careful about <strong>resiliency and fallback.</strong></li></ul><h4><strong>Ownership tends to extend boundaries</strong></h4><p>If you really care about something being<strong> done right</strong>, like a piece of a code you wrote, in most cases you will start caring about other things as well, and eventually, you might accept <strong>ownership </strong>of them too. You will care about how others handle code reviews, and you might revisit the engineering code review policy. You will care about the relationship between the engineering team and the product team and work to improve it. You may not be able to fix your entire organization, but you will start with the one thing that bothers you and work from there. This may start with your own territory and domain, but this ownership tendency has the ability to grow and <strong>influence globally</strong>, not just locally.</p><h4><strong>Ownership makes great leaders</strong></h4><p>Once you feel ownership and accountability not only towards a code but also for people, then I know that you are on the right path for a <strong>leadership position</strong>. At the end of the day, leaders are responsible for all of the successes and failures of their team, and they should treat their team member as their most <strong>valuable assets</strong>.</p><p>Just as the owner of the domain should feel accountable for the domain’s success and make it the best it can be, a leader should feel the same about his team members and make them the <strong>best </strong>they can be. In a nutshell, this is what <strong>leadership is</strong> really all about.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wCSyQnSv7QcqaSDXEN_BzQ.jpeg" /></figure><h3>How to spot ownership in a candidate?</h3><p>So, I hope I convinced you that ownership is super important and why it is one of the first attributes I search for in a candidate. However, the next major question is how to look for it? How do you know if the interviewee in front of you is an <em>owner </em>or not? Will he/she be the perfect fit for your <strong>company’s culture</strong>, which is already composed of people with strong ownership skills?</p><h4>Care about what you left behind</h4><p>Why did they leave their last company? Was it because they wanted to experience and learn new things? Was it because they joined a startup and they already used all of their funds? Did they just get bored? If not any of these reasons, then why did they decide to leave?</p><p>People leave for many good reasons. I will not get into that now, maybe in a future post, but if you care and you have that <strong>sense of ownership</strong>, leaving your company <strong>should hurt</strong> in almost all cases. Leaving your company is not something you do easily if you care strongly about it. If you feel proud of the work you did and are proud of the people around you, yet you still decide to leave it all behind and look for new opportunities, it should definitely hurt. That does not mean it is not the right decision to leave, however, it should not feel like a trivial thing to do. Leaving for a higher salary, to learn something new, or just because you moved to a new city are all valid reasons to leave. Being <strong>nonchalant</strong> about leaving your company makes me believe that you saw your last work place only as a place that pays your salary every month.</p><p>While recruiting, seek the engineers that shows they <strong>care </strong>about the parts and people they left behind or what will happen to the rest of the company after they leave.</p><h4>Work to change the reality</h4><p>In my interviews, I ask many different questions, I tend to go with the flow and I don’t have a specific list of questions that I normally ask. Having said that, I always ask one particular question in most of my interviews:</p><blockquote>If you were not there, (in the last company) what wouldn’t have happened?</blockquote><p>I ask candidates with over 10 years of experience and junior candidates with only 2 years of experience this same question. The <strong>amount of time</strong> in their role is almost irrelevant, and the answers can vary from, “Our testing framework sucked big time and I came with an idea to replace it and did it,” or it can be something like, “I wanted to make our meeting room names more attractive so I asked the other employees to suggest new names and I changed them.” If a candidate does not give me even one case where he/she <strong>changed the reality</strong> in his/her last position, it automatically raises a red flag for me. Did he/she simply not care that testing takes so long to complete? Did everything work so perfectly that nothing, really nothing, needed to change? But let’s say, in a different situation, that the candidate did change many things and he did care, then this is the time for me to pull out <strong>the big guns </strong>and I ask:</p><blockquote>Give me an example where you asked to change something and your manager\colleagues told you this is not a good idea or will take too long to execute. What did you do about it?</blockquote><p>This creates a great discussion. If someone tells you, “I accepted the manager’s opinion and forgot about it,” then again, this is a red flag. If after 2–3 times he continues to get rejected, and he stops suggesting ideas rather than pursing them, becomes passive, and his passion fades, then he is not going to develop strong ownership skills. You want to see the <strong>passion in the eyes of the candidate</strong>. Good answers vary between, “I pushed my ideas again and again until my manager approved them,” to, “After hearing what my manager explained to me I realized my solution was not optimal, so I went back to the drawing board and fixed my solution,” or even, “I pushed anyway, and I <strong>showed my manager that he was wrong</strong>.” Those are all reasonable answers that can lead to interesting follow up questions.</p><h4>Terminology does matter</h4><p>I know what you are thinking, this is way too nitpicky, but I also listen to the word choice of the candidate carefully. The term <em>them</em> instead of the term <em>us </em>is usually a red flag but it doesn’t automatically disqualify a candidate. <em>Them</em> can refer to the “big” and “scary” teams such as <strong>management or HR</strong> or any other team across the hall for that matter. Why is it important if a candidate separates the world between <em>us </em>and <em>them</em>? The separation is like saying, “Why fix this bad code I just found in our code base when it belongs to them?” or “Okay, production is on fire but this is their problem and I would rather continue to fix a bug that is related to my team but only impacts 0.0000001% of our users”. This shows that they are not keen on teamwork and do not understand that there is a level of<strong> satisfaction </strong>achieved when helping others. You would like to recruit people that feel ownership towards things that affect the <strong>entire organization</strong>, and overall can see the bigger picture of success. If production is down, offer your help to other teams by doing code review because another set of eyes is always beneficial, or at least let them, use you for <a href="https://en.wikipedia.org/wiki/Rubber_duck_debugging">rubber duck debugging</a>.</p><h4>The boy scout rule</h4><p>God, I love this rule, and if you don’t <a href="https://deviq.com/boy-scout-rule/">know it</a>, it goes like this, “Always leave the campground cleaner than you found it. If you find a mess on the ground, you clean it up regardless of who might have made the mess. You intentionally improve the environment for the next group of campers.” How is this applied to software and engineering you may ask? Let me give you a few examples. You write your feature and stumble into an important piece of code that you didn’t write and realize that this code isn’t covered by any tests. What do you do? You try to push into production and there is a flaky test that it is not related to you or your new feature. It fails 2 out of the 3 times it runs, so what do you do? Lastly, you are writing a feature and you see an old code that has never been used, what do you do? I think you understand my point now. You want to hire people who <strong>treat the entire code base as if they wrote all of it themselves</strong> and want to fix any flaky test even if they didn’t write it or make it flaky in the first place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5icpUJt_XYMnQyc6Qe5Dog.jpeg" /></figure><h3>Summary</h3><p>Back to Joel Spolsky’s blog post - I do believe that recruiting people who are <strong>smart </strong>and that <strong>get things done</strong> is very important and I would not compromise those requirements. However, you also want to recruit people who feel that their team’s success, their engineering success, and that their company’s success is also <strong>their own personal success</strong>. You do not want to hire engineers who throw out good ideas but do not have the will or motivation to pull them through. Rather, you want to hire engineers who go <strong>above and beyond</strong> and contribute to the overall <strong>greater picture</strong>.</p><p>What truly shows ownership among a strong candidate is having compassion towards the people you work with, caring about projects that are not only your own, and being passionate about the product you’re working on. Having people that care is so fundamental, and I believe it is one of the <strong>key building blocks</strong> for creating a <strong>healthy and successful engineering culture</strong>.</p><p>I believe that having colleagues who care about their company and are passionate about what they do can help create a great engineering culture. Working among people with the characteristics I described throughout this post is what will make <strong>coming to the office</strong> every morning so much greater.</p><p>Think otherwise? Have more examples or other ways to look for ownership in an interview? Let me know in the comments below.</p><p>And thanks to talented <a href="https://medium.com/u/44c6e773963c">bnaya eshet</a> for the great images.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf01e2b50acb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/sears-israel/ownership-the-secret-ingredient-bf01e2b50acb">Ownership — the secret ingredient</a> was originally published in <a href="https://medium.com/sears-israel">Sears Israel</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>