This repository has been archived by the owner on Jul 2, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 113
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
5e8b528
commit e5796f4
Showing
1 changed file
with
137 additions
and
194 deletions.
There are no files selected for viewing
331 changes: 137 additions & 194 deletions
331
content/departments/product/career-development/framework.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,196 +1,139 @@ | ||
| # Sourcegraph product career development framework | ||
|
|
||
| ## Levels | ||
|
|
||
| <style> | ||
| .container { | ||
| --width: var(--container-width); | ||
| } | ||
| </style> | ||
|
|
||
| <table class="levels-table"> | ||
|
|
||
| <thead> | ||
| <tr> | ||
| <th scope="col">Level</th> | ||
| <th scope="col" class="category-title">Business/GTM Strategy</th> | ||
| <th scope="col" class="category-title">Industry/Market Knowledge</th> | ||
| <th scope="col" class="category-title">Product Strategy</th> | ||
| <th scope="col" class="category-title">Developer/Technical Intuition</th> | ||
| <th scope="col" class="category-title">Maximizing Impact</th> | ||
| <th scope="col" class="category-title">Data-Driven</th> | ||
| <th scope="col" class="category-title">Collaboration</th> | ||
| <th scope="col" class="category-title">Mentorship and Coaching</th> | ||
| </tr> | ||
| </thead> | ||
|
|
||
| <tbody> | ||
| <!-- IC1 --> | ||
| <tr> | ||
| <th id="ic1" scope="row" rowspan="3" class="level"><a class="anchor" href="#ic1"></a><abbr title="Individual Contributor">IC</abbr>1</th> | ||
| </tr> | ||
| <tr> | ||
| <td class="level-summary" colspan="8"> | ||
| An entry level PM who can execute on a highly scoped problem with strong support from engineering counterparts; an Associate PM. | ||
| </td> | ||
| </tr> | ||
| <tr class="behaviors-row"> | ||
| <td class="behaviors"> | ||
| Understands how Sourcegraph makes money and how our business KPIs measure the long-term success of the business. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Understands how the company's GTM strategy impacts the product experience. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Understands the role their product plays in the platform's vision and strategy. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Understands the technical constraints related to their product and uses that knowledge to correctly plan and scope their roadmap. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Defines goals, leads their team in prioritizing our work, and works with their team to execute tactically. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Understands the problem we are trying to solve based on existing research and can articulate this to others. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Conducts team meetings in a way that fosters effective team collaboration. | ||
| </td> | ||
| <td class="behaviors"></td> | ||
| </tr> | ||
| <!-- IC2 --> | ||
| <tr> | ||
| <th id="ic2" scope="row" rowspan="3" class="level"><a class="anchor" href="#ic2"></a><abbr title="Individual Contributor">IC</abbr>2</th> | ||
| </tr> | ||
| <tr> | ||
| <td class="level-summary" colspan="8"> | ||
| A junior PM capable of owning a small piece of a highly ambiguous project that impacts a specific feature within Sourcegraph. | ||
| </td> | ||
| </tr> | ||
| <tr class="behaviors-row"> | ||
| <td class="behaviors"></td> | ||
| <td class="behaviors"> | ||
| Understands the category our product operates in and our key direct competitors. Understands the high-level problems our customers have and how Sourcegraph solves them. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Can derive their product's strategy based on the overall strategy and communicate in the open why we will or won't deliver on certain items. | ||
| </td> | ||
| <td class="behaviors"></td> | ||
| <td class="behaviors"> | ||
| Incorporates user research, market/industry knowledge, and business goals in their prioritization of discovery and delivery efforts. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Understands the problem we are trying to solve and what information we'd need to validate it. Knows how to measure the success of an initiative. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Frequently shares work-in-progress and present updates on their product to everyone in the company. | ||
| </td> | ||
| <td class="behaviors"></td> | ||
| </tr> | ||
| <!-- IC3 --> | ||
| <tr> | ||
| <th id="ic3" scope="row" rowspan="3" class="level"><a class="anchor" href="#ic3"></a><abbr title="Individual Contributor">IC</abbr>3</th> | ||
| </tr> | ||
| <tr> | ||
| <td class="level-summary" colspan="8"> | ||
| A mid-career PM who is confident driving an established feature or product from beginning to end. | ||
| </td> | ||
| </tr> | ||
| <tr class="behaviors-row"> | ||
| <td class="behaviors"> | ||
| Understands how the company's GTM strategy impacts the product experience. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Understands the direct key competitors in our category and how we compare against them. Understands specific challenges our customers face and how our product(s) address these. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Drives the creation of their product's strategy based on the early and continuous feedback of and collaboration with stakeholders. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Considers how influential devs and dev communities will perceive their product and take that into account when planning their roadmap. Understands the technical aspects of their product and uses that knowledge to create a better product. | ||
| </td> | ||
| <td class="behaviors"> | ||
| With a scoped problem, is able to drive the creation and launch of an experience by working cross-team (i.e. product marketing) to create shared outcomes. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Understands the pros/cons of different research techniques and knows what to use to solve a particular question. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Is familiar with other teams' work and how it relates to their team's work. Works collaboratively with other teams when responsibilities overlap. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Recognizes their skill/knowledge gaps and seeks out mentors who can help them grow. | ||
| </td> | ||
| </tr> | ||
| <!-- IC4 --> | ||
| <tr> | ||
| <th id="ic4" scope="row" rowspan="3" class="level"><a class="anchor" href="#ic4"></a><abbr title="Individual Contributor">IC</abbr>4</th> | ||
| </tr> | ||
| <tr> | ||
| <td class="level-summary" colspan="8"> | ||
| A PM capable of executing an ambiguous, cross-functional project to completion that shapes the future of Sourcegraph’s business; a Senior PM. | ||
| </td> | ||
| </tr> | ||
| <tr class="behaviors-row"> | ||
| <td class="behaviors"> | ||
| Partners with the GTM team to support GTM growth within existing features. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Understands direct and indirect competitors in our category, how we can compare and where we could invest to win. Has built relationships with key customers, understands their specific needs and works collaboratively with them to build solutions. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Drives the long term vision of their product(s) and influence the overarching product vision. Creates a strategy that identifies the key challenges we may face and how we overcome them to maximise the impact we have. Continues to iterate and adapt the strategy based on new input and communicates this transparently. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Understands how influential devs and dev communities will perceive their product, and effectively communicates with them directly in a way that gains us new knowledge and/or respect. Deeply understands the technical aspects of their product and uses that knowledge to create a better product that meets particularly complex technical requirements. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Given a rough direction based on critical business needs, can create the right outcome, based on an understanding of the market and customer. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Is able to clearly define research questions and leverage multiple research methods to gather sufficient data to answer their question. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Leads cross-functional collaboration to deliver outcomes that improve user experience. Teams recognize how they create and communicate their strategy and apply it with their teams. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Actively serves as a mentor to a team member working on a project related to their own. | ||
| </td> | ||
| </tr> | ||
| <!-- IC5 --> | ||
| <tr> | ||
| <th id="ic5" scope="row" rowspan="3" class="level"><a class="anchor" href="#ic5"></a><abbr title="Individual Contributor">IC</abbr>5</th> | ||
| </tr> | ||
| <tr> | ||
| <td class="level-summary" colspan="8"> | ||
| A very experienced PM, capable of efficiently driving multiple cross-functional projects in a highly autonomous way while understanding the impact of their work to Sourcegraph and the broad market as a whole; a Staff PM. | ||
| </td> | ||
| </tr> | ||
| <tr class="behaviors-row"> | ||
| <td class="behaviors"> | ||
| Leverages new product opportunities to expand Sourcegraph into new GTM channels/markets and kickstart new levers of growth. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Understands and identifies where there are opportunities in adjacent product categories, or creates new product categories that would benefit our business. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Efficiently seeks net-new product opportunities that expand Sourcegraph into new markets by exploring strategic opportunities to buy or partner with external companies. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Is known and respected by influential devs and dev communities in their product area, and us that to increase the odds of success for their product. Uses their technical intuition to create a better product in ways that rely on brand new approaches and/or their nuanced understanding of the evolving technical landscape of product area. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Is able to efficiently execute cross-Sourcegraph efforts in highly ambiguous and often risky projects for Sourcegraph. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Is able to clearly define research questions, leverage multiple research methods and define net-new methods when required. | ||
| </td> | ||
| <td class="behaviors"> | ||
| The business depends on them to successfully manage cross-functional initiatives. | ||
| </td> | ||
| <td class="behaviors"> | ||
| Actively serves as mentors to junior team members and other less experienced PMs. | ||
| </td> | ||
| </tr> | ||
| </tbody> | ||
| </table> | ||
| Our career development framework is here to help you understand the expectations of your role, and to provide a common language for you and your manager to discuss and plan your career growth. It is also an important part of our larger goal of ensuring everyone is equitably recognized for the impact they have at work, and to reduce bias in promotions and hiring. | ||
|
|
||
| ## What are the expectations of my role? | ||
|
|
||
| We have shared expectations for all product managers, regardless of level or role. On top of that we have additional levels showing how a teammate’s impact, scope, execution, and teamwork varies by level. | ||
|
|
||
| - Impact: The tangible and positive difference made through one's contributions to the company’s mission. | ||
| - Scope: The breadth and depth of one’s technical and non-technical expertise, including how one maps business goals to technical solutions. | ||
| - Execution: The ability to consistently and efficiently translate plans into outcomes. | ||
| - Teamwork: The art of collaborating effectively with others, both within and outside the organization. | ||
|
|
||
| Expectations for a level add to the expectations of earlier levels. In addition, we expect product managers at all levels to exhibit our values. | ||
|
|
||
| ## All Levels | ||
|
|
||
| - Impact | ||
|
|
||
| - Directly contributes to achieving the company’s strategic goals and long term success. | ||
|
|
||
| - Scope | ||
|
|
||
| - Has high productivity and output, with frequent and meaningful impact on the direction of our products based on a keen understanding of our customer’s needs. | ||
| - Works with engineering to release regularly and with marketing to launch regularly. | ||
| - Provides clarity by writing strategy and roadmap docs, PRDs and related docs as appropriate to the level and that align with the style and best practices of the organization and that are well-socialized and ratified by the EPD team and appropriate stakeholders. | ||
|
|
||
| - Execution | ||
| -Seeks clear ownership of areas of responsibility as appropriate for the level. | ||
|
|
||
| - Prioritizes high impact work. Identifies engineering, design, marketing and business problems and collaborates on solutions. | ||
| - Gathers customer data from a variety of sources to make product decisions, e.g. DevRel, UXR, metrics and, of course, directly from customers. | ||
| - Demonstrates technical knowledge, both for having productive conversations with engineering and to empathize with our target customers. | ||
| - Has a firm technical opinion that helps shape the direction of our technical products. | ||
| - Balance customer needs with business priorities, even in the face of ambiguity. | ||
| - Can work remotely & asynchronously. Knows how to manage time, work, and communication. | ||
|
|
||
| - Teamwork | ||
| - Escalates early and efficiently when blocked, stuck, overloaded, or sees a better way to achieve our goals. | ||
| - Works with the EPD team to ensure successful releases, launches and landings while also keeping an eye on the future in their areas of responsibility. | ||
| - Works to accelerate and unblocks colleagues as needs arise. | ||
| - Communicates thoughtfully and proactively to keep stakeholders informed and identify risks. | ||
| - Helps build team cohesion by advocating for design and engineering needs. | ||
| - Helps others understand the company direction, detects misalignments, and provides missing context. | ||
|
|
||
| ## IC2 | ||
|
|
||
| - Impact: | ||
|
|
||
| - Clarifies project scope and delivers projects of medium to large size, e.g. groups of related features in existing products. | ||
|
|
||
| - Scope: | ||
|
|
||
| - Primarily focuses on their team’s features/product. | ||
| - Pulls on broader knowledge of Sourcegraph. | ||
| - Strong generalist skill set; starting to develop some areas of expertise. | ||
|
|
||
| - Execution: | ||
|
|
||
| - Identifies non-obvious gaps in the product. | ||
| - Representing the product to peers directly in small groups. | ||
|
|
||
| - Teamwork: | ||
| - Actively contributes to a collaborative and respectful team culture. | ||
| - Collaborates across teams, focused on their direct areas of work. | ||
|
|
||
| ## IC3 | ||
|
|
||
| - Impact: | ||
|
|
||
| - Drives clarity on highly technical, open-ended, potentially ambiguously-defined projects. | ||
| - Drives clarity for one large or several small-medium projects. | ||
|
|
||
| - Scope: | ||
|
|
||
| - Often collaborates with teammates on projects outside their immediate domain. | ||
| - Demonstrates some specialized skill sets on top of their general knowledge. | ||
|
|
||
| - Execution: | ||
|
|
||
| - Identifies new areas for improvement/investment. | ||
| - Representing the product to customers directly in small groups. | ||
| - Representing the product to leadership. | ||
| - Use intermediate technical knowledge to understand customer pain points well enough to discuss implementation alternatives with engineering. | ||
|
|
||
| - Teamwork: | ||
| - Begins to mentor junior team members. | ||
| - Gives feedback which influences the work of others. | ||
| - Gather input directly from customers to guide decisions as appropriate. | ||
| - Actively collaborates on solutions to projects outside the PM discipline, e.g. eng, design, marketing and sales. | ||
| - Manage up effectively by communicating the implications of management and leadership requests appropriately. | ||
|
|
||
| ## IC4 | ||
|
|
||
| - Impact: | ||
|
|
||
| - Deliver on projects with high technical and organizational risk. | ||
| - Owns a related set of medium-large products. | ||
|
|
||
| - Scope: | ||
|
|
||
| - Recognizes product, strategic and business issues beyond their immediate domain and suggests solutions. | ||
| - Drives clarity across the organization to produce the ideal solution for customers. | ||
|
|
||
| - Execution: | ||
|
|
||
| - Owns strategy and roadmap for a family of medium-large projects. | ||
| - Use technical knowledge to have a strong technical opinion about the direction of your products. | ||
|
|
||
| - Teamwork: | ||
| - Actively mentors one or more junior team members | ||
| - Actively shapes the product management team’s culture. | ||
| - Works with executive leadership to align on area strategy. | ||
| - Manage up effectively by pushing back on management and leadership requests as appropriate for the overall benefit of the company. | ||
|
|
||
| ## IC5 | ||
|
|
||
| - Impact: | ||
|
|
||
| - Drives and delivers top-level company strategy in a specific area of responsibility. | ||
|
|
||
| - Scope: | ||
|
|
||
| - Applies strategic product and business expertise to the company’s most impactful initiatives. | ||
| - Influences the company’s overall product and business direction. | ||
| - Uses domain expertise to steer the direction of the company. | ||
| - Provides strategic and tactical solutions that are examples for others to follow. | ||
|
|
||
| - Execution: | ||
|
|
||
| - Brings conviction backed by data about what problems we should solve and how we should solve them. | ||
| - Identifies and implements ways that product management can help advance business goals. | ||
| - Drives x-org alignment to advance our business goals. | ||
|
|
||
| - Teamwork: | ||
| - Actively mentors two or more team members. | ||
| - Expertise is recognized across the company. Actively shares insights, upleveling others. | ||
| - Works with executive leadership to drive business goals. | ||
| - Manage up effectively by determining their own tasks and priorities instead of getting those from management. |