Customer Success Manager - US ICNew

Our mission is to bring clarity and control to the world's most complex codebases. AI is accelerating code creation, but the infrastructure to understand, oversee, and evolve that code hasn't kept pace. Sourcegraph gives engineering organizations full visibility across their systems, precise context for their agents, and the ability to execute coordinated code changes  agentic development becomes the dominant engineering paradigm, we provide the context layer teams need to take control of their codebase.

With Code Search, Deep Search, MCP, and Agentic Batch Changes, we deliver on that mission today - giving engineering teams and their AI tools the cross-repo context to navigate massive codebases with confidence, and the ability to make changes across hundreds of repositories panies like Stripe, Reddit, and Leidos rely on Sourcegraph to ship faster and with higher quality. We're backed by a16z, Sequoia, and Redpoint, and proud to operate as a globally distributed team that values high agency, direct communication, and customer love.

If you want to build the infrastructure that lets every engineering team - and every agent they deploy - operate on their codebase with confidence, join us.

• United States

You’ll play a meaningful role on a small, high-performing Customer Success team at a pivotal moment. As a CSM at Sourcegraph, you’ll manage a book of 20 enterprise and commercial accounts, helping developers get real, measurable value out of our products. You’ll own the post-sales relationship end to end, driving adoption, surfacing risk, and getting customers healthy for renewal and expansion.

This isn’t a passive relationship management role. You’ll be in the product, digging into health scores and telemetry, running 1:1 trainings, leading business reviews, and working alongside Named AEs and Field Engineers to move customers forward. Sourcegraph is also at an exciting inflection point as we shift from a seats-based model to consumption, which makes the CSM’s impact more tangible than ever.

Within one month, you will…

• Build relationships with your team, Named AEs, and Field Engineering counterparts
• Learn our product, value proposition, customers, and internal processes
• Shadow customer calls to understand how our enterprise and commercial customers use Sourcegraph
• Begin taking over your first accounts and establishing yourself as a trusted point of contact

Within three months, you will…

• Own regular cadences with your customers, understanding their use cases, building value maps, and tracking adoption health scores
• Identify which customers need more support, which are trending toward risk, and prioritize accordingly
• Start leading product trainings and basic demos independently, without relying on Field Engineering for standard engagements
• Partner with Named AEs on accounts nearing renewal or showing expansion signals

Within six months, you will…

• Drive adoption across your book, getting customers to actively use Deep Search, MCP, and consumption-based features
• Proactively surface risk and opportunity: which customers haven’t signed the AI addendum, who needs to move to cloud, where MAU is low relative to licensed seats
• Run internal business reviews and customer-facing QBRs with documented KPIs
• Serve as the voice of your customers internally, sharing feedback with EPD, PMM, and Support to influence product direction

You’re tech-curious, customer-oriented, and comfortable operating with a lot of autonomy. You don't need someone to build your week for you. You can look at a book of 20-30 accounts, assess the data, identify what needs your attention, and go.

You are genuinely interested in developer tooling and the problems developers face. You don't need to write code, but you need to care about what developers care about, get into Sourcegraph, and guide customers confidently on best practices. Leading a group training without backup from a Field Engineer should feel comfortable, not intimidating.

You are analytical and communicate well across audiences. You can pull up product telemetry, read health scores, spot patterns in usage data, and build a story around what…