Customer Engineer

RevenueBase:

• We're building the data infrastructure that makes AI agents trustworthy instead of error-prone.

• We provide continuously refreshed, verified B2B data for autonomous AI agents and GTM workflows.

• We've tripled growth while maintaining 100% gross dollar retention and staying cashflow positive.

• We power AI agents for Clay, Zoominfo, Dun & Bradstreet, and the next generation of AI GTM tools.

Why We're Hiring This Role:

• The companies building the future of go-to-market are building on top of our B2B data infrastructure. Many are onboarded and running.

• The hardest part of being a B2B data customer is figuring out how to run the right searches across the data to get the business outcome they bought us for. They need a technical partner to help them actually succeed with the product.

• This role exists to own the full customer lifecycle — onboarding, activation, health, and expansion — across every account we have.

• You are the founding hire for this function. When we hire behind you, you hire them.

What You'll Do:

• Own the "first successful search" — every new customer's activation milestone. Get them there, fast. This is the most important thing you do.

• Own customer health across all accounts. Know which customers are getting value, which are quiet, and which are at risk — before anyone asks.

• Drive expansion and cross-sell. As we ship new API surface area (verification, enrichment, discovery, MCP), identify which customers need what and run the expansion conversation.

• Run onboarding at scale. 3-5 new customers per month today, scaling to 10+. Make onboarding light, fast, and reliably successful.

• Be the voice of the customer inside RevenueBase. Sit on top of every Slack channel, every support request, every integration conversation, and tell product and engineering what customers actually need.

• Build the function. Write the playbooks, the health scoring, the expansion motion, and the onboarding framework — then rewrite them when they stop working.

Who You Are:

• You've owned a quota before — NRR, expansion, or retention — and know how to drive it without being pushy.

• You've worked at early-stage companies. You are allergic to process for process's sake. You write the playbook because there isn't one.

• You are the most technical non-developer in every room, and developers respect you. You don't pretend to be an engineer, but you're not precious about getting into the weeds.

• You don't wait to be told. The customer's success is your outcome, and you treat it that way.

Must have:

• Tech literacy — enough to read a customer's integration code (Python, JSON, SQL, you name it), spot what's broken, write a small script to demonstrate an API call, and be credible in a technical conversation.

• B2B data fluency — you know what firmographics, technographics, intent, and contact enrichment are. You understand why an email bounces, why a company name match is hard, and why verification matters.

• API mental model — REST, webhooks, rate limits, authentication, and the difference between a batch file drop and a real-time API call. You can walk a customer through integrating our MCP server.

Nice to have:

• Direct experience in B2B data, sales intelligence, or RevOps tooling

• Experience with MCP servers or LLM-powered agent workflows

• Prior founding CS or founding CE experience at an early-stage company

Your First 90 Days:

• Days 1-30: Shadow every active customer conversation. Write queries against our Snowflake environment. Sit in on sales and onboarding calls. Build a map of all customers — health, usage, expansion potential, risk.

• Days 31-60: Take ownership of onboarding. Run the "first successful search" milestone with every new customer. Publish a customer health scoring framework.

• Days 61-90: Identify and execute your first three expansion opportunities. Ship the v1 onboarding playbook. Tell us what you need to do this job 10x better.

Who You Are Not:

• You have not spent your career at companies with 1,000+ employees and defined CS processes.

• You do not need a playbook to get started.

• You are not looking for a pure relationship role with no technical depth, and you are not looking for a pure engineering role with no customer contact.

Why RevenueBase:

• Product with real traction: Customers rely on our platform in production.

• High ownership: Small team where your work directly shapes the product.

• Customer-driven culture: Activation and retention are how we measure success.

• Growth stage company: Clear product-market fit and momentum.

• Impact over process: Less bureaucracy, more building.

What We Offer:

• Competitive compensation based on experience.

• Meaningful ownership and long-term growth opportunities.

• Flexible working hours.

• Fully remote-friendly team (East Coast / Boston preferred).

• Direct collaboration with founders and core engineering leadership.

Originally posted on Himalayas