Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move product roles to the handbook #1376

Merged
merged 6 commits into from
Aug 13, 2020
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion handbook/engineering/product_documentation.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Whenever a feature is changed, updated, introduced, or deprecated, the pull requ

The developer who made the code change is also [responsible](../../handbook/engineering/roles.md#software-engineer) for writing the initial documentation for new features and updating the documentation for changes to existing features. At the pace Sourcegraph evolves, this is the only way to keep the docs up to date.

It's the [responsibility of the Product Manager](../../handbook/product/roles.md#product-manager) to ensure all features are shipped with documentation (i.e., that nothing slips through), whether is a small or big change.
It's the [responsibility of the Product Manager](../../handbook/product/roles/product_manager.md) to ensure all features are shipped with documentation (i.e., that nothing slips through), whether is a small or big change.

We use the [monthly release blog post](https://about.sourcegraph.com/blog) as a changelog checklist to ensure everything is documented.

Expand Down
30 changes: 9 additions & 21 deletions handbook/product/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,43 +6,31 @@ The product team is newly growing, and consists of all product managers and prod

### Members

- [Product managers](roles.md#product-manager)
- [Product management](product_management/index.md)
- [Christina Forney](../../../company/team/index.md#christina-forney-she-her)
- [Pooja Jain](../../../company/team/index.md#pooja-jain-she-her)
- [M.A.C](../../../company/team/index.md#todo) starting 2020-08-24
- [Product designers](roles.md#product-designer)
- [Product design](design/index.md)
- [Rob Rhyne](../../../company/team/index.md#rob-rhyne)
- [Alicja Suska](../../../company/team/index.md#alicja-suska-she-her)
- [Quinn Keast](../../../company/team/index.md#quinn-keast-he-him)
- [Developer communications](roles.md#developer-communications)
- [Kimberly Hopson](../../company/team/index.md#kimberly-hopson-she-her)
- [Technical writing](technical_writing/index.md)
- [Kimberly Hopson](../../../company/team/index.md#kimberly-hopson-she-her)

### [Roles and responsibilites](roles.md)
### [Roles](roles/index.md)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The roles and hiring sections felt redundant, so I combined them. They still feel a bit redundant to the Members section above, and in order to not have broken links I needed to create the redundant roles/index.md that simply links to the roles pages. If you have ideas how we can clean this up while keeping it top level, I'd love to hear suggestions!

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made this a little better by linking to the docs areas in the Members section, and am now only linking to the roles pages here. Feedback still appreciated!


See [Roles and responsibilites](roles.md)
_Updated 2020-08-12_

### Hiring status

_Updated 2020-07-16_

We are hiring for these roles:

- +4 [Product Manager](https://github.com/sourcegraph/careers/blob/master/job-descriptions/product-manager.md)
- [Product Manager](roles/product_manager.md) - hiring +3
- [Product Designer](roles/product_designer.md) - closed to applications
- [Technical Writer](roles/technical_writer.md) - hiring +1

See [2021 Organizational plan](../engineering/2021_org.md) for more details on areas of ownership.

## [Goals](goals.md)

See [Goals](goals.md)

## [Product management](product_management/index.md)

- [Product process](product_management/product_process.md)

## [Design](design/index.md)

- [Design process](design/design_process.md)

## Resources

### References
Expand Down
2 changes: 1 addition & 1 deletion handbook/product/planning.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Planning

Planning is a continuous process of negotiation between product and engineering. Teams should review the project roadmap weekly with the [Product Manager](roles.md#product-manager) during their team meetings, and update it regularly as new information comes in. The product manager should also review the plans for all projects in the next release for overall coherency. This ensures that projects can work on the schedules that make the most sense for them (subject to the constraint of needing to ship some kind of milestone monthly). A particularly long-term project can have many months of visibility into requirements and plans, and shorter or more experimental projects can be planned with shorter time horizons.
Planning is a continuous process of negotiation between product and engineering. Teams should review the project roadmap weekly with the [Product Manager](roles/product_manager.md) during their team meetings, and update it regularly as new information comes in. The product manager should also review the plans for all projects in the next release for overall coherency. This ensures that projects can work on the schedules that make the most sense for them (subject to the constraint of needing to ship some kind of milestone monthly). A particularly long-term project can have many months of visibility into requirements and plans, and shorter or more experimental projects can be planned with shorter time horizons.

## Planning artifacts

Expand Down
61 changes: 0 additions & 61 deletions handbook/product/roles.md

This file was deleted.

5 changes: 5 additions & 0 deletions handbook/product/roles/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
# Product team roles

- [Product Manager](product_manager.md)
- [Product Designer](product_designer.md)
- [Technical Writer](technical_writer.md)
63 changes: 63 additions & 0 deletions handbook/product/roles/product_designer.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,63 @@
# Product Designer

We are looking for a self-motivated Product Designer with the leadership skills to be the facilitator of design, and the pragmatism to be the person responsible for producing and executing the design. You will work collaboratively with product and engineering to create a highly functional and beautiful experience that delights a technical audience.

Developers [love our product](https://engineeringblog.yelp.com/2019/11/winning-the-hackathon-with-sourcegraph.html) and rely on it daily to ship and deploy better software. Our passionate users provide a constant stream of thoughtful feedback and love engaging with us to help them and their teams solve their toughest problems.

Our [public roadmap](https://docs.google.com/document/d/1cBsE9801DcBF9chZyMnxRdolqM_1c2pPyGQz15QAvYI/edit) shows the product priorities for each engineering team and we use [OKRs](https://about.sourcegraph.com/company/okrs) to communicate company goals for each quarter.

## Responsibilities

You will:

- Contribute to the overall strategy and decision-making about Sourcegraph’s features.
- Drive continual progress towards a cohesive, delightful experience for a technical audience through iterative improvements.
- Have the autonomy to facilitate conversations, identify problems, arrive at solutions, and execute designs.
- Pull together insights to propose a variety of solutions, then collaborate with product and engineering to determine the best solutions to problems.
- Use prototyping and usability testing to inform and validate designs.
- Collaborate directly with customers to inform strategy and design decisions.
- Play a key role in building design culture at Sourcegraph.

We will encourage and support you to:

- Publish blog posts and give conference talks about your work at Sourcegraph.

## Qualifications

- Expertise in designing complex web applications as demonstrated in a strong portfolio showcasing your tried and tested process for tackling design problems, as well as high quality interaction, and visual design.
- Experience building end-to-end experiences in popular design tools (we use Figma).
- The ability to adapt your tools and processes for the velocity of a fast-paced startup where projects have varying requirement levels.
- Experience with usability testing, customer journey mapping, developing personas, wireframing and prototyping, sketching, and other UX design methods.
- The ability to proactively give maintenance to the design system when thinking about how new concepts impact the whole product.
- A knack for giving and receiving feedback, and explaining the reasoning behind your designs.
- A deep understanding of developers, and a strong understanding of Git and Git workflows.

## Nice-to-haves

- Experience designing developer tools.
- Experience working in cross-functional teams on multiple projects in tandem.
- Experience building or contributing to the design of consumer or enterprise applications.
- Experience working with distributed or remote teams.

## Learn more about us

To create a product that serves the needs of all developers, we are building a diverse [all-remote team](https://about.sourcegraph.com/company/remote) that is [distributed across the world](https://about.sourcegraph.com/company/team). Sourcegraph is an equal opportunity workplace; we welcome people from all backgrounds and communities.

We provide [competitive compensation](https://about.sourcegraph.com/handbook/people-ops/compensation) and [practical benefits](https://about.sourcegraph.com/handbook/people-ops/benefits-and-perks) to keep you happy and healthy so that you can do your best work.

Learn more about what it is like to work at Sourcegraph by reading [our handbook](https://about.sourcegraph.com/handbook/).

## Interview process (role currently closed to applications)

1. You apply.
1. We set up a 30-minute call to chat with you about Sourcegraph to find out what you are looking for in your next role.
1. We schedule a 1 hour portfolio review for you to present your past work.
1. **Design exercise:** We give you a problem statement and you walk us through your design process in a 2 hour block.
1. We schedule 5 hours of remote interviews over video chat across multiple days.
- **Design strategy:** We ask you about your past work and accomplishments and how you will apply that to your role at Sourcegraph.
- **Team collaboration:** We ask you about how you work and communicate in a team setting, and how you handle tricky situations.
- **CEO/CTO:** We ask you about what motivates you to do your best work, and we tell you more about the vision for the company.
1. We check your references.
1. We make you a job offer.

We want to ensure Sourcegraph is an environment that suits your working style and empowers you to do your best work, so we are eager to answer any questions that you have about us at any point in the interview process.
66 changes: 66 additions & 0 deletions handbook/product/roles/product_manager.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,66 @@
# Product Manager

You work with engineering, sales, marketing, and design to plan, ship, and grow usage and engagement in specific areas of our product. As an early member of our product team, you have significant product ownership and will communicate directly with our users to drive continuous improvement.

Developers [love our product](https://engineeringblog.yelp.com/2019/11/winning-the-hackathon-with-sourcegraph.html) and rely on it daily to ship and deploy better software. Our passionate users provide a constant stream of thoughtful feedback and love engaging with us to help them and their teams solve their toughest problems.

Our [public roadmap](https://about.sourcegraph.com/direction) shows the product priorities for 2020, our [product team goals](https://about.sourcegraph.com/handbook/product/goals) are our team's focus, and we have [company goals](https://about.sourcegraph.com/company/goals) to communicate what is important across the organization.

## Responsibilities

You will **own an area of the product**\* and:

- Significantly grow usage and engagement of that area and Sourcegraph as a whole.
- Collaborate with, support, and motivate their team to plan and build the solutions to customer problems.
- Add value to the user by surfacing real problems and improving the user’s workflow as a developer.
- Gather customer feedback to validate priorities, improve documentation, and define product requirements.
- Make sure the development team for the product area is working on the most impactful things.
- Maintain a roadmap, backlog, and curate and solicit feedback for the product area.
- Communicate product ideas clearly by focusing on the problems that are being solved, the outcomes, and how we will measure success.
- Be transparent in your internal and external communication. Sourcegraph is open source, so most discussions are public or in channels where you communicate directly with our customers.

\* Product ownership areas: Search, campaigns, extensions and code insights, code intelligence.

## Qualifications

This is a very technical role and requires software engineering experience to effectively communicate with engineers and make educated decisions affecting product scope and performance at scale.

As a result, we expect:

- Experience working as a software engineer.
- Strong understanding of Git and Git workflows.
- Excellent written and verbal communication skills, technical writing ability, and use of data to back up your arguments.
- Ability to stay focused on goals and strategically prioritize work.
- Deep passion for developer tools and productivity enhancements.
- Demonstrated leadership skills and ability to drive and influence product strategy across engineering, design, and distribution.

## Nice-to-haves

- Previous product management experience on a software development or developer tools product.
- Experience building and/or contributing to developer tools.
- Experience working remotely with globally distributed teams.

## Learn more about us

To create a product that serves the needs of all developers, we are building a diverse [all-remote team](https://about.sourcegraph.com/company/remote) that is [distributed across the world](https://about.sourcegraph.com/company/team). Sourcegraph is an equal opportunity workplace; we welcome people from all backgrounds and communities.

We provide [competitive compensation](https://about.sourcegraph.com/handbook/people-ops/compensation) and [practical benefits](https://about.sourcegraph.com/handbook/people-ops/benefits-and-perks) to keep you happy and healthy so that you can do your best work.

Learn more about what it is like to work at Sourcegraph by reading [our handbook](https://about.sourcegraph.com/handbook/).

## Interview process

1. You [apply here](https://jobs.lever.co/sourcegraph/254299f5-f91b-43e2-aa1a-3732963dd296/apply).
1. We set up a 30-minute call to chat with you about Sourcegraph and to find out what you are looking for in your next role.
1. We give you a writing project to see how you communicate and think about product problems.
1. **Product experience:** We review your writing project and dive deep on how you work as a product manager.
1. We schedule 3 hours of remote interviews over video chat across multiple days.
- **Working with customers:** The sales and customer engineering teams talk with you about how you work with customers to gather feedback.
- **Design and Engineering collaboration:** The design and engineering teams talk with you about how you collaborate and work within a team.
- **CEO/CTO:** We ask you about what motivates you to do your best work, and we tell you more about the vision for the company.
1. We check your references.
1. We make you a job offer.

We want to ensure Sourcegraph is an environment that suits your working style and empowers you to do your best work, so we are eager to answer any questions that you have about us at any point in the interview process.

**[Click here to apply](https://jobs.lever.co/sourcegraph/254299f5-f91b-43e2-aa1a-3732963dd296/apply)**
Loading