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.