Product Marketing Manager Assignment + Presentation

• Duration: async assignment + 60-minute presentation
• Details: during this stage in the interview process, we want to understand how you have led and contributed to a meaningful GTM launch. Choose a product, feature, or major initiative you previously brought to market and walk us through the launch from strategy through execution and results. We are most interested in your decisions, your role, how you worked across teams, and the impact.
• Interview structure:
  • Pre-work (async - up to 48 hours prior to interview):
    • Candidate prepares a presentation on one previous GTM launch
    • Brings it to the session and presents (25-30 min)
  • Live session (60 minutes):
    • 25-30 min: Candidate walks through the launch
    • 15-20 min: Discussion and deeper questions
    • 10 min: Retrospective on what worked, what didn’t, and what you would have done differently.
• Audience: Sourcegraph Marketing, GTM, and EPD team members
• Deliverable:
  • Prepare a concise presentation that covers:
    1. The product, market context, and problem being solved
    2. Target audience, buyer, and key insights that informed the GTM strategy
    3. Launch goals and how success was defined
    4. Your specific role, ownership, and key decisions
    5. Positioning, messaging, launch strategy, and timing
    6. Cross-functional partners and how you drove alignment
    7. Key deliverables and channels
    8. Results and measurable business impact
    9. What you learned and what you would do differently
  • Be prepared to discuss:
    1. Where you personally had the greatest impact
    2. Tradeoffs or difficult decisions you made
    3. How you handled disagreement, changing inputs, or execution challenges
    4. How you knew whether the launch was successful

PMM Technical Interview

• Interviewer(s): a member of our engineering team
• Duration: 30 minutes
• Details: this is a conversation about how software gets built and what developers look for in their tools. We’ll talk about the tools you’ve used, how you think about a developer’s day-to-day work, and how you pick up new technical topics. You don’t need to know anything about Sourcegraph going in and you don’t need an engineering background. We’re looking for curiosity and how you think, not memorized definitions. There’s nothing to prepare. This is also your chance to ask an engineer about the product, the team, and how we build.
• Example questions:
  • What dev tools and AI coding tools have you used?
  • Tell me about the last technical topic you had to learn quickly.

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