Founding Deployment Strategist JD

AutonomyAI; Northern (KY); Hybrid; USD 90,000 - 120,000; Full time

Job summary

AutonomyAI is seeking a Customer Success/Account Manager to own retention and expand revenue with enterprise accounts. You will lead post-sale handoffs, set usage goals, and drive weekly activation while coordinating with product and forward-deployed engineers.

You will manage engineering relationships, ensure rapid PR resolutions, and hand off new expansion opportunities to the account execs, while maintaining top-tier support communications.

Qualifications

• 3-5+ years in customer success or account management at a B2B software company selling to engineering or product teams.
• Able to read tech workflows, discuss CI concepts, and converse with VP of Engineering.
• Strong data mindset with experience in usage analytics and CRM tooling.
• Excellent written communication in English.

Responsibilities

• Own gross revenue retention and renewals management from contract start.
• Run post-pilot handoff and first 90 days with measurable milestones.
• Drive weekly active usage within accounts and coordinate with product and engineering.
• Manage engineering relationships and ensure rapid response to PR feedback.
• Identify and hand off expansion opportunities to account executives.
• Maintain high support quality with timely responses and clear customer communication.
• Build onboarding playbooks, health scores, renewal timelines, and exec reviews.

Skills

Customer success

Account management

Data-driven

Technical empathy

English writing

Tools

CRM

Support tooling

Usage analytics

Job description

We have a fast-growing customer base and no one whose job is keeping them. Retention has been carried by the product, the founders, and the forward-deployed engineers who run onboarding. That worked to here. It will not work at twice the account count, and the accounts that matter most now are enterprises where the person who bought is not the person who uses the product, and the engineering team that reviews our pull requests did not ask for us.

Our product is unusual for a customer success job: it ships code into the customer's codebase. Success is not a login. Success is a product manager writing intent on Monday and a merged, verified pull request on the customer's production surface by Wednesday, week after week, with the engineering team trusting it more each month. When that loop is running, customers expand. When it stalls, they churn quietly at renewal. You own making sure it runs.

What you will do

• Own gross revenue retention. Every renewal is yours from day one of the contract, not day 300. You know each account's renewal date, its usage trend, its champion, its engineering skeptic, and its risk level, and the CEO can see all of it on one page any Monday.
• Run the post-pilot handoff and the first 90 days. Pilots convert on a signed rubric and a pull-request ledger our forward-deployed engineer keeps. You take the account from there: usage goals in writing, weekly operator cadence, monthly executive readout with the numbers that matter (tasks shipped, merge-without-rework rate, engineering review time saved).
• Drive weekly active usage inside each account. Our activation and retention data is clear: accounts that reach a weekly rhythm of tasks stay and grow. You get operators (product managers, designers, business analysts) to that rhythm, you find out why they stall, and you route product fixes back with evidence.
• Manage the engineering relationship. Client engineers are the reviewers of our work and the most common source of churn. You keep the pull-request ledger visible, the rejection categories honest, and the fix loop inside 24 hours, working with our engineering owner for the account. A comment left for two days is a verdict. You make sure it is answered in ten minutes.
• Find and hand off expansion. New teams, new repos, new product surfaces, the second door (a customer's IT or operations group). You spot it, you qualify it, and you bring the account executive in.
• Own support quality. Tickets flow through our support desk. You make sure response times, escalations, and the "what shipped this week" note to customers are consistent, and you are the internal voice of the customer in the weekly product review.
• Build the playbook. Onboarding checklist, health score, renewal timeline, executive business review template, churn post-mortem. You are the first hire in this function. What you write becomes how the next three CSMs work.

Preferred Qualifications:

What you must already have

• 3-5+ years in customer success or account management at a B2B software company selling to engineering or product teams, with a book of business you personally owned and a retention or expansion number you can defend.
• You are technical enough to be trusted by engineers. You can read a pull request, explain what continuous integration is, follow a code review thread, and hold a conversation with a VP of Engineering about review load. You do not need to write production code.
• You have handled the buyer-is-not-the-user problem. You know how to keep an executive sponsor engaged, a champion promoted, and a skeptical team from quietly opting out.
• You run on data. Usage analytics, CRM, support tooling, and a spreadsheet you built yourself. You notice a usage drop before the customer mentions it.
• You write clearly and briefly, in English. Most of our accounts are in the US. Weekly customer notes, executive summaries, and internal escalations all need to read as a peer wrote them.
• You use AI tools yourself, daily. Our customers are buying a new way of building software from us; you need to be a credible example of it.

Nice to have

• Experience with AI developer tools, infrastructure, or any product where adoption depended on an engineering team's trust.
• Experience turning a founder-led post-sale motion into a function, at a company between $2M and $20M ARR.
• Hebrew for the Israeli accounts.
• Experience running onboarding or implementation alongside a forward-deployed or solutions engineer.

How we work

• We iterate in public. Work-in-progress is shared early; nobody disappears for three weeks and returns with a masterpiece.
• Planning lives in artifacts, not meetings. A written memo beats a recurring sync.
• Blockers are yours to resolve, not to upscale indefinite.
• One number per person. Everyone knows what they own.

If that list reads as refreshing, we should talk. If it reads as harsh, we probably should not.

What we offer

• A product whose success metric is visible in the customer's own repository, which makes your job measurable in a way most customer success roles are not.
• Meaningful equity and competitive compensation, with a variable tied to your retention number.
• Direct work with the CEO, VP Sales, CTO, and the engineers who onboard your accounts. No layers.

Process

Fast and respectful of your time: an intro conversation with the VP Sales, a deep dive with the CEO, a paid work sample built on real anonymized account data (usage, ledger, renewal dates: tell us which three accounts you would call this week and what you would say), a conversation with the CTO on how the product actually works, references including a customer you kept, and a decision within days, not weeks.