Regional Director of Pooled Customer Success

Coderabbit

Where
Hybrid in San Francisco
Pay
$143 an hour

Posted 41 days ago· Checked live at Coderabbit 1 hour ago

Stale: open 41 daysUp for more than two weeks. It may already be filled.

See how you score for this job

One sentence and your resume. We score it against what Coderabbit asks for, line by line.

See my score
Is this job still open?
Yes. We checked it live on Coderabbit's own hiring page 1 hour ago.
What is the job?
CodeRabbit is the governance and control layer for agentic software development, helping engineering teams trust the code they ship. AI can generate code faster than people can review and understand it. Teams still need to know whether each change solves the right problem, fits their architecture, and is safe to ship.
What does it pay?
$143 an hour, as the posting states.
Our verdict
Stale. Up for more than two weeks. It may already be filled.

What the job is

CodeRabbit is the governance and control layer for agentic software development, helping engineering teams trust the code they ship. AI can generate code faster than people can review and understand it. Teams still need to know whether each change solves the right problem, fits their architecture, and is safe to ship.

What you'll own

  • Hiring and managing the pooled customer success managers, starting with the first hires in your first quarter
  • Queue design: which signals create work, how work is prioritized, the response and resolution standards, and how a case closes
  • The routing rules between the digital, pooled and named lanes, including the escalation path out of digital and the hand-back when an account grows into named coverage
  • The playbook library, one per trigger: what a CSM does on a dormant account, a solo user, a stalled onboarding, a cancellation notice, an approaching renewal. Written with the Content and Enablement Specialist and kept current from what the queue teaches you
  • The save lane: cancellation and non-renewal signals routed to a person, the reason captured on every one, and the fixable ones fixed
  • The expansion hand-off: when the team surfaces seat headroom or a buying signal, the account goes to the account executive working the scaled lanes, with the context they need to close
  • The team's readout: queue volume by trigger, time to first response, time to resolution, configuration movement, and retention of covered accounts, built with the Success Analytics Engineer and read monthly
  • Capacity: how many accounts one person on the queue can carry, measured from the queue, and the case for extending pooled coverage further down the base as triggers and playbooks mature

Nice to have

  • Experience with health scoring or trigger-based outreach in a success or support platform
  • Familiarity with Pylon, Customer.io http://Customer.io, PostHog, Salesforce or their equivalents
  • Familiar with AI tooling and examples of you using it in similar roles
  • You have used CodeRabbit or another AI code review tool on your own repositories

Similar open jobs

Account manager jobs in San Francisco (230)Jobs in San Francisco (11741)