Product team onboarding

Welcome to Sourcegraph! As a member of the product team, it is your job to be the voice of the user, and to balance that with the goals of the company. For all roles on the product team, you will have a very similar first week. Weeks 2–4 will vary depending on your role and areas of focus, but the high level goals for each week will be the same.

Onboarding buddy: You will be paired up with an “onboarding buddy” in order to become better acquainted with Sourcegraph team and culture. A buddy will be your go-to person for questions (in addition to your manager and the People Ops team).

Manager checklist

  • Visit the Onboarding process for Hiring Managers page to understand the workflow with People Ops.
  • Create onboarding Google doc and copy in this page to customize week 2–4 tasks and have a personal checklist for the new teammate.
  • Update onboarding doc Week 2–4 with initial projects.
  • Notify People Ops on the tools needed by day one - Tools for new teammates form
  • Grant access to necessary services.
  • Schedule a recurring 1-1.
  • Schedule check-ins for the first and second weeks at Sourcegraph to keep up with onboarding and to create space for answering any questions that might come up.
  • Create a 1-1 doc and add initial discussion items
    • Onboarding doc - YAYYYYYYYYYY WELCOME!!!!! 🎉
      • Your onboarding doc is to help outline the projects and tasks you have over your first 30 days.
      • This 1-1 doc will be where we take notes on discussions, set goals, and make sure you’re on track.
    • 1-1 meetings - What format do you like? What is most helpful to you for these meetings?
    • How do you like to receive feedback?

Week 1 - Getting started

Your objective is to get to know the team and learn as much about Sourcegraph (the company and product) as possible. It is your responsibility to be proactive in your onboarding, and it is the team’s #1 priority to support you and help set you up for success. Everyone will drop what they’re doing to help you. We are so excited to have you on the team and can’t wait to get to know you better!


  • Sourcegraph is an open company. Everything here at Sourcegraph is public unless there is a very good reason for it to be private.
    • One of our values is to be open and transparent
    • Good reasons for things to be private: sensitive customer information, sensitive personal information
    • If you see a “request permission” page for some doc or other resource, it is a mistake. Just ask to be granted access to it (and make a PR to update the handbook so the next person starting is granted access to that system).
  • Unlike at many companies, it is OK (and important) to call out when we did something poorly or when something doesn’t go well (e.g., a sales pitch falls flat). That helps us be real and do it better in the future.

Day 1

  • Complete Process st onboarding
    • Keep the guiding principles from the general onboarding page in mind - we are here to support you and you should act like an owner!
  • Write your 30–60–90 day objectives in your 1:1 doc with Christina

Get to know the team

  • Schedule individual meetings with each person on the Product team
  • Schedule individual meetings with each person on the engineering team you’ll be working most closely with ( this will be in your specific onboarding docs)
  • Schedule a meeting with the Head of Customer Support
  • Get up to speed on what your team is working on

Set up the basics

Get to know the product

Get to know our customers

Know our tools

Understand company and team goals

Get ready to contribute to the docs

Set up your design environment

If you are a designer on the team, use the following resources to get up to speed on design at Sourcegraph.

You’ll find we have a strong base to work from, but we are in the early stages of creating our program. Your input will be critical to our success, so take notes about everything you experience while onboarding. We’ll use them to help us improve our process and the product!

  • Set up Figma
    • Get a tour of from another designer on the team.
    • Review a few usability studies to get an idea of how you will use the product.
  • As you learn the product, if you come across a quick win for better usability based on general heuristics, create a GitHub issue identifying the problem and proposing a quick solution, and tag it with ‘UX’.
  • Suggest a tool you love to the team in the #design channel on Slack!
  • Storybook houses our React component library. We use Chromatic to easily access and collaborate on the components. You can access the React components library in two ways:
    1. Log in to Chromatic with your GitHub account and open Sourcegraph library
    2. from the root of your local development environment run storybook: yarn storybook.
  • Explore and favorite the Google Drive design folder
  • Review the Potential UX projects document

Week 2–3 - initial projects

  • The goal is to give you a handful of projects that will help you familiarize yourself with the product, and get some quick wins in your first weeks.
  • If you see something that you think would be a great project for you to tackle as you’re onboarding, let’s talk about it!
  • We are excited to get you meatier projects, and also want to make sure you have adequate ramp-up time :)

Week 4 - start a larger project

  • Let’s talk about your strengths, interests, areas you’re excited about, as well as what will help drive the team and company goals!
    • Use this document to record issues you’d like to work on as you discover them during your onboarding