Customer Engineer

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.

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

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.

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.

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.