Sales Systems Engineer, Enterprise Operations

Perplexity Perplexity · AI Frontier · San Francisco, CA · Enterprise Operations and Systems

This role focuses on building and maintaining the technical systems that support an enterprise sales motion, including CPQ, account/lead scoring, data orchestration, and integrations between Salesforce, Snowflake, and other GTM tools. It requires strong SQL, Salesforce expertise, and experience with reverse ETL and iPaaS tools. The role is hands-on and emphasizes building custom solutions.

What you'd actually do

  1. CPQ: Quote-to-cash configuration, product catalog, pricing rules, approval workflows, discount governance, contract generation. Partner with Finance and Legal on guardrails.
  2. Scoring: Account scoring, lead scoring, PLG activation scoring, intent signal aggregation. Build and maintain scoring models in Snowflake, push scores to Salesforce via reverse ETL.
  3. Data orchestration: Polytomic, Hightouch, and Workato pipelines that move data across Snowflake, Salesforce, NetSuite, Apollo, Unify, and the rest of the stack. Own SLAs, monitoring, and breakage response.
  4. Salesforce engineering: Flows, validation rules, formula fields, custom objects, Apex when needed, Lightning page configuration, permission sets, sandbox management.
  5. Integrations: API-level integration work across our GTM tools. Build custom connectors when off-the-shelf does not cut it.

Skills

Required

  • 5+ years in Sales Systems, RevOps Engineering, Salesforce engineering, or Enterprise Systems at a high-growth SaaS company
  • Deep Salesforce expertise: flows, formula fields, validation rules, custom objects, sharing model, Apex if needed
  • Hands-on CPQ experience (Salesforce CPQ, Stripe Billing, Maxio, or similar) including pricing, approvals, and quote generation
  • Strong SQL. You can write production-grade Snowflake queries and build dbt-style transformation logic.
  • Production experience with reverse ETL (Polytomic, Hightouch, Census) and iPaaS (Workato, Tray, Zapier at scale)
  • Comfort with REST APIs, webhooks, and scripting in Python or JavaScript
  • A bias for building. You have shipped custom solutions when the vendor option was wrong.
  • Operator mindset. You read tickets, you ship fixes, you do not need a PM to translate seller requests.

Nice to have

  • Familiarity with PLG-to-enterprise motion and scoring users into accounts
  • Experience with Apollo, Unify, Loops, Gatsby, Momentum, Floqer, or similar GTM tools
  • NetSuite or Metronome billing exposure
  • Comp plan tooling (Everstage, CaptivateIQ, QuotaPath)
  • Background in entity resolution, dedup, or domain enrichment

What the JD emphasized

  • build a system that scales
  • bias for building
  • shipped custom solutions
  • Operator mindset
  • You read tickets, you ship fixes