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).
- Visit the Onboarding process for Hiring Managers page to understand the workflow with People Ops.
- Create an onboarding Google doc for the new teammate
- Link to this page and relevant team specific pages such as designer onboarding
- Customize your teammates onboarding tasks as required
- Update the onboarding doc with initial projects for weeks 2–4
- Notify People Ops on the tools needed by day one - Tools for new teammates form
- Sourcegraph organization on GitHub
- Invite to GitHub teams, including @sourcegraph/everyone
- Suggest people the new teammate should create a 1:1 with
- 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. Some suggestions:
- 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?
- Link the onboarding doc - YAYYYYYYYYYY WELCOME!!!!! 🎉
- Your onboarding doc is to help outline the projects and tasks you have over your first 30 days.
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).
- When you have a question, try to ask publicly. Other people probably have the same question.
- In a DM a teammate might say: “Do you mind asking this publically? I’ll answer there”. You can use this phrase too to help generate open conversations.
- 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.
- 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 your manager
Get to know the team
- Schedule individual meetings with the Product team members suggested by your manager
- 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)
- Get up to speed on what your team is working on
- Team handbook page(s), to learn about the team and its internal processes
- Sourcegraph user docs
Set up the basics
- Configure your GitHub notifications.
- Make sure that your Name is set to your First and Last name on GitHub so that other teammates can easily indentify you. Go to GitHub -> Your profile -> Edit profile -> Fill out the ‘Name field’ -> Save
- Familiarize yourself with our team chat and join team channels on Slack, as well as any other channels you find interesting. Product team chat documentation.
- Set up your local development environment. If you encounter any issues, ask for help in Slack and then update the documentation to reflect the resolution (so the next person that we hire doesn’t run into the same problem).
- You will need to run Sourcegraph locally to test and validate work that engineering is doing, to provide early feedback, or to review the UX of recently implemented work.
- Add Sourcegraph as a browser search engine. To search our private code, log in to our internal dogfood instance (
k8s.sgdev.org) and add another entry:
- Install a text editor of your choice. A lot of the team uses Visual Studio Code.
Get to know the product
- Review product resources
- Learn how the Customer Engineering team gives demos and talks about the product in the product demo recording.
- Read about search queries and perform your first searches.
- Work through the questions from the Sales Onboarding Quiz to make sure you understand key concepts. Feel free to skip any obvious answers and discuss any questions you have or knowledge gaps with your manager.
- Record yourself completing the Sales 10 Step Demo Certification.
- How to make configuration changes to sourcegraph.com
Get to know our customers
- Watch the demo videos & recent Chorus.AI recordings with customers
- Familiarize yourself with customer feedback channels:
- HubSpot surveys
- Slack #feedback channel
Know our tools
- Watch ProductBoard’s how-to videos as an intro
- Walk through ProductBoard with someone from the team
- Watch Figma for Sourcegraphers part 1 to learn how we use the application
- Watch Figma for Sourcegraphers part 2 (intro to the Wildcard Design System)
- Read Figma developers guide
- We use Amplitude for analytics on Sourcegraph Cloud. More on Amplitude here.
- Walk through UserTesting.com with one of the designers on the team
Understand company and team goals
Get ready to contribute to the docs
- Read the content guidelines for contributing to the handbook, product docs, and product copy
- Google Cloud Storage access: Ask in #product to be added to the
- Screenshot/GIF making software: See the handbook for guidelines about software. Expense the program that works for you when you need it.
- Product documentation guidelines
- Docs to Markdown add-on for Google Docs
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