Executive Business Partner working session scenario

• Interviewer(s): Gregg Stone, VP of Sales

• Duration: 60-minutes.

• Details: The goal of this working session is to give us all a sense of what it would be like to work together. Below is a hypothetical situation that we would like to play out during this 60-minute session.

  You are new to the role (30 days) when Gregg asks you to meet and discuss organizing an in-person event for the sales/marketing teams. The idea behind this event is to build strong relationships among team members and align on goals.

  Your objective in this meeting is to:

1. Gather all the information that you need in order to be successful at planning and executing this event.
2. Provide recommendations, share potential ideas, and discuss solutions with Gregg.

Our advice:

• Don’t go overboard on preparation or detail.
• Clever ideas are awesome and appreciated.
• We are also looking for your process/framework/principles.
• If you need to take notes, we usually use Google Docs!

Some background info:

• Team org: Sales team and Marketing team
• Publicly referenceable customer logos
• Everything at Sourcegraph and our handbook should be assumed to be accurate and up to date.

A few pointers:

• Ask identifying questions about existing gaps on the team
• Be ready to identify immediate solutions
• Be prepared to have a dynamic conversation to uncover nuances about the teams you will be working with

BizOps: Director of Data & Analytics take-home project

• It’s 2021, and Sourcegraph is growing at a rapid pace. With the launch of Sourcegraph cloud and significant growth in sales of the existing self-hosted deployment option, the VP of Operations is asking you to prepare a plan for upgrading our data infrastructure to be prepared for the next several years of growth.
• We have a complex user journey that can touch a number of websites, apps, and integrations:
  • Data sources:
    • Websites
      • About.sourcegraph.com: Sourcegraph’s marketing website (pages include: a splash homepage, our blog, about us, contact us, press, careers, terms of service, etc.)
      • Learn.sourcegraph.com (learning and tutorials about code search)
      • Docs.sourcegraph.com (documentation)
      • Custom SEO landing pages
      • And more…
  • Core products:
    • Sourcegraph.com: The cloud product, used for searching across the universe of open source code and users’ private repositories. Can be used as an actual product destination or simply as a demo as needed.
    • Self-hosted Sourcegraph instances: Self-hosted webapps, using the same codebase as Sourcegraph.com, but deployed on-premises or in our customers’ private clouds. An example would be Uber’s private Sourcegraph instance—only accessible to Uber employees and contractors, and only containing Uber’s code. It would be accessible to Uber devs on an internal-only domain, like sourcegraph.uber.com.
  • Integrations:
    • Sourcegraph browser extensions: Chrome, Safari, and Firefox extensions that add Sourcegraph features to other websites where users view code (e.g. enhanced code views on sites like GitHub, GitLab, Bitbucket, and more).
    • Sourcegraph editor extensions: downloadable plugins for desktop code editors, such as VS Code, Atom, and Vim, that add some Sourcegraph features locally.
• Key notes:
  • The expectation for privacy is much higher for our downloaded products and self-hosted Sourcegraph instances. E.g. the customers who opt to host Sourcegraph themselves expect us not to track their users’ actions. Instead, we only collect aggregated telemetry from self-hosted Sourcegraph instances, with no individual user-level details.
  • Consumers of this user journey data include nearly every part of the company, from product (core app engagement and product usage data), engineering (application performance data), marketing and sales (top of funnel data and user engagement data for outreach), customer success (customer health and engagement), and more.
  • Our current traffic is ~100k monthly website visitors and cloud product users and ~40k monthly self-hosted instance users.
• Deliverables:
  • Please design a high-level, conceptual data pipeline that would serve our business’s needs. Please name specific recommended tools (or options) to serve at each step of the pipeline. No need to write descriptions of every step, but please be prepared to answer questions about them.
  • Please describe the basic structure of data at the beginning(s) and the end(s) of the pipeline, and be prepared to discuss the data transformations that take place along the way.
  • Finally, please draw or describe (no real data required) the dashboards or reports that you would recommend providing to the CEO, the head of Product, and the head of Marketing each month.
• We recommend that you spend approximately 2 hours on this case study. Please feel free to reach out with any questions!

BizOps: Product Analyst take-home project

This exercise should take 2–3 hours to complete; please don’t take more than that!

• Getting setup: You’ll be using Mode Analytics public datasets to complete this take-home project. Here are the steps to getting into the SQL workspace: _ 1.Create an account if you don’t already have one _ 2.Click the green+in the top right (‘Create report’)to access the workspace * 3.We’ll be using the following Mode Public Warehousetables to complete the exercise:tutorials.playbook_users,tutorials.playbook_events,tutorials.playbook_experiments,tutorials.playbook_emails
• Prompt: For each of the following questions please create charts and/or tables (within Mode or by exporting to a spreadsheet tool if that’s easier) to show your findings. We’re not expecting a slide deck or document to explain your findings, but quick summaries of charts, if needed, are just fine. Keep in mind that in most cases there are no “right” or “wrong” answers; we’re more interested in your approach and thought processes. _ 1. What company is most engaged with the product? _ 2. We ran an A/B test (experiment) to increase ‘like_message’ actions users are taking. Which variant would you recommend going forward with, if any?
• When you’ve completed the project, share your results via static run links along with some availability you have over the next week to review the project with a BizOps team member. When reviewing, you can expect questions about your approach in getting to know the data, the process you took to find the results, results themselves, and how you decided to communicate your findings.

Legal: Corporate & Legal Counsel take-home project

The goal of the assignment is to give you a chance to demonstrate how you think, write, and negotiate while tackling issues that are top of mind for Sourcegraph and our customers.

• Please see the attached MSA redlines (we will provide this to you if you get to this stage in the process) from our prospective customer, a CA-based tech company. Deal summary:
  • On-premise instance
  • 100K USD ACV
• Will you respond to the redlines and include comments to the customer explaining your reasoning for any redlines that you reject or modify? Please accept any redlines that you suggest that we agree to with a brief comment explaining why.
• In addition, please draft a short, casual note with your assessment that you would send to the account executive. Include a short issues list, with the prioritization of issues made clear.

TechOps: Tech Ops IT Engineer take-home project / Technical Interview

The technical interview should be approximately:

• 25 min for questions from Nicky and Dan M
• 10 min questions from you to us
• 10 min to discuss a short take-home project (3 min presentation and 7 min discussion)

Project:

• We have a fully remote team. Tech Ops wants to ensure that our Team Members are appropriately protected from security threats. As part of the onboarding process we want to provide all new hires with a Security Checklist. What would you put on this checklist?
• Please be prepared to present this recommendation on a detailed level in 3 minutes.

Collaboration and communication skills

Similar to the general peer interview (you will talk to a member of the support team), but with a specific focus. The purpose of this conversation is to get a sense of how they approach collaboration and communication. We look for someone who can collaborate equally well with customers (software engineers) and teammates in any role (from sales to product), is able to modify collaboration and communication methods depending on who they are working with/talking to, and who is adept at communicating about complex things in a way that is easy to understand.

Technical knowledge and troubleshooting skills

Similar to the general peer interview (you will talk to a member of the support team), but with a specific focus. The purpose of this conversation is to get a sense of how they approach technical troubleshooting. We look for someone who is very curious, more of a problem solver than a builder, who can truly hit the ground running, and once onboarded requires very little assistance from engineering.

Hiring Manager Interview

During this interview you will meet with the hiring manager on the Customer Engineering team. They will seek to gain an understanding of your customer-facing experience. Specifically, what if any, is your experience in a pre-sales and / or post-sales role as well as what your career aspirations are. You will have an opportunity to ask any questions about the team, role, company, or product.

Take Home & Live Interview with a Customer Engineer

For this interview we want to give candidates an opportunity to learn about our product and assess your capabilities working in the developer tooling ecosystem! Sourcegraph has a public version of our product available here to let users get a sense of product capabilities—it’s connected to public GitHub repositories. We’ll use this instance to guide the project portion of the interview which will be conducted live, via Zoom, with a customer engineer on the team.

There are two main concepts you should get familiar with in advance of the interview:

• Search
• Intelligence

Using search and our intelligence features we’ll emulate a customer use case with you and ask you to demonstrate it live for us. We don’t expect you to know everything, so if you get stuck during the interview, show us how you go about researching our docs to try and find the answer! This is as much about understanding how you approach and breakdown problems as it is getting to the correct answer.

The live project demonstration will be followed by a short Q&A with the customer engineer to give you both a chance to get to know each other more, and you’ll discuss your take home questions (see below) and answers together.

Finally, prior to this interview, we would like you to answer the following questions. Please submit your answers to these back to us. We will review your answers as part of the 15 minute Q&A in the interview:

1. Explain how Sourcegraph can improve code review flows for dev teams. Explain the challenges of code-review and how Sourcegraph addresses those.
2. What are 3 examples of something a developer can search for in Sourcegraph that would help them make their code more secure
3. How can Sourcegraph help reduce the time to onboard a new dev?

We’ll conduct the interview in the following format:

• 20 minutes: live use-case demonstration
  • The customer engineer will ask you to perform a few basic search and intelligence functions
  • You will be sharing your screen (both the Sourcegraph public instance and our docs)
• 15 minutes: Q&A from customer engineer to learn more about you and your capabilities and discuss your take home answers
• 10 minutes: general Q&A with customer engineer
  • Ask anything you want! It’s your chance to learn about the team, the role, and the company from a peer!

Customer Scenarios Interview, Live Working Session Instructions

For this interview round, you will have an hour-long working session with a Customer Engineer on the team and one of the CE leaders. This working session is intended to help us understand how you approach customers and customer meetings. The working session will cover 4 prompts, spending approximately 10–12 minutes on each of them.

Important note: Please make a copy of this deck and use it to present on the details below.

A summary of the 4 prompts are provided below:

1. Preparing for a customer call: See below for some meeting notes taken by your Account Executive (AE) from an initial meeting with a prospect. The AE is requesting that you prepare a demo. Based on the notes provided: what would your demo agenda be, what would your talking points be during it, what questions do you still have for the AE and / or the customer, what additional information do you need, what would be your ideal next step after that meeting and how do you get there?
2. Discovery during a customer call: See below for some high-level information about a prospect put together by a Sales Development Rep (SDR). They are requesting that you and an AE join them on a second conversation with the Director of Developer Productivity and several IC engineers. What are some things you’d want to uncover during that next meeting, what would you ask, what would you share, what in your mind is the overall goal of that meeting?
3. Dealing with detractors: Your AE is asking you to join a meeting with a prospective customer. The AE has met with the prospect a couple times and the initial feedback you’re hearing from the AE is that the prospect isn’t seeing the value in Sourcegraph and does not feel like it’s compelling enough for them to consider at this time given other priorities they have. How do you handle this situation? What’s your game plan with your AE for that meeting?
4. Managing customer expectations and internal handling: You are working with a customer during a trial and they are running into an issue trying to set up one of their code hosts. How would you handle this situation? What do you say to your customer? Who internally do you engage with? What if you learn that what they are trying to do is actually a feature request; how does that change your approach?

The agenda for the meeting will go as follows:

• 0–2 mins: Intros and recap of this interview stage
• 2–14 mins: Prompt 1
• 14–26 mins: Prompt 2
• 26–38 mins: Prompt 3
• 38–50 mins: Prompt 4
• 50–60 mins: Feedback and Q&A

Important Note: Keeping the timing of the interview will be your responsibility. If you’re running out of time on a prompt, it is better to wrap up the most salient points, and move on to the next prompt. It is important that 10 minutes be left at the end for feedback.

Finally, as you prepare for this it may be useful to read some of our customer case studies to understand how they have solved their problems and found value from our products. It may also be helpful to read about our five core use cases.

Prompt #1: AE Notes

1. Current team size:
   • 200 engineers. LinkedIn only shows 43 as many engineers are coming from acquired software companies. This will help accelerate their development, the goal is to improve their customer experience of their betting platform.
   • 100% growth in last year
   • 50% growth next year
2. Why Anything (where is the need from)?
   • They are acquiring companies to grow (new markets, products), this has resulted in them having to manage more code hosts and on board devs at 100% growth rates. Cross repo changes are key as they grow. They now use local IDEs + GitHub and GitLab search, no cross host search
   • Efficiency is poor, devs keep writing new code rather than reusing what they have access to - need to be more efficient
   • Errors are creeping - i.e. they made a recent Redis configuration change and did not apply it to all the relevant files, it is difficult to see where all changes need to be made
3. Why Sourcegraph and why now?
   • They have lots of new engineers via acquisitions, they bring in new code on different code hosts. They need a tool for ensuring everyone understands the code across all code hosts
   • They have three code-hosts: 2 GitLab, 1 GitHub

Prompt #2: SDR Notes

A prospect (Director of Developer Productivity) came in last year and talked to the previous VP of Sales. Her team was given a license key for trial but COVID hit and the trial was put on pause. They currently have a free version but need to scale their users.

• Use case: primary use case is search and then Batch Changes. She wants 2 sets of users. Power users group with Enterprise features mostly search and batch and 2nd group just for daily users using search and intel. Roughly around 250 devs
• Codehost: Primarily GitLab but they have GitLab as well just for open source projects
• # of repos: 1500 (most of them not active) 300 active. 350,000 LOC for 5 repos
• LOC: Roughly 3–4M
• Lang: Go (adding more Go into their code base), Python 60%, JS 20% and PHP, Kotlin, and Swift rest 20%
• Architecture: microservices.
• Deployment setup: Kubernetes
• Timeline: no timeline but the sooner they can start a POC the better

The technical champion said there aren’t any initiatives driving this re-engagement but they‘ve wanted this tool for the longest time. The biggest thing she wants to walk away with is that we can accommodate the 2 sets of user groups: power users, and daily users. She wants to understand pricing, and what next steps would be towards a more formal trial of our Enterprise product.

Hiring Manager Screen

During this stage of the interview, you will meet with the hiring manager. During this conversation they’ll seek to understand both your exposure to a technical product and audiences and how you lead in a fast-growth organization.

Cross-Functional Collaboration with a Peer

You’ll meet with a potential peer in an adjacent team with whom we want to understand how you build relationships and partner with other leaders and how you manage across adjacent teams.

Leadership & Team Management with 2 IC CEs

You’ll meet with two individual contributors on the CE team to learn about how you build relationships within a team and how you lead, mentor, and develop others.

Working Session: Leadership Scenarios Interview, Live Working Session Instructions

For this interview round, you will have an hour-long working session with the Customer Engineering leadership team. This working session is intended to help us understand how you approach both organizational and customer scenarios as a leader. The working session will cover 4 prompts, spending approximately 10–12 minutes on each of them. It is recommended you take time to prepare in advance based on the details below.

A summary of the 4 prompts are provided below:

1. Account/Deal Review: Two core responsibilities of this role are to perform regular reviews of your team’s book of business and making technical/strategic suggestions to unblock issues that arise. How will you go about performing such reviews with the members of your team? What are your expectations during these reviews; for net new prospects, for existing customers with upcoming renewals? From your past experiences, what do you expect your team to provide to you and on what cadence? Where is this information stored / maintained? If, on a net new deal, you uncover a deal-blocking technical requirement that we cannot fully meet, how do you handle that with your CE? With adjacent teams?

2. Escalation Handling: You are receiving feedback from cross-functional leaders that there are concerns about one of your employees. Their paired Account Executive is requesting to be assigned with a new CE stating that they feel they are not able to progress deals forward due to lackluster performance by the CE during calls and demos. How do you handle this situation? What do you share with the CE? How would you understand if the CE needs to make changes? How would you work with them to improve performance and what would you do if you do not see the improvements you expect?

3. Change Management: We are in a hyper-growth phase and there are several key initiatives that will likely be rolling out over the course of the next several quarters. A key responsibility of this role is to align and train your team, introduce, implement, and manage organizational change, and anticipate emerging needs to iterate quickly. One such initiative we expect to need to implement across the CE organization in the near future is introducing a subset of individuals with the technical skills to be able to test/validate customer edge cases prior to progressing a deal forward. This is outside the current CE responsibilities today and Engineering believe that this is best served from within CE as the team responsible for the technical success of the customer. See below for more context on this prompt. How would you approach this change with your team? How will you uncover and handle objections from within the team? What will you do personally to oversee this broad initiative?

4. Your 30–60–90 Day Plan: What would your personal 30 / 60 / 90 day plan be for joining the team as a leader? What would you personally need to ensure success executing against this 30 / 60 / 90 day plan? How will you communicate and ensure alignment with our leadership team during your 30 / 60 / 90 day plan?

The agenda for the meeting will go as follows:

• 0–2 mins: Intros and recap of this interview stage
• 2–14 mins: Prompt 1
• 14–26 mins: Prompt 2
• 26–38 mins: Prompt 3
• 38–50 mins: Prompt 4
• 50–60 mins: Feedback and Q&A

Important Note: Keeping the timing of the interview will be your responsibility. If you’re running out of time on a prompt, it is better to wrap up the most salient points, and move on to the next prompt. It is important that 10 minutes be left at the end for feedback. You are more than welcome to use slides to facilitate this conversation or personal notes—whichever you feel is most appropriate.

Prompt 3 additional notes: The CE organization is pre- and post-sales oriented to the overall technical success of our customers: from the initial deal through our long term engagement. The types of activities that we perform as part of our core responsibilities are described here. These activities align with traditional Sales Engineering, Solution Architecture, and Technical Account Management organizational responsibilities because we essentially wear all of these hats. How we currently interact with other teams is described here. As the team accountable for our customers’ technical success we recognize the need to inspect opportunities from the lens of technical requirements aligning with our product and to validate edge cases or customer-specific requirements. We expect that a new, dedicated sub-team will work with the account CE to perform these technical validation steps.

Content working session

• Duration: 60-minutes.
• Details: during this stage in the interview process, we try to get a sense of your approach and thought process when reviewing writing drafts submitted by team members. You will be given a blog post draft to review for the first 30-minutes of the session, after which you and the hiring manager go through how you approached the piece and talk about the changes you made and why.

Technical Content working session

• Duration: 60-minutes.
• Details: during this stage in the interview process, we try to get a sense of how you think about content. You will be given (2) pieces of content to read through for the first 30 minutes of the session, after which, you and the hiring manager will take the last 30 minutes to go through what you liked, disliked, and what you would change about each piece and why.

Senior Digital Marketing Manager working session

• Duration: 60-minutes.
• The Goal: The purpose of this working session is to give us all a sense of what it’d be like to work together and make sure we have a shared understanding of the role and goals. This is not meant to be stressful or require a lot of preparation. Part 1: Methodology & Planning (20 Minutes)
• Coming out of our conversations we’ve taken an action item to better understand your campaign planning and activation methodology. - What are your ideas for a long-term, evergreen brand activation across the various digital channels? - What would a successful campaign look like? - How would you monitor and share results? Part 2: Creativity & Collaboration (20 Minutes)
• We’ve just wrapped up our H2 off site where the brand team led a brainstorm about big ideas for a second half awareness campaign focused on quick wins targeting developers.
• Top 3 creative ideas to fuel digital marketing campaigns directed at a DevOps Audience. These creative ideas can be part of the long-term brand awareness plays, or quarterly campaigns
• Include your timeline for concept-to-execution
• What would your goals be for these quick win campaigns?
• What are some key deliverables you’d expect to see from these campaigns?
• Who will you collaborate with and why?
• How would you approach bridging these awareness activities with contact acquisition/product sign-ups?
• NOTE: Please don’t go overboard on preparation, plans, or detail. A Google Doc outline is how we’d do this kind of thing internally, so that’s best. Doesn’t have to be pretty. If you prefer slides, that’s fine. This will be a casual back and forth conversation; not a formal presentation.

Program Manager, Demand Gen Campaigns working session

• Duration: 60-minutes.
• Part 1: Creativity & Collaboration (20 Minutes)
  • Coming out of our conversations we’ve taken an action item to better understand your creative campaign planning and activation methodology.
  • Problem: We need a meeting maker campaign to support sales pipeline goals. Instead of using traditional activation methods, we want this to be a product-led initiative.
    • Task: Create 3 product-led meeting maker campaigns to drive meetings to Sales
    • Audience: Developer Team leads, leaders, and senior leadership
  • Please include:
    • Your create ideas and what inspired them
    • Include your rough timeline for concept-to-execution
    • What channels will you use to activate?
    • Who will you collaborate with?
    • Do you have any out-of-the-box ways to get these in-market?
• Part 2: Data-Driven (20 Minutes)
  • Your meeting maker program is in-market and showing early signs that it’s going to be successful. The team is asking for data to understand how we’re measuring and planning to expand if it is successful.
    • Choose one of your meeting makers and consider the following:
    • What would a successful campaign look like?
    • When will it be time to change strategies?
    • How would you monitor and share results?
    • Which metrics are most important and why?
    • What are some key deliverables you’d expect to see?
• Part 3: Q&A

Developer Educator working session

• Duration: 60-minutes.
• During this stage in the interview process, we try to get a sense of your approach and thought process about curriculum and writing. You will be given a curriculum and short tutorial draft to review for the first 30 minutes of the session, after which you and Lisa will take the last 30 minutes to go through your thoughts about that approach and talk about your feedback and what you would add.

Product Marketing Manager working session

• Duration: 60-minutes.
• The goal of the working session is to give us all a sense of what it’d be like to work together and make sure we have a shared understanding of the role and goals. This is not meant to be stressful or require a lot of preparation.
• First, we’d like to cover some general stuff:
  • Your 20-second Sourcegraph pitch: Imagine a senior eng at your current company asked you what Sourcegraph is. We don’t expect this to be super polished or even 100% correct - we want to hear your spin on what we’re selling and the value proposition.
  • What do you need to be successful? (tools, resources/special budget for anything, specific commitments from other teams, anything from me, etc.)
• Then we’d like to hear, at a high level, how you would approach putting together a GTM plan for the [TBD Product] GA launch.
• This could easily take several hours, but we’re just looking for a 60-min conversation total (including the general stuff above). You don’t need to put together a full plan!
• Please don’t go overboard on preparation, plans, or detail. Clever ideas are awesome, but we’re looking for your process/framework/principles. A Google Doc outline is how we’d do this kind of thing internally, so that’s best. Doesn’t have to be pretty. If you prefer slides, that’s fine. This will be a casual back and forth conversation; not a formal presentation.
• Feel free to reach out to Andy with any questions.

Senior Customer Marketing Manager working session

• Duration: 60-minutes.

• The goal of the working session is to give us all a sense of what it’d be like to work together and make sure we have a shared understanding of the role and goals.

  • Part 1: Driving engagement with our Customer Advisory Board members The first part of the meeting will be with Andy Schumeister (Director of Product Marketing), Victoria Yunger (Product Marketing Lead, Enterprise), and Alex Isken (Product Marketing Manager, Cloud).

  • First, you’ll share your 20-second Sourcegraph pitch: Imagine a senior eng at your current company asked you what Sourcegraph is. We don’t expect this to be super polished or even 100% correct - we want to hear your spin on what we’re selling and the value proposition.

  • Then, we’d like to hear your ideas for how we can drive engagement with our Customer Advisory Board members in-between meetings in order to provide even more value for members.

  • Please don’t go overboard on preparation, plans, or detail. Clever ideas are awesome, but we’re also looking for your process/framework/principles. A Google Doc outline is how we’d do this kind of thing internally, so that’s best. Doesn’t have to be pretty. If you prefer slides, that’s fine. This will be a casual back and forth conversation; not a formal presentation. You’ll also have an opportunity to ask the team questions during this portion.

  • Part 2: Setting you up for success

  • Then, you’ll meet 1:1 with Andy where you’ll have a chance to discuss the role and share what you need to be successful: tools, resources/special budget for anything, specific commitments from other teams, anything from Andy, etc.)

Manager of Internal Communications working session

• Duration: 60-minutes.
• The goal of the working session is to give us all a sense of what it’d be like to work together and make sure we have a shared understanding of the role and goals. This is not meant to be stressful or require a lot of preparation.
• First, we’d like to cover some general stuff:
  • Your 20-second Sourcegraph pitch: Imagine a senior eng at your current company asked you what Sourcegraph is. We don’t expect this to be super polished or even 100% correct - we want to hear your spin on what we’re selling and the value proposition.
  • What do you need to be successful? (tools, resources/special budget for anything, specific commitments from other teams, anything from me, etc.)
• Then we’d like to hear, at a high level, how you would approach putting together Sourcegraph’s 60–90 minute Q1 kickoff this February.
• Q1 company kickoff
• This of course takes hours of planning, but we’re just looking for a 60 minute conversation total (including the general stuff above). You don’t need to put together a full plan!
• Some (hypothetical) updates to account for:
  • We missed our Q4 revenue target and are slightly under for the fiscal year, but current pipeline has us on track to hit Q1 goals
  • We’re updating the company travel policy from one individual trip per year anywhere in the world to collaborate with a coworker, to a regional meetup trip (west coast NA, east coast NA, EMEA)
• Please don’t go overboard on preparation, plans, or detail. Clever ideas are awesome, but we’re looking for your process/framework/principles. A Google Doc outline is how we’d start off content planning. Doesn’t have to be pretty. If you prefer slides, that’s fine. This will be a casual back and forth conversation; not a formal presentation.
• Feel free to reach out to Amie (amie.rotherham@sourcegraph.com) with any questions.

Senior People Partner working session

• Duration: 60-minutes.
• Our working session is designed to give us more insight into how you’d think about and approach typical scenarios you might be called on to provide support to managers on. We’ve detailed three scenarios for you to walk us through the way you’d think and respond to each scenario. For each scenario please walk us through:
  • How would you approach this situation and why? What risks or concerns does each scenario present?
  • Who would you involve, why and how?
  • What feedback would you give the manager concerned?
  • What, if anything, might be changed internally based on this situation arising?
• We will provide the detailed scenarios via email 24 hours before your scheduled interview.
• Note: you don’t need to submit anything (in writing or presentation) ahead of the interview - just structure your thoughts and talk us through it! We’ll ask questions as they come up.

Product manager

Product designer

Product Design Intern

User Researcher

Sales Development Representative:

Enterprise Account Executive

Regional Sales Director

Recruiter assignment

• Interviewer(s): NA—this is a take home assignment.
• Duration: we expect this to take no more than 1 hour.
• Details: we want to ensure we understand your approach to proactively reaching out to and engaging with passive talent. Instructions:
• Step 1. You are the newly assigned recruiter for the [pick a job on our website] role. As a first step, you’ll want to have an intake meeting with the Hiring Manager. What questions do you plan to ask to gain a full understanding of the role?
• Step 2. We have posted the job and have received zero applicants, so we need to go out and recruit the right person. Please identify 5 target candidates and explain 1) how you found them (what search string(s) did you use) and 2) why are you targeting them specifically?
• Step 3. As we know, rarely do we hear back from a candidate after our 1st message or call. Pick one of the above profiles and please describe your outreach “campaign.” What steps will you take to engage with this candidate? Please 1) include example inmails, emails, voicemails etc, and 2) please explain your approach and why you chose to craft your outreach campaign in this way. Your ultimate goal is to secure a call with the candidate.
• Step 4. Good news! The candidate you messaged in step 3 is interested in having an exploratory conversation. How do you describe/sell Sourcegraph to them?