<?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 Medium Engineering on Medium]]></title>
        <description><![CDATA[Stories by Medium Engineering on Medium]]></description>
        <link>https://medium.com/@MediumEng?source=rss-d0bbc53072f4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*melPLM5yc-94hes12VO31g.jpeg</url>
            <title>Stories by Medium Engineering on Medium</title>
            <link>https://medium.com/@MediumEng?source=rss-d0bbc53072f4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 02:06:29 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@MediumEng/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[Engineering growth at Medium]]></title>
            <link>https://medium.engineering/engineering-growth-at-medium-4935b3234d25?source=rss-d0bbc53072f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/4935b3234d25</guid>
            <dc:creator><![CDATA[Medium Engineering]]></dc:creator>
            <pubDate>Mon, 01 Jul 2019 13:21:49 GMT</pubDate>
            <atom:updated>2019-07-01T13:21:49.940Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*HFfC7aZbMiudym0E5ayLwA.png" /></figure><p>Over the years, Medium Engineering <em>(in partnership with our People Operations team)</em> worked to improve the process to evaluate our engineers growth and their impact on the organization. We’ve shared some of our thinking and approach to this process in the past, and are happy to hear that other companies are using their own adaptations of this model!</p><p>As we continue to learn, we are now on our third iteration of this process, and are excited to share with this community some key takeaways. At its core, our mission at Medium is to build the best possible product, so while we won’t be updating this post with each new iteration of our growth framework, we are still engaged in conversations about what it means to grow as an engineer, what increasing scope looks like for different kinds of leaders, and how we can be fair in our evaluation strategy.</p><p>The bullets below give an overview of how we are trying to continuously improve our process so that we can build a robust, flexible, and inclusive team:</p><ul><li>Focus on describing behaviors you can <strong>observe, teach, and evaluate</strong> in your rubric criteria.</li><li>Conversations about growth and impact should be ongoing, and no one should be surprised by information communicated at the time of their assessment.</li><li><a href="https://www.glassdoor.com/research/does-money-buy-happiness-the-link-between-salary-and-employee-satisfaction/">Studies</a> <a href="https://www.upi.com/Science_News/2016/03/10/For-most-a-pay-raise-has-no-effect-on-happiness/6791457646362/">have</a> <a href="https://www.pnas.org/content/107/38/16489.abstract">shown</a> that the positive feelings associated with getting a raise are only temporary, and that long term satisfaction is much more closely tied to personal development. This is another reason why we have chosen to frame our conversations around growth.</li><li>We value a <a href="https://www.mindsetworks.com/science/">growth mindset</a>, and are intentional about this being reflected in our rubric</li><li>Traditional methods of assessing people, and often the language that is used to describe them — ladders, slots, boxes, etc. — are primarily concerned with giving someone a level or categorizing them in some way. We instead craft a framework that centers around the <strong>growth</strong> of an individual, and supports them in the kind of career that they both want to have and that also benefits the business. Therefore, we talk about what others may call a performance assessment in a way that anchors on growth and uses a tool (the rubric) to define how to progress, and how we measure and reward that progress.</li><li>A key measure of success for any assessment system is whether it treats employees equitably, and rewards their work appropriately, regardless of race, gender, age, or any other personal identifiable indicator.</li><li>A strong rubric will incentivize the kinds of behaviors that we want to see in the team, and recognize the different kinds of value that people add.</li><li>It’s important to connect hiring and growth progression to our company values, so we hire, incentivize, and reward what we value throughout the employee lifecycle.</li><li>There are many paths to a successful career, and diverse experiences and strengths together make for a robust and flexible team.</li><li>Titles typically serve three purposes — helping people understand that they are progressing, vesting authority in those people who might not automatically receive it, and communicating an expected competency level to the outside world.</li><li>Execution: The best idea in the world is worthless without great execution. Delivering great software products in teams requires rallying people behind an idea, strong technical leadership throughout the project, a focus on quality, and excellent communication to keep everyone aligned.</li><li>Management: Effective, formal people management is crucial to getting the most out of a team, building for the future, and providing stability during organizational change.</li><li>Ideally, we would have a completely objective rubric, with simple Yes/No decisions made about clear, concrete tasks. This isn’t really possible, but it’s important to get as close as possible. Of course, subjectivity invites the possibility, and likelihood, of bias so an effort needs to be made to ensure the rubric is applied as evenly and fairly as possible.</li><li>How do you capture communication objectively? How do you capture selflessness?</li><li>We base our criteria on scopes of influence, which help paint a picture of how a specific skill can grow over time to impact more people or more surfaces.</li></ul><p>We have learned so much going through this process, and want to thank our community for their questions and conversation on this topic!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4935b3234d25" width="1" height="1" alt=""><hr><p><a href="https://medium.engineering/engineering-growth-at-medium-4935b3234d25">Engineering growth at Medium</a> was originally published in <a href="https://medium.engineering">Medium Engineering</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Wednesday 26 January 2018]]></title>
            <link>https://medium.com/postmortems/wednesday-26-january-2018-3d1e505a9abb?source=rss-d0bbc53072f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/3d1e505a9abb</guid>
            <dc:creator><![CDATA[Medium Engineering]]></dc:creator>
            <pubDate>Mon, 29 Jan 2018 19:32:23 GMT</pubDate>
            <atom:updated>2018-01-31T00:48:06.686Z</atom:updated>
            <content:encoded><![CDATA[<h3>Summary</h3><p>On January 26th, 2018, Medium had a rolling outage from 4:51PM until 5:32PM.</p><h3>Impact</h3><p>A majority of requests to medium.com failed (including visits from a web browser, interactions from our native apps, and API requests).</p><h3>Timeline</h3><ul><li>4:51PM: Server errors began</li><li>5:31PM: A bad cache instance was identified and restarted</li><li>5:32PM: The last sustained server errors ended</li></ul><h3>Root cause</h3><p>At Medium, we run experiments that affect the behavior of the site, the apps, emails, and many other things — all with the goal of refining the Medium experience to make it better for our users. When a server processes a request or handles an event, it checks the status of all running experiments to ensure the correct response is delivered.</p><p>This outage was caused by the failure of a cache that stored metadata for currently running experiments. The resulting surge of requests that failed over to our database were beyond provisioned capacity and requests began to fail.</p><h3>Action taken</h3><p>We have taken steps to ensure that the cache is more resilient against the failures of instances serving hot cache keys.</p><p><em>The Medium Engineering team have committed to publishing a technical postmortem for serious outages to Medium core services, in order to build trust and hold us accountable to our users. </em><a href="https://medium.com/postmortems/public-accountability-5935ed4d5e5a"><em>More background on this program</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3d1e505a9abb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/postmortems/wednesday-26-january-2018-3d1e505a9abb">Wednesday 26 January 2018</a> was originally published in <a href="https://medium.com/postmortems">Postmortems</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Engineering growth: frequently asked questions]]></title>
            <link>https://medium.com/@MediumEng/engineering-growth-frequently-asked-questions-e860b07ca4ab?source=rss-d0bbc53072f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/e860b07ca4ab</guid>
            <category><![CDATA[values]]></category>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Medium Engineering]]></dc:creator>
            <pubDate>Tue, 17 Oct 2017 18:05:33 GMT</pubDate>
            <atom:updated>2019-07-01T13:40:25.720Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>As we continue to learn, we are now on our third iteration of this process. Please see </em><a href="https://medium.engineering/engineering-growth-at-medium-4935b3234d25"><em>here</em></a><em> for the latest update.</em></p><p><em>We recently undertook a project to define professional development for members of Medium’s engineering team. As part of that, I wrote this document to answer some questions that came up during development. It was originally published to Hatch, our internal version of Medium, on August 25, 2017. For more information about Medium’s practice of making internal documents public, see </em><a href="https://medium.com/inside/hatching-inside-medium-5ae60292d655"><em>Hatching Inside Medium</em></a><em>.</em></p><p><em>This is the actual document used by Medium to answer questions our engineers have, and has replaced the version on Hatch as the source of truth.</em></p><p>Preface: <a href="https://medium.com/p/8ba7b78c8d6c">Introduction</a><br>Part 1: <a href="https://medium.com/p/4e02ab330524">Framework overview</a><br>Part 2: <a href="https://medium.com/p/b1fad620787e">Tracks</a><br>Part 3: <a href="https://medium.com/p/743620e70763">Assessing progress</a><br>Part 4: <a href="https://medium.com/p/25a2161ed582">Appeals process</a><br>Part 5: Frequently asked questions</p><p>You can also <a href="https://docs.google.com/spreadsheets/d/1EO-Dbsayn8Nz9Ii3MKcwRbt-EIJ2MjQdpoyhh0tBdZk">read the rubric in full</a>, and <a href="https://snowflake.medium.com">use the interactive tool</a>.</p><p><strong>Q: Do I have to become a manager to grow in this framework?</strong></p><p><em>A: This framework isn’t designed to benefit managers. In fact, that’s something we consciously worked to avoid in creating this framework. We strongly believe that there are many paths for engineers to increase impact, and that leadership comes in many forms. There are different ways for someone to achieve the highest level without needing to formally manage any direct reports, and your group lead can help you create a career plan that works best for you.</em></p><p><strong>Q: What are the different “shapes” of my potential career path at Medium? Examples?</strong></p><p><em>A: There are many different paths for engineers at Medium. Some engineers might have deep spikes in certain tracks, while others might be more well-rounded. While some specific roles will require progress in certain tracks — like </em>Career Development<em> for a group lead — the framework is also flexible. Engineers can make progress in different areas and with our growth tool, you’ll be able to see how progress in different paths will affect your overall level.</em></p><p><em>With the help of your group lead, you can plan career paths that speak to your interests, while increasing your impact at Medium.</em></p><p><strong>Q: Do people at the same level get the same salary? How about equity?</strong></p><p><em>Level-based salary and equity will be the same for all engineers at the same overall level. There may be rare occasions where this is not the case due to external factors or extenuating circumstances.</em></p><p><em>Medium also may periodically offer refresher equity tied to tenure and performance at the company. For that reason, not every engineer at the same level may have the same amount of equity. Medium may in the future choose to offer cash or equity bonuses on a one-time basis. In the event that we do so, we will make that process transparent and fair.</em></p><p><strong>Q: Are we going to publish the salaries for each level?</strong></p><p><em>A: No. Your salaries are not secret, and we expect that people will discuss theirs with each other. However, we don’t plan to publish salaries.</em></p><p><strong>Q: Do we consider prior-Medium experience when assessing engineers? If so, what is the strategy?</strong></p><p><em>A: Many people have experience outside of Medium, which contributes to their overall ability. We wanted to make sure we fairly capture that in this initial progress measurement and with new hires. When making the first assessment for current Medians, we considered what they had done in recent previous roles. However, prior experience was less of a factor the longer someone had been at Medium, as they gained more opportunities to demonstrate their skills firsthand.</em></p><p><strong>Q: How do we assess new hires?</strong></p><p><em>A: We’ll sit down with each new hire and show them the Growth Framework, explaining how we measure the engineering team. In that conversation, the group lead speaking with the candidate will ask for some input on what the candidate has done in their recent previous experience, and what milestones they think they would hit. The hiring committee will make an overall level and provisional milestones determination based on recent relevant experience and a comparison to similar engineers already at Medium.</em></p><p><em>If the candidate accepts the offer, their group lead will share this information in detail. They’ll check in with them at 6 weeks and 3 months to talk about how their work aligns with their milestones on the rubric, and where we expect them to be for their level. At the 3 months point, their milestones will be confirmed.</em></p><p><em>If there is a substantial mismatch with the expected overall level and the observed performance, we will have an honest conversation about remedial steps to bring the engineer up to their assigned level as quickly as possible.</em></p><p><strong>Q: Will I know my milestone in each of the tracks? Will other people?</strong></p><p><em>A: When your group lead shares your growth assessment, they will share your overall level and the milestones you’ve achieved in each track. Although overall levels will be internally public, we are not currently planning to do the same for milestones.</em></p><p><strong>Q: Will I know my percentile of each of the tracks?</strong></p><p><em>A: We don’t currently have plans to share this, but may do so in the future if there’s a compelling reason.</em></p><p><strong>Q: How do we think about tenure for assessment?</strong></p><p><em>A: We do not consider the tenure at Medium as a factor in determining someone’s contributions. The growth rubric focuses on behaviors and deliverables instead of tenure. Inevitably, the longer you are at Medium, the more opportunities you will have to demonstrate your skills and to grow.</em></p><p><strong>Q: Given my personality traits and areas of interest, will I reach a ceiling of my growth at Medium?</strong></p><p><em>A: We are proud that our team is made up of engineers with different personality traits and areas of interest. We want to help you find ways for you to continuously grow in ways that speak to your interests and personality. Medium’s Growth Framework provides multiple opportunities for progress that counts towards your overall level.</em></p><p><em>Each milestone can be achieved through many different types of behaviors or tasks. This means that there are different ways to achieve a milestone, and your group lead can help you identify the best way for you to achieve that next milestone — including helping to advocate for opportunities.</em></p><p><strong>Q: What happens if I do not agree with my milestones or level?</strong></p><p><em>A: We recognize that the review panel may make mistakes from time to time. To address this, we’ve created an appeals process. See details on how to appeal </em><a href="https://medium.com/p/25a2161ed582"><em>here</em></a><em>.</em></p><p><strong>Q: What happens if I think the rubric values the wrong things? Or misses areas that I think are important?</strong></p><p><em>A: We would love to hear your feedback. We’ve created the #eng-growth-framework in Slack and we also have an anonymous feedback form at go/eng-growth-feedback.</em></p><p><strong>Q: Will my level degrade if I switch roles?</strong></p><p><em>A: Our Growth Framework is designed with our engineering values in mind — one of which calls out that roles are not static, and we strive to help people grow and change. You will not lose the points you’ve already gained for switching roles. We may in the future change our approach such that there’s a decrease in points for areas where you aren’t actively using those skills to contribute to the company. We do not currently plan to do that, but if we do, we will provide plenty of notice.</em></p><p><strong>Q: Who determines a person’s level?</strong></p><p><em>A: A review panel comprised of senior engineers determines the current milestones for each engineer using the </em><a href="http://go/eng-growth-rubric"><em>growth rubric</em></a><em>.</em></p><p><strong>Q: Do I have to make progress in every track?</strong></p><p><em>A: Making progress in all tracks at once is highly unlikely. It will typically be more effective to target a couple of tracks, and to work with your group lead to make a career plan that helps you understand which tracks to focus on. You have a whole career to grow :) By focusing on fewer tracks, you can continue to progress in ways that make sense and are achievable. There isn’t an expectation that anyone will make progress on all tracks at once (or get to milestone 5 on all tracks, even in their whole career). We have very senior engineers at the company who have zeros in some tracks!</em></p><p><strong>Q: What if I haven’t done the examples?</strong></p><p><em>A: The examples in the rubric are provided to help give a sense of what type of behaviors we would expect from someone at that milestone. The examples aren’t specific criteria that must be met — instead, they help paint a picture of what type of things someone might do when they’ve achieved that milestone. You can exhibit different behaviors and achieve different tasks of similar complexity, scope, or impact, and still achieve a milestone.</em></p><p><strong>Q: What about cross-functional roles like PM+Eng or Eng+Design?</strong></p><p><em>A: For hybrid work, your growth rubric will correspond to your “home” organization. If you interviewed as an engineer, for example, you are part of the engineering organization unless an explicit change is made. Within this rubric, you may not see as many specific examples of hybrid work, but the examples are not exhaustive. In these cases, we use the overall framing for each level and category and consider how your work fits within each one.</em></p><p><strong>Q: Will the rubric change over time?</strong></p><p><em>A: Yes, we reserve the right to modify the rubric as necessary to meet the needs of the business. We may also make minor changes to examples from time to time, to keep it current. If we make changes that materially affect the usage or outcomes of the rubric, like modifying levels, adding milestones or making milestones substantially harder to achieve, we will give plenty of prior warning.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e860b07ca4ab" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Engineering growth: appeals process]]></title>
            <link>https://medium.com/@MediumEng/engineering-growth-appeals-process-25a2161ed582?source=rss-d0bbc53072f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/25a2161ed582</guid>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[values]]></category>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Medium Engineering]]></dc:creator>
            <pubDate>Tue, 17 Oct 2017 18:05:23 GMT</pubDate>
            <atom:updated>2019-07-01T13:40:47.056Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>As we continue to learn, we are now on our third iteration of this process. Please see </em><a href="https://medium.engineering/engineering-growth-at-medium-4935b3234d25"><em>here</em></a><em> for the latest update.</em></p><p><em>We recently undertook a project to define professional development for members of Medium’s engineering team. As part of that, I wrote this document to describe the appeals process. It was originally published to Hatch, our internal version of Medium, on August 25, 2017. For more information about Medium’s practice of making internal documents public, see </em><a href="https://medium.com/inside/hatching-inside-medium-5ae60292d655"><em>Hatching Inside Medium</em></a><em>.</em></p><p><em>This is the actual document used by Medium to define how the appeals process works, and has replaced the version on Hatch as the source of truth. If you </em><a href="https://medium.engineering/engineering-f7e2dee906be"><em>take a job at Medium</em></a><em>, this is how you can appeal your formal review, should you need to.</em></p><p>Preface: <a href="https://medium.com/p/8ba7b78c8d6c">Introduction</a><br>Part 1: <a href="https://medium.com/p/4e02ab330524">Framework overview</a><br>Part 2: <a href="https://medium.com/p/b1fad620787e">Tracks</a><br>Part 3: <a href="https://medium.com/p/743620e70763">Assessing progress</a><br>Part 4: Appeals process<br>Part 5: <a href="https://medium.com/p/e860b07ca4ab">Frequently asked questions</a></p><p>You can also <a href="https://docs.google.com/spreadsheets/d/1EO-Dbsayn8Nz9Ii3MKcwRbt-EIJ2MjQdpoyhh0tBdZk">read the rubric in full</a>, and <a href="https://snowflake.medium.com">use the interactive tool</a>.</p><p>In rolling out our <a href="http://go/eng-growth-rubric">growth rubric</a>, we’re starting a more formal conversation about growth at Medium. This gives engineers the opportunity to understand the progress they’ve made, how they can progress in the future, and how that translates to their overall level. This is the beginning of our efforts to have more ongoing and intentional conversations with engineers about their growth.</p><p>Using the growth rubric, a review panel determines the current progress measurements for each engineer. This group will formally <a href="ttps://hatch.dm/@majelbstoat/e0d70946fa2d">assess milestone progress</a> every 6 months. The panel is designed to ensure that progress isn’t determined by a single individual — instead, a group of people holistically review an individual’s progress, and determine what milestone they have achieved in each of the 16 tracks.</p><p>We recognize that while the review panel will consider many different inputs and behaviors, its assessment may still sometimes be inaccurate— whether due to a misunderstanding of a project’s complexity, or differing interpretations of a milestone’s requirements. We understand that the framework isn’t perfect, and we will continue to iterate on it over time. With this in mind, it’s important that we provide space for engineers to ask questions, get more context, and request a second consideration of progress and level.</p><p>To support this, we’ve created an appeals process. We think it’s important to have this in place from day one of the new framework, to ensure we start off in the right place, and so that engineers feel empowered to advocate for themselves if their perception differs from that of their initial assessment. In the future, growth will be an ongoing conversation engineers have with their group lead, which we hope will make appeals less necessary. The aim is to have a transparent process where engineers are engaged and involved every step of the way.</p><h4>Appeals Panel</h4><p>Appeals will be reviewed by an appeals panel, some of whom may be on the review panel, but some of whom will not. The appeals panel will have at least one contracted external industry expert to provide a measure of disinterested impartiality.</p><h4>Material Change</h4><p>The appeals panel will only review cases where a change in milestones would lead to an overall level change. This is to avoid overburdening the appeals panel with minor changes that will not have a material impact on level or salary. Depending on the volume of appeals, we may review this rule in the future.</p><h3>Appeals</h3><p>Appealing your assessment is a 5 step process. The window for lodging an appeal is end of day, 3 business days after your assessment is communicated to you. We will try to make allowances if external events prevent you from submitting an appeal within that timeframe.</p><ol><li>Once assessments are made, you’ll have a conversation with your group lead about how your milestones and level have changed. This is a space for you to raise any initial questions or concerns. Your group lead will discuss these with you, provide you more context if necessary, and give you advice on whether an appeal has a realistic chance of success. After that conversation, if milestone measurements still don’t feel accurate, and a favorable outcome would impact your overall level, you can make an appeal for your assessment to be reviewed. You can lodge an appeal, without penalty, even if your group lead doesn’t think it will be successful.</li><li>Gather as much evidence as you can, and fill out <a href="https://goo.gl/forms/DEHJgnq7x0SZkpUo2">this form</a>. This will help highlight information that showcases your achievement in the track(s) you’d like reviewed. For example, you might point to projects you’ve completed and what type of work you contributed. Or, you might point out relationships you’ve developed, and processes you’ve improved. Include anything that contributes to your progress in the track(s). The more specific the better.</li><li>Confirm with your group lead that you’d like to make an appeal. Include the additional info and context you gathered. If you do not feel comfortable raising this with your group lead, you can reach out directly to the head of engineering instead. Doing so will have no negative impact on your appeal, but we encourage you to work with your group lead first, if you can.</li><li>The appeals panel will take another look at your progress, taking into account the additional information you submitted. We’ll also confirm that both HR and your group lead know that your assessment is being reviewed and has the potential to change.</li><li>The appeals panel will make a final decision and will share the outcome with you and your group lead. We will aim to have appeals completed within 1 week of the close of the appeals window, though this may vary with the volume of appeals and the availability of an external industry expert.</li></ol><p>If you have any questions about the appeals process, reach out to your group lead, HR, any other group lead, or the head of engineering.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=25a2161ed582" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Engineering growth: assessing progress]]></title>
            <link>https://medium.com/@MediumEng/engineering-growth-assessing-progress-743620e70763?source=rss-d0bbc53072f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/743620e70763</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[values]]></category>
            <dc:creator><![CDATA[Medium Engineering]]></dc:creator>
            <pubDate>Tue, 17 Oct 2017 18:05:12 GMT</pubDate>
            <atom:updated>2019-07-01T13:41:18.494Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>As we continue to learn, we are now on our third iteration of this process. Please see </em><a href="https://medium.engineering/engineering-growth-at-medium-4935b3234d25?source=post_elevate_sequence_page---------------------------"><em>here</em></a><em> for the latest update.</em></p><p><em>We recently undertook a project to define professional development for members of Medium’s engineering team. As part of that, I wrote this document to explain how milestones are evaluated. It was originally published to Hatch, our internal version of Medium, on August 25, 2017. For more information about Medium’s practice of making internal documents public, see </em><a href="https://medium.com/inside/hatching-inside-medium-5ae60292d655"><em>Hatching Inside Medium</em></a><em>.</em></p><p><em>This is the actual document used by Medium to help understand how we assess progress, and has replaced the version on Hatch as the source of truth. If you </em><a href="https://medium.engineering/engineering-f7e2dee906be"><em>take a job at Medium</em></a><em>, this process is how the review panel will consider your growth during formal assessments.</em></p><p>Preface: <a href="https://medium.com/p/8ba7b78c8d6c">Introduction</a><br>Part 1: <a href="https://medium.com/p/4e02ab330524">Framework overview</a><br>Part 2: <a href="https://medium.com/p/b1fad620787e">Tracks</a><br>Part 3: Assessing progress<br>Part 4: <a href="https://medium.com/p/25a2161ed582">Appeals process</a><br>Part 5: <a href="https://medium.com/p/e860b07ca4ab">Frequently asked questions</a></p><p>You can also <a href="https://docs.google.com/spreadsheets/d/1EO-Dbsayn8Nz9Ii3MKcwRbt-EIJ2MjQdpoyhh0tBdZk">read the rubric in full</a>, and <a href="https://snowflake.medium.com">use the interactive tool</a>.</p><p>At first glance, the growth rubric can be a little overwhelming. There are lots of tracks, and lots of examples. Engineers may be uncertain as to whether they qualify for a given milestone. It is important that everyone be clear on how we judge these milestones as they will directly affect an engineer’s level, and ultimately compensation. We must establish trust in the process and be as consistent as we can, judging people solely on the merits of their contributions.</p><p>This guide is designed to explain how to read the rubric, how to assess progress towards milestones, and how to discuss the framework.</p><p>Before that, some important points:</p><h4>Subjectivity vs objectivity</h4><p>Ideally, we would have a completely objective rubric, with simple Yes/No decisions made about clear, concrete tasks. Of course, this isn’t really possible.</p><p>Even in a team that is as mission-driven as Medium, if we are prescriptive about exactly what counts for credit, human nature says our people will do precisely those actions, and not focus any energy on tasks not defined. We can’t possibly define all the tasks that we want our people to do, and we cannot predict the tasks that we will need our people to do in the future. A fully objective rubric would be brittle, and would incentivize the growth of a team with homogenous skills.</p><p>There are also more intangible behaviours that, while incredibly valuable to the team, cannot adequately be captured by tasks alone. One of the central challenges of valuing knowledge work is that, though the output of building products in teams is actually quite measurable — does the product do what it’s supposed to do? — many of the skills necessary to do so aren’t easily measured. How do you capture <em>communication </em>objectively? How do you capture <em>selflessness?</em></p><p>Of course, subjectivity invites the possibility, and likelihood, of bias. We have to be constantly vigilant and take steps to ensure that we’re applying the rubric evenly. This includes reviewing the overall distribution of level increases made during formal growth assessments, ensuring that the review panel that makes those assessments is broadly representative of the team, being as transparent as possible without compromising privacy, and providing an <a href="https://medium.com/p/25a2161ed582">appeals process</a>.</p><h4>Developing a conversation</h4><p>One of the key ways we hope to reduce the problem of bias is by moving away from all-or-nothing, twice-yearly assessments. We have observed that these are frequently opaque, frustrating and stressful for engineers, who see them as one of a limited number of high-stakes opportunities to demonstrate progress. Medium’s growth framework instead encourages and requires an ongoing conversation between an engineer and their group lead, where growth plans are created and discussed together at regularly scheduled check-ins. To facilitate this, we created an <a href="https://snowflake.medium.com">interactive growth tool</a> that helps visualise how different kinds of progression will affect an engineer’s overall level.</p><p>It is important that the group lead establishes a long-term, trusting relationship with their group members, and takes the time to understand each one’s career goals and personality. Group leads should leverage this understanding to advise them on appropriate tracks for growth. From time to time, they may also have to guide engineers more firmly, either for business reasons, or because they recognise a latent capability that is not being realised. While engineers are in principle free to choose their own path, the realities of building a team and product will sometimes require compromise on their part. This is a healthy thing to discuss as part of career planning.</p><h4>Impact and opportunity</h4><p>Our tracks are framed as increasing in impact, whether that mean complexity, scope, or responsibility. However, impact is very strongly tied to opportunity. In many companies, it is much easier to progress, for example, if you’re directly making the company money. Those not in a position to do so are at a disadvantage.</p><p>Group leads at Medium should be working hard to ensure that members of their group are presented with opportunities to progress. To emphasise this, group leads are specifically incentivised to do so with the <em>Career Development</em> track, which aligns their goals with their group members’.</p><p>We believe that people management is an active endeavour. At the same time, we want our engineers to make their own opportunities. By providing many tracks for progress, we hope they take the initiative to lead in areas that interest them and which are underserved. <em>Instigating Change</em> is a core value of Medium, and engineers are strongly encouraged to do so on behalf of both themselves and the company.</p><p>Should they struggle with this, engineers are expected to advocate for themselves in the regular check-ins, and raise any concerns they have around a lack of opportunity to showcase and develop their skills.</p><h3>Assessment</h3><p>Each track has an overall description, and five milestones. Each milestone has a description, and a set of example behaviours and tasks.</p><p>The examples are only examples. <strong>It is not required that an engineer do the listed tasks, or exhibit all the listed behaviours.</strong> The examples and descriptions are intended to be read together to paint an overall picture of what we might expect from an engineer that has accomplished this milestone.</p><p>We do not wish to promote box-ticking, or to incentivise everyone to do the same work. Engineers should feel free to substitute tasks of equivalent complexity or scope, and group leads should help set expectations as to what qualifies, in consultation with domain experts, using the examples as a guide.</p><h4>The 5 Cs</h4><p>To achieve a milestone, the review panel must have a good faith belief that the engineer has been performing to the appropriate standard. In general, the engineer must have demonstrated a <em>Conscious, Comfortable, Continuous, Consistent Competency</em>, defined as follows:</p><ul><li><strong>Conscious:</strong> having devoted intentional effort to this endeavour,</li><li><strong>Comfortable:</strong> without being overly stretched,</li><li><strong>Continuous:</strong> for a reasonable period of time,</li><li><strong>Consistent:</strong> reliably and evenly,</li><li><strong>Competency:</strong> meeting the criteria.</li></ul><p>As a natural consequence, an engineer does not achieve a milestone the first time they demonstrate relevant behaviours or tasks.</p><p>Overall, if it is not <strong>Clear</strong> that an engineer is at a given milestone, they are at the previous milestone.</p><p>Some engineers may find that they exhibit some of the example behaviours at a later milestone without exhibiting all of the example behaviours at an earlier milestone. This is to be expected. At the earlier stages of an engineer’s career, they are limited to simple contributions. Engineers with more experience can typically contribute in higher leverage ways which supersede those simpler tasks, meaning they no longer do them. It is assumed they could do them, should they be required to.</p><p>However, there are certain fundamentals which engineers should not grow out of. It’s hard to imagine someone progressing very far along the <em>Communication</em> track if they aren’t <em>Collaborating with empathy</em>, even if they are facilitating the communication of entire teams and dozens of people. <em>Writing tests for every patch</em>, for example, is an important behaviour that every engineer should be exhibiting. If there are noticeable gaps at lower levels, engineers should use these as an opportunity for introspection, reflection, and improvement. At senior levels, role modelling becomes very important, and authority, respect, and credit gained from demonstrating the right behaviours is stronger than that merely based on tenure.</p><h4>Cycle</h4><p>In order to minimise the overhead in convening review panels, and on our people and finance teams, we will continue to make formal milestone and level changes at discrete six monthly intervals. However, in the intervening periods, it is expected that group leads will conduct informal progress check-ins with their group members about every six weeks. These check-ins should discuss the tracks along which the group member would like to improve, the kinds of projects and behaviours that would reasonably demonstrate improvement, and ongoing progress towards achieving them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZfjPV7PPH3FjtKzQbLD3Dw.png" /></figure><p>The aim should be that when the formal assessment is made, neither the group lead nor the engineer are surprised by the outcome. To ensure this, group leads should also regularly check-in with other engineering leaders to help understand whether significant enough progress is being made. Of course, the final assessment will still be subjective, but the provision of examples, good cross-team calibration on milestone requirements, and the regular discussion of progress should help alleviate stress around those decisions.</p><p>Formal assessment will be made by a review panel of senior engineers. Group leads are expected to advocate on behalf of their engineers, and make a proposal for milestone and level adjustments, if warranted. The review panel will consider the supplied evidence to support these adjustments, and may — based on their experience, and company knowledge — recommend lower or higher milestones than those suggested.</p><p>At this time, there is no plan to lower milestones established in a previous growth assessment, but we reserve the right to change this — with plenty of notice — in the future, if necessary.</p><h4>Progress</h4><p>Not every engineer will have an overall level change in every cycle, especially given that each milestone and level becomes successively harder to achieve. In situations where an overall level change is not warranted, we hope that formal recognition of improvement along some tracks may still be motivating for engineers, and will encourage them to keep up the effort. This is more likely for senior engineers, for whom overall level changes are typically much harder to achieve than for someone early on in their career.</p><p>Group leads should use the regular check-ins to effectively set expectations, so a senior engineer doesn’t wonder why they appear to be making no visible progress, even as they believe they are improving.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=743620e70763" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Engineering growth: tracks]]></title>
            <link>https://medium.com/@MediumEng/engineering-growth-tracks-b1fad620787e?source=rss-d0bbc53072f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/b1fad620787e</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[values]]></category>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[professional-development]]></category>
            <dc:creator><![CDATA[Medium Engineering]]></dc:creator>
            <pubDate>Tue, 17 Oct 2017 18:04:55 GMT</pubDate>
            <atom:updated>2019-07-01T13:41:32.137Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>As we continue to learn, we are now on our third iteration of this process. Please see </em><a href="https://medium.engineering/engineering-growth-at-medium-4935b3234d25?source=post_elevate_sequence_page---------------------------"><em>here</em></a><em> for the latest update.</em></p><p><em>We recently undertook a project to define professional development for members of Medium’s engineering team. As part of that, I wrote this document to describe the rationale for each assessment track. It was originally published to Hatch, our internal version of Medium, on August 25, 2017. For more information about Medium’s practice of making internal documents public, see </em><a href="https://medium.com/inside/hatching-inside-medium-5ae60292d655"><em>Hatching Inside Medium</em></a><em>.</em></p><p><em>This is the actual document used by Medium to explain the kinds of contributions we value, and has replaced the version on Hatch as the source of truth. If you </em><a href="https://medium.engineering/engineering-f7e2dee906be"><em>take a job at Medium</em></a><em>, these are the areas you can develop in that will contribute to your overall level.</em></p><p>Preface: <a href="https://medium.com/p/8ba7b78c8d6c">Introduction</a><br>Part 1: <a href="https://medium.com/p/4e02ab330524">Framework overview</a><br>Part 2: Tracks<br>Part 3: <a href="https://medium.com/p/743620e70763">Assessing progress</a><br>Part 4: <a href="https://medium.com/p/25a2161ed582">Appeals process</a><br>Part 5: <a href="https://medium.com/p/e860b07ca4ab">Frequently asked questions</a></p><p>You can also <a href="https://docs.google.com/spreadsheets/d/1EO-Dbsayn8Nz9Ii3MKcwRbt-EIJ2MjQdpoyhh0tBdZk">read the rubric in full</a>, and <a href="https://snowflake.medium.com">use the interactive tool</a>.</p><p>Medium’s engineering growth framework defines 16 tracks for progression, grouped into 4 categories. This document defines the rationale for the selection of these tracks.</p><p>The track descriptions are read as being preceded by “An engineer pursuing the ____ track…”, e.g. <em>An engineer pursuing the Mobile track develops expertise in native mobile platform engineering, such as iOS or Android.</em></p><h3>Building</h3><p>Building software is at the core of any engineering organisation. These tracks are concerned with building expertise in the development of high quality production features and supporting infrastructure. We expect engineers to demonstrate empathy for their clients — whether users or colleagues — to understand complex and subtle problems thoroughly, and use their creativity and experience to design appropriate technical solutions.</p><h4>Mobile</h4><p><em>Develops expertise in native mobile platform engineering, such as iOS or Android</em></p><p>Native apps allow us to provide better, more tailored experiences to users. To build those, we need engineers with expertise in iOS and Android, who can help us deliver feature parity across all the platforms we support, and build first class products that blend in seamlessly with platform conventions.</p><h4>Web Client</h4><p><em>Develops expertise in web client technologies, such as HTML, CSS, and JavaScript</em></p><p>We need to provide our users with a modern, responsive web product that renders well across all major browsers. We need engineers with expertise in web client technologies to help us continue to build industry-leading technology like <a href="https://medium.engineering/why-contenteditable-is-terrible-122d8a40e480">our editor</a> and take advantage of new opportunities like AMP.</p><h4>Foundations</h4><p><em>Develops expertise in foundational systems, such as deployments, pipelines, databases and machine learning</em></p><p>A strong infrastructure provides a solid and stable foundation on which to build great products. Organizational excellence here lets us deploy rapidly with confidence, and be robust to systems failure. Engineers with strong database or machine learning skills give us the ability to model and process data in ways that allow us to deliver great experiences to our users.</p><h4>Servers</h4><p><em>Develops expertise in server side engineering, using technologies such as Go, NodeJS, or Scala</em></p><p>Excellent clients are no use if they don’t have a fast and responsive server to communicate with. We need engineers that can help build efficient application services that respond quickly to requests, and provide clean interfaces that can be accessed from multiple different clients.</p><h3>Executing</h3><p>The best idea in the world is worthless without great execution. Delivering great software products in teams requires rallying people behind an idea, strong technical leadership throughout the project, a focus on quality, and excellent communication to keep everyone aligned.</p><h4>Project Management</h4><p><em>Delivers well-scoped programs of work that meet their goals, on time, to budget, harmoniously</em></p><p>There is a limit to what people can achieve individually, and coordination of multiple people on a project is very important. We need people that can take large projects, break them down into achievable milestones, manage and delegate scope effectively, and ensure that deadlines are met.</p><h4>Communication</h4><p><em>Shares the right amount of information with the right people, at the right time, and listens effectively</em></p><p>Great communication is central to everything we do at Medium, and without it, most non-trivial efforts would fail. Whether discussing approaches, giving presentations, listening attentively, or managing stakeholders, excellent communication is a key skill. The ability to communicate an idea, and to understand communicated ideas is of critical importance to ensure a well-aligned, agile team.</p><h4>Craft</h4><p><em>Embodies and promotes practices to ensure excellent quality products and services</em></p><p>We want quality to be at the center of everything we do, and strive to create well-built products that provide a polished and intuitive user experience. We want engineers to take pride in their work and sweat the details. We need them to produce well-written, well-tested code that is easy to maintain, and easy to remove when no longer needed.</p><h4>Initiative</h4><p><em>Challenges the status quo and effects positive organisational change outside of mandated work</em></p><p>We want engineers to take ownership of the product, focus on fixing issues when they see them, get the details right, and improve things as they go. We need people that effect change, champion new ideas, and work hard to move the company forward, even when there is organisational resistance.</p><h3>Supporting</h3><p>We believe in a model of <a href="https://en.wikipedia.org/wiki/Servant_leadership">servant leadership</a> that exists to develop team members, advocate for them, support their well being, and ensure an environment conducive to enabling effective work. Effective, formal people management is crucial to getting the most out of our team, building for the future, and providing stability during organisational change.</p><h4>Career Development</h4><p><em>Provides strategic support to engineers to help them build the career they want</em></p><p>Personal and professional growth are very important to us, and to support this, we need our group leads to be aligned with group members on the importance of career development. We want our group leads to be intentionally working to support an engineer’s growth, whether by putting together career plans, finding new opportunities for them, or providing formal training.</p><h4>Org Design</h4><p><em>Defines processes and structures that enables the strong growth and execution of a diverse eng organization</em></p><p>Too much structure and process can slow a team down, but too little can also be debilitating. As an organisation, we need to be continually focusing on how the team is executing, finding ways to do things faster and better, and ensuring that the appropriate systems are in place to foster a diverse and inclusive team.</p><h4>Wellbeing</h4><p><em>Supports the emotional well-being of group members in difficult times, and celebrates their successes</em></p><p>The psychological safety of our team is of paramount importance. Individuals cannot take risks if they are afraid of the consequences of failure, and the ability to take risks is a significant part of innovation. We need our group leads to support the health and wellbeing of our people, ensure that they feel safe, help them work through interpersonal difficulties calmly, and promote a culture of empathy and self-awareness on the team.</p><h4>Accomplishment</h4><p><em>Inspires day to day excellence, maximises potential and effectively resolves performance issues with compassion</em></p><p>We need leaders who can tactically unblock engineers who are struggling, and can work with them to understand, contextualise, and resolve root causes. We also need people who can resolve higher level organisational dysfunction when it occurs and get teams back on track.</p><h3>Strengthening</h3><p>Many engineers do other work outside their primary responsibilities which strengthen the team, but are often undervalued. We explicitly recognise the importance of these contributions, each of which are important to building the kind of team we want, even though they may not be celebrated as widely or as often as product releases.</p><h4>Mentorship</h4><p><em>Provides support to colleagues, spreads knowledge, and develops the team outside formal reporting structures</em></p><p>While <em>Career Development</em> is about formal planning, mentorship is equally important. We want to continue our culture of learning and teaching, and incentivise engineers to help develop each other, whether through internal posts, support groups, team presentations, programming curricula, or some other medium.</p><h4>Evangelism</h4><p><em>Promotes Medium to the outside world and establishes it as an attractive and thoughtful place to work</em></p><p>Medium devotes a lot of intentional thought to all its endeavours, whether our technical innovations, the cultural impact of our choices, or how we design our organisation. We strive to create a healthy, balanced, and mindful workplace, build exceptional products, and engage with the outside world in a responsible, inclusive way. We want our people to be communicating these efforts externally, representing Medium well, building partnerships with other organisations, and encouraging people to get to know us more.</p><h4>Recruiting</h4><p><em>Strengthens Medium’s team by bringing in excellent staff members</em></p><p>Recruiting is one of the most important things that we do as an organisation. We need engineers to bring candidates into the pipeline, think about how we build a diverse team that covers our blindspots, evaluate candidates purely on <a href="http://medium.engineering/engineering-interviews-what-we-screen-for-af2d84122417">the criteria that we deem important</a>, and ensure that we only bring in new people that believe in our company values.</p><h4>Community</h4><p><em>Builds community internally, gives of themself to the team, and champions and extols company values</em></p><p>We are not trying to build a family, but we are trying to build a team where people trust and support each other, and work hard to build something together. We highly value those people who always pitch in to help, who do tedious refactoring for the good of the team, or who work to build a culture of collaboration, community, and togetherness.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b1fad620787e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Engineering growth: framework overview]]></title>
            <link>https://medium.com/@MediumEng/engineering-growth-framework-overview-4e02ab330524?source=rss-d0bbc53072f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e02ab330524</guid>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[medium]]></category>
            <category><![CDATA[values]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Medium Engineering]]></dc:creator>
            <pubDate>Tue, 17 Oct 2017 18:04:23 GMT</pubDate>
            <atom:updated>2019-07-01T13:41:43.245Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>As we continue to learn, we are now on our third iteration of this process. Please see </em><a href="https://medium.engineering/engineering-growth-at-medium-4935b3234d25?source=post_elevate_sequence_page---------------------------"><em>here</em></a><em> for the latest update.</em></p><p><em>We recently undertook a project to define professional development for members of Medium’s engineering team. As part of that, I wrote this document to describe the main features of our Growth Framework. It was originally published to Hatch, our internal version of Medium, on August 25, 2017. For more information about Medium’s practice of making internal documents public, see </em><a href="https://medium.com/inside/hatching-inside-medium-5ae60292d655"><em>Hatching Inside Medium</em></a><em>.</em></p><p><em>This is the actual document used by Medium to explain how we think about recognising growth, and has replaced the version on Hatch as the source of truth. If you </em><a href="https://medium.engineering/engineering-f7e2dee906be"><em>take a job at Medium</em></a><em>, this is the framework within which your career development will be assessed.</em></p><p>Preface: <a href="https://medium.com/p/8ba7b78c8d6c">Introduction</a><br>Part 1: Framework overview<br>Part 2: <a href="https://medium.com/p/b1fad620787e">Tracks</a><br>Part 3: <a href="https://medium.com/p/743620e70763">Assessing progress</a><br>Part 4: <a href="https://medium.com/p/25a2161ed582">Appeals process</a><br>Part 5: <a href="https://medium.com/p/e860b07ca4ab">Frequently asked questions</a></p><p>You can also <a href="https://docs.google.com/spreadsheets/d/1EO-Dbsayn8Nz9Ii3MKcwRbt-EIJ2MjQdpoyhh0tBdZk">read the rubric in full</a>, and <a href="https://snowflake.medium.com">use the interactive tool</a>.</p><p>By <a href="https://medium.com/u/4533cec1ea76">Jamie Talbot</a> and <a href="https://medium.com/u/8e995a263311">Madeline Bermes</a>.</p><p>Medium’s Growth Framework is a little different from how many companies approach development, recognition and leveling. This document describes its structure and some of the reasoning behind it.</p><h3>Goals</h3><p>We are attempting to solve a number of problems with this framework, and avoid others that we recognised in other systems. At a high level, we are trying to achieve multiple goals:</p><ul><li>Allowing engineers to develop in multiple ways, rather than artificially reducing them to “engineer” or “manager”.</li><li>Recognising that roles are not static, and that people will evolve over time.</li><li>Codifying what is expected of engineers.</li><li>Recognising contributions that are typically undervalued or ignored in traditional engineering ladders.</li><li>Providing multiple ways for people to be recognised for leading within the organisation.</li><li>Giving recognition and rewarding professional development.</li><li>Ensuring fair and equitable compensation.</li><li>Avoiding the development of a homogenous team, where everyone does the same kind of work.</li><li>Connecting hiring and progression to our company values, so we hire, incentivise, and reward what we value.</li></ul><p>Overall, the main goal we are trying to achieve is helping engineers answer the question “How do I progress?”</p><h3>Overview</h3><p>We recognise that all engineers are different and that each applies a unique combination of skills in their work. We understand that there are many paths to a successful career, and support and encourage the growth of different shapes of engineers that together create a robust and flexible team. We know that there are particular kinds of work that is often overlooked, which is nevertheless very important.</p><h4>Tracks</h4><p>To recognise these contributions, we define 16 tracks along which engineers are incentivised to develop and progress. Each of these tracks represents a discipline that adds value to the organization and helps Medium achieve its goals. These tracks are grouped into 4 categories:</p><p><strong>Building<br></strong>Mobile, Web Client, Foundations, and Servers</p><p><strong>Executing<br></strong>Project Management, Communication, Craft, and Initiative</p><p><strong>Supporting<br></strong>Career Development, Org Design, Wellbeing, Accomplishment</p><p><strong>Strengthening<br></strong>Mentorship, Evangelism, Recruiting, Community</p><p>Each category has a list of hiring indicators from <a href="https://medium.engineering/engineering-interviews-what-we-screen-for-af2d84122417">the hiring rubric</a>, which hint at the kind of qualities useful for progress along these tracks, but they are intended to be more informational than prescriptive.</p><p>Each track is weighted equally. We have deliberately tried to define tracks that add concrete value to the organisation, and hold appeal to all kinds of engineering personalities.</p><p>Engineers may attempt to progress down any combination of tracks, though realistically, they will only be able to focus on a few at a time, and organisational needs may mean that they are strongly encouraged to focus on certain areas.</p><h4>Milestones</h4><p>Each track has 5 milestones, which get progressively harder to achieve. It is much harder, for example, to move from milestone 4 to milestone 5 than from milestone 1 to milestone 2. Track milestones typically range from simple individual contribution to major organisational impact. Each milestone is intended to be approximately as difficult to achieve as the same milestone in every other track for a motivated individual, assuming a start from scratch. Given the wide range of tracks, and people’s experience or natural capabilities, every engineer will find some tracks easier or harder than others.</p><p>Each milestone has a description, which provides a high-level overview of the milestone, and 6 example behaviours and tasks. These examples are descriptive, not prescriptive. They are designed to be read together with the milestone description to paint a picture of the kind of person we would expect to see at that milestone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QkmhR7HhRZY1MkG9j77N1Q.png" /><figcaption>Milestones 1 and 2 of the Craft Track</figcaption></figure><h4>Points</h4><p>Each milestone achieved earns points. Because successive milestones are harder to achieve, they are worth more points. The chosen point progression slightly favours specialisation over generalisation. Organisationally, it is important that people develop and are rewarded for mastery of certain skills so we have the ability to innovate at the leading edge. However, we recognise that strong generalists provide great flexibility and are foundational to a robust and antifragile team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NMBRbXqV1M5xThouoBQqnQ.png" /><figcaption>Milestone points progression</figcaption></figure><p>Points at a given milestone replace points earned at an earlier milestone. For example, moving from milestone 3 to milestone 4 earns an additional 6 points, not an additional 12 points.</p><p>With 16 tracks, each having 5 milestones, there are a total of 320 points available. We do not expect anyone to come close to achieving that number.</p><h4>Levels</h4><p>Every point earned contributes to an engineer’s overall level. There are 5 overall levels, each divided into 3 sub levels. Successive levels require more points and are harder to achieve.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*F6G9xRiurHzXBJSQBfUASw.png" /><figcaption>Level progression</figcaption></figure><p>The entire point progression is defined in <a href="https://docs.google.com/spreadsheets/d/1EO-Dbsayn8Nz9Ii3MKcwRbt-EIJ2MjQdpoyhh0tBdZk">the rubric</a> and in <a href="https://snowflake.medium.com">the interactive tool</a>.</p><p>We may add more levels over time as we grow as an organisation. The highest level is currently defined at 135 points out of a possible 320, which gives us plenty of room to grow should it be necessary.</p><h4>Salary</h4><p>We care very much about fairness and recognising equal contribution with equal compensation.</p><p>Level-based salary and equity is the same for all engineers at the same overall level. There may be rare occasions where this is not the case due to external factors or exceptional extenuating circumstances, such as acquisitions.</p><p>Medium offers equity refreshes based on tenure, so it is not necessarily the case that everyone at the same overall level will have the same equity.</p><p>Medium may also offer one-time signing bonuses where there is a compelling business need, such as a role that is particularly hard to hire for, or where we need to incentivise someone to move their home. Taking this into account, annualised compensation may differ between people at the same level.</p><p>Although we reserve the right to retain this flexibility, we work very hard to ensure that people performing at the same level are compensated equally, regardless of gender, race, or any other unimportant factor.</p><h4>Titles</h4><p>Titles typically serve three purposes — helping people understand that they are progressing, vesting authority in those people who might not automatically receive it, and communicating an expected competency level to the outside world.</p><p>The first two needs are met by the level number itself, and so internally, to the extent that we refer to them at all, we will use the level numbers to communicate seniority and capability.</p><p>In standard industry parlance the 5 major levels are broadly comparable to <em>Engineer I, Engineer II, Senior Engineer, Staff Engineer, </em>and<em> Principal Engineer</em>, but externally the levels don’t mean much without context. Therefore, we allow people to choose a title from a restricted set at each overall level, for external use on their resume, bio, or LinkedIn profile. For example, an engineer focusing primarily on <em>Supporting</em> tracks at Level 3.3 might choose <em>Engineering Manager</em>, while an engineer focusing on <em>Building</em> tracks at the same overall level might choose <em>Senior Engineer</em>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e02ab330524" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Engineering growth: introduction]]></title>
            <link>https://medium.com/@MediumEng/engineering-growth-introduction-8ba7b78c8d6c?source=rss-d0bbc53072f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ba7b78c8d6c</guid>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[values]]></category>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[medium]]></category>
            <dc:creator><![CDATA[Medium Engineering]]></dc:creator>
            <pubDate>Tue, 17 Oct 2017 18:04:06 GMT</pubDate>
            <atom:updated>2019-07-01T13:42:19.624Z</atom:updated>
            <cc:license>https://creativecommons.org/licenses/by-sa/4.0/</cc:license>
            <content:encoded><![CDATA[<p><em>As we continue to learn, we are now on our third iteration of this process. Please see </em><a href="https://medium.engineering/engineering-growth-at-medium-4935b3234d25?source=post_elevate_sequence_page---------------------------"><em>here</em></a><em> for the latest update.</em></p><p>Until recently, the process around progression and promotion as a Medium engineer was relatively opaque. We did have the concept of levels, and senior leadership were reasonably well calibrated on what being at a certain level entailed. However, engineers did not know what their level was, or the kinds of work they specifically needed to do to progress in their career. Instead, we relied upon the trust relationship between an engineer and their <a href="https://medium.com/p/dd1092f4e9f3#d16b">group lead</a>, and in senior engineering leadership to do “the right thing”.</p><p>Although we in the leadership team were thoughtful about these areas, and did our best to be fair, the lack of transparency was frustrating for some, and led others to express reasonable doubts about the process. This was at odds with one of our company values, <em>Build Trust</em>. To remedy this, in late August we rolled out our Growth Framework, a set of documents and tools that described what we value at Medium, how to progress, and how we measure and reward that progress.</p><p>In doing so, we attempted to build a thoughtful process that was equitable, incentivised the right kind of work, and which encouraged the growth of a robust, flexible, and inclusive team. Although development and delivery of the framework was led by <a href="https://medium.com/u/4533cec1ea76">Jamie Talbot</a> and <a href="https://medium.com/u/8e995a263311">Madeline Bermes</a>, it is the result of input and collaboration from the whole engineering team at Medium over many months.</p><blockquote>Today, we are excited to make our Growth Framework public for everyone to see.</blockquote><p>We’re releasing all this material under a <a href="https://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution-ShareAlike</a> license. You are welcome to take this work, build on it, and make suggestions for improvements. Medium strongly believes that our industry would benefit greatly if we shared and built upon each other’s organisational processes the same way we share and build upon each other’s open source code.</p><p>In addition to this introductory piece, there are five living documents which describe the specifics of the framework, and three tools that we use to plan, assess, and memorialise growth. (Thanks to <a href="https://medium.com/u/59a2a7ebcaac">Alex Wolfe</a> for art direction of the written documentation!) We will modify and improve all of these over time. As with <a href="https://medium.engineering/engineering-interviews-what-we-screen-for-af2d84122417">our hiring documentation</a>, these public documents and tools are the actual ones that we use at Medium. There are no separate internal versions of these guides.</p><h4>Part 1: <a href="https://medium.com/p/4e02ab330524">Framework overview</a></h4><p>The <em>framework overview</em> describes the major characteristics of the framework, the problems we are trying to solve, and related areas like salary and titles.</p><h4>Part 2: <a href="https://medium.com/p/b1fad620787e">Tracks</a></h4><p>Medium engineers add value to the engineering organisation in many ways, and we attempt to capture this by recognising progress in 16 areas. The <em>tracks</em> document explains the rationale for each track.</p><h4>Part 3: <a href="https://medium.com/p/743620e70763">Assessing progress</a></h4><p><em>Assessing progress</em> explains how we determine whether an engineer has reached a given milestone in a track, as well as the cadence at which we check in on progress and make formal assessments. It also discusses the tension between subjectivity, objectivity, and bias, and acknowledges the role that opportunity plays in advancement.</p><h4>Part 4: <a href="https://medium.com/p/25a2161ed582">Appeals process</a></h4><p>Given that the framework is somewhat subjective, we accept that even reasonable people acting in good faith can make mistakes or fail to appropriately value work. The <em>appeals process</em> outlines the way in which engineers can challenge a decision they consider to be inaccurate.</p><h4>Part 5: <a href="https://medium.com/p/e860b07ca4ab">Frequently asked questions</a></h4><p>Even with exhaustive documentation, people still have questions. <em>Frequently asked questions</em> attempts to answer them.</p><h4>Tool: <a href="https://docs.google.com/spreadsheets/d/1EO-Dbsayn8Nz9Ii3MKcwRbt-EIJ2MjQdpoyhh0tBdZk">Rubric</a></h4><p>The<em> rubric</em> is the source of truth that defines the progression of engineers at Medium. It provides descriptions for each milestone along with example tasks and behaviours that, taken together, illustrate our expectations of engineers as they advance in their careers, without being overly prescriptive.</p><h4>Tool: <a href="https://snowflake.medium.com">Snowflake</a></h4><p><em>Snowflake</em> is a simple web tool that we use to have growth conversations with engineers. It lets us show them how progress along certain tracks will affect their overall level, and helps them make decisions about how they want to grow. You can find and fork <a href="https://github.com/Medium/snowflake">the code</a> on GitHub. Props to <a href="https://medium.com/u/d2e2f44df9bf">Emma Zhou</a> for building this in her spare time, while simultaneously delivering <a href="https://blog.medium.com/show-authors-more-️-with-s-c1652279ba01">Claps</a>, and <a href="https://medium.com/u/1d33bf437270">Jonathan Fuchs</a> for later iterations!</p><h4>Tool: <a href="https://docs.google.com/document/d/1-elpy-O0LykgMu11PPDJbgZ03MaJBsdkWiiXZuueMA8">Medium Story template</a></h4><p>We like telling stories at Medium, and we like to think of our engineers’ progress at Medium as a continuously unfolding story, which includes things like formal reviews and <a href="https://medium.com/@gabekleinman/madlib-tm-feedback-e0fcd1b56921">peer feedback</a>. The <em>Medium Story template</em> is a Google Doc template that lets us celebrate and memorialise an engineer’s growth over time, and provides a historical record that we can use to frame growth conversations.</p><p>We spent a lot of time thinking through this process and plan to publish more about the high level philosophy, the challenges we faced, the process we used to arrive at this framework, and some of the things we learned along the way.</p><p>However, there are three elements that are worth noting in more detail here.</p><h4>Growth</h4><p>We really struggled to make much headway on the system, until <a href="https://medium.com/u/8e995a263311">Madeline Bermes</a> made the insightful comment that this framework should be about growth, not leveling. Traditional methods of assessing people, and even the language that is used to describe them — ladders, slots, boxes, etc. — are primarily concerned with giving someone a level or categorising them in some way. We think this is artificially constraining, and frames professional development as a competition rather than a personal journey.</p><p>Rather than follow this model, we instead tried to craft a framework that centers around the growth of an individual, and supports them in the kind of career that they want to have. While we do have overall levels — which is important for ensuring fairness in compensation — they are explicitly a by-product of an engineer’s growth. <a href="https://www.upi.com/Science_News/2016/03/10/For-most-a-pay-raise-has-no-effect-on-happiness/6791457646362/">Studies</a> <a href="https://www.glassdoor.com/research/does-money-buy-happiness-the-link-between-salary-and-employee-satisfaction/">have</a> <a href="http://www.pnas.org/content/107/38/16489.abstract">shown</a> that the positive feelings associated with getting a raise are only temporary, and that long term satisfaction is much more closely tied to personal development. The kinds of people we like to hire are collaborative, curious, and have a <a href="https://www.mindsetworks.com/science/">growth mindset</a>. It is important that our framework supports and encourages that.</p><p>As a result, you will notice that we consistently refer to the framework as a Growth Framework, and that we only discuss overall levels as the result of that growth. The terms we use to describe the system help communicate that the primary intent is to support personal improvement.</p><h4>Conversation</h4><p>Typical professional development frameworks assess people at fixed intervals once, or maybe twice a year. This creates a low number of high stakes moments, which induce stress and frustration as people try to prove their worth in order to gain a promotion.</p><p>Although formal assessments at Medium are made every 6 months, we aim to turn professional development into an ongoing conversation that helps increase accountability on both sides. This begins with a personalised growth plan for every engineer, in the form of OKRs and milestone goals for the next 6 months. An engineer and their group lead review these in mandated sessions every 6 weeks, which creates space for an honest conversation about progress, and any challenges or blockers. The regular check-ins are designed to ensure that no-one is surprised with the outcome of the formal assessment at the end of the cycle. We also encourage engineers to record evidence of their achievements over time to combat recency bias.</p><h4>Equity</h4><p>A key measure of success for this system was whether it treated engineers equitably, and rewarded their work appropriately, regardless of race, gender, age, or any other unimportant factor. With rare exception (typically due to external factors), everyone at the same overall level receives the same level-based compensation.</p><p>Looking at the distribution of level changes after our first assessment, we believe the new rubric helps us better acknowledge valuable contributions that were not previously recognised.</p><p>We plan to publish more comprehensive statistics in the future.</p><p>Having a formal system means we can better support the growth of our engineers. We’re able to have more honest, open conversations about progress, promotions, and opportunity. While the framework is still relatively new, it is showing early promise at incentivising the kinds of behaviours we want to see in the team, and recognising the different kinds of value that people add.</p><p>We already have ideas on how to improve the framework further, and plan to continue iterating on it over time. We are releasing it publicly now, in the hope that it can help other companies that are thinking about how to grow and support their employees.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ba7b78c8d6c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tuesday 19 September 2017]]></title>
            <link>https://medium.com/postmortems/tuesday-19-september-2017-825c0849f275?source=rss-d0bbc53072f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/825c0849f275</guid>
            <category><![CDATA[postmortem]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[medium-engineering]]></category>
            <dc:creator><![CDATA[Medium Engineering]]></dc:creator>
            <pubDate>Fri, 06 Oct 2017 01:30:59 GMT</pubDate>
            <atom:updated>2017-10-06T01:30:59.869Z</atom:updated>
            <content:encoded><![CDATA[<h4>Crash on app launch for users running iOS 11</h4><p>On September 19, 2017, version 3.3 of the Medium iOS app was released to the App Store. Apple released the official version of iOS 11 earlier that same day. Through a combination of factors, the app started crashing on launch for users running iOS 11.</p><h4>Timeline</h4><ul><li><strong>September 19, 3:22pm: </strong>Version 3.3 was released to the App Store.</li><li><strong>4:16pm:</strong> iOS engineers received an alert from Crashlytics about a crash affecting a large percentage of users on iOS 11 only.</li><li><strong>6:03pm:</strong> A fix for the crash was submitted in version 3.4 of the app with an expedited review request.</li><li><strong>September 20, 11:00pm:</strong> Version 3.4 of the app was approved and released.</li></ul><h4>Root cause</h4><p><a href="https://medium.com/p/2bfaaea75bfe">The crash was caused by a runtime type mismatch</a> between what type an object was declared to be and what type it was at runtime. This type mismatch was introduced a while ago, but didn’t start causing crashes until iOS 11.</p><p><em>The Medium Engineering team have committed to publishing a technical postmortem for serious outages to Medium core services, in order to build trust and hold us accountable to our users. </em><a href="https://medium.com/postmortems/public-accountability-5935ed4d5e5a"><em>More background on this program</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=825c0849f275" width="1" height="1" alt=""><hr><p><a href="https://medium.com/postmortems/tuesday-19-september-2017-825c0849f275">Tuesday 19 September 2017</a> was originally published in <a href="https://medium.com/postmortems">Postmortems</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tuesday July 11th, 2017]]></title>
            <link>https://medium.com/postmortems/draft-for-the-public-post-mortem-for-outage-of-july-11th-2017-8190e503df7d?source=rss-d0bbc53072f4------2</link>
            <guid isPermaLink="false">https://medium.com/p/8190e503df7d</guid>
            <dc:creator><![CDATA[Medium Engineering]]></dc:creator>
            <pubDate>Wed, 26 Jul 2017 20:08:34 GMT</pubDate>
            <atom:updated>2017-07-26T20:30:43.255Z</atom:updated>
            <content:encoded><![CDATA[<h3>Summary</h3><p>On July 11th, 2017, Medium.com was not serving requests from 4:10 pm to 4:14 pm due to a deployment issue caused by a miscommunication.</p><h3>Impact</h3><p>No one could access <a href="https://medium.com/">https://medium.com</a> for 4mn.</p><h3>Root cause</h3><p>At Medium, all services are deployed following a <a href="https://en.wikipedia.org/wiki/Continuous_delivery">continuous integration and continuous deployment</a> model. What this means is that deployments of our services happen automatically at a high frequency (this service, in particular, gets deployed dozens of times a day). To make this process safe, our deployment pipeline runs a health check on a <a href="https://martinfowler.com/bliki/CanaryRelease.html">canary</a> to make sure that there is no obvious regression.</p><p>If the health check step passes, all production traffic is redirected to a fleet of servers running the new build.</p><p>If anything bad is discovered, the deployment pipeline stops and notifies the on-call team. The team then investigates the possible regression and decides between retrying the health check step or abandoning a build.</p><p>In this case, the health check step did not pass, and two different protocols were implemented simultaneously, causing an outage.</p><h3>Action Taken</h3><p>We took the necessary actions to prevent such issues from happening again by adding a lock to prevent an abandoned build from being retested and adding extra steps prior to the promotion of a build to make sure enough hosts are running the service before switching traffic to the new fleet.</p><h3>Timeline</h3><ul><li><strong>4:10 pm PDT</strong><br>Health check of our deployment pipeline mistakenly allows a terminated build to be promoted taking down <a href="https://medium.com">https://medium.com</a></li><li><strong>4:14 pm PDT</strong><br>Oncall engineer rolls back the bad fleet and returns Medium to service</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8190e503df7d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/postmortems/draft-for-the-public-post-mortem-for-outage-of-july-11th-2017-8190e503df7d">Tuesday July 11th, 2017</a> was originally published in <a href="https://medium.com/postmortems">Postmortems</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>