Skip to main content

Owner

GTM Engineer

Remote - United States (Remote)fulltimemidAdded today

About this role

Owner seeks a GTM Engineer to architect and build the revenue infrastructure powering their AI-native small business platform. You'll own the systems connecting customer acquisition, intent detection, trial conversion, and billing across product, data, and GTM teams—essentially designing the growth engine from the ground up.

What you'll do

  • Design and build infrastructure for lead identification, routing, nurturing, and conversion into ARR
  • Develop billing systems, CPQ flows, Salesforce syncs, and RevOps integrations
  • Evolve Salesforce toward headless architecture for greater engineering flexibility
  • Build platforms enabling Growth, Sales, and Launch teams to deploy AI across their funnels
  • Create unified lead funnel spanning landing pages, lifecycle messaging, and sales workflows
  • Partner cross-functionally with Engineering, Analytics, RevOps, Sales, Marketing, and Finance

What they're looking for

  • CRM platform architecture (Salesforce depth preferred)
  • GTM tools and modern stacks (Clay, Apollo, or similar)
  • AI/ML integration for engagement and automation
  • Billing and subscription infrastructure
  • Data pipeline and analytics engineering
  • API integration and headless architecture design
  • Product thinking and cross-functional collaboration
  • Revenue operations and lifecycle marketing systems
Apply on the employer's site

Opens the official application on the employer’s site. No login required.

Owner

Owner builds an AI platform designed for local businesses, particularly restaurants, enabling owners to operate their services through conversational AI agents. The company is hiring for both software engineers to develop its AI platform and IT support specialists to manage technology infrastructure as it scales.

View all jobs at Owner

Likely interview questions

  • Walk us through a GTM or revenue infrastructure project where you architected a system from scratch—what were the key decisions?
  • How would you approach transitioning a Salesforce instance from traditional to headless architecture while maintaining ongoing operations?
Unlock all 7 questions free — and practice them live →