Growth GTM Engineer, Revenue Operations
Company websiteperplexity.ai (Perplexity, opens in new tab)
Base salary $175K – $235K
Employer-published annual base salary, USD. Advertised base range in San Francisco, CA +2 more
You apply on the employer's own site. Six Figure Work does not handle applications.
- LocationSan Francisco, CA +2 more
- WorkplaceHybrid
- Status at last checkSource accepting applications when checked
- Last checked (3 h ago) · observed since
All places named
- San Francisco, CA
- Austin, TX
- New York City, NY
About this job
In 2026, we launched Computer, the defining product for the new era of agentic AI. Millions of people and teams adopt Perplexity and Computer on their own, and our marketing programs bring in thousands more leads. To turn that demand into pipeline, every lead has to be enriched, scored, and routed to the right next step within minutes.
We're hiring a Growth GTM Engineer on the Revenue Operations team to own the lead-to-engagement engine: the enrichment platform that completes every marketing and product lead, the routing that sends each lead to nurture or to BDRs and Sales, and the syncs that move data from our warehouse into Salesforce and our GTM tools. You'll also put lead and account scores to work with Data Science, who own the scoring models, and help deliver our BDRs' prospecting tools.
You'll report to the Head of Pipeline Operations, who sets the priorities for this work and owns our marketing automation platform, campaign operations and attribution.
You'll build mostly with AI, so we care more about your instinct for go-to-market systems than your depth in any one programming language. You'll measure everything you build against meetings, pipeline and revenue.
Tech stack: Salesforce | Clay | Reverse ETL (Hightouch or similar) | Routing and scheduling (Default, Chili Piper or similar) | Snowflake | SQL | Python | Computer | LLM APIs
Why Perplexity is different
Craftsmanship. We build high quality, tasteful products targeting both the AI native and AI curious.
Ownership. You identify the problem, design the solution and ship it.
Entrepreneurship. We think like founders, act with urgency, and hustle to deliver for each other and our users.
Scholarship. Work among highly talented peers, pursuing knowledge and truth, upleveling ourselves, our teams, and our products.
Partnership. We amplify each others' strengths, break down silos, and give selflessly to help our colleagues deliver excellence.
What you'll do
Own the enrichment platform. Design and run waterfall enrichment across third-party providers, AI research agents and first-party data for every marketing and product lead. Handle lead-to-account matching, deduplication, field governance, data freshness and provider cost. Publish enriched data to the warehouse for Data Science and other teams to use.
Own lead routing. Design the decision logic that sends each lead, from marketing programs or product usage, to Marketing for nurture or to a BDR, AE or Account Manager for engagement, based on score, segment, territory, account ownership, capacity and existing opportunities. Co-define lifecycle stages, handoff SLAs, recycle rules and speed-to-lead triggers with the Head of Pipeline Operations, and enforce them in Salesforce and our routing tools, with MQLs and PQLs on the same lifecycle and SLAs. Deliver the enrichment, signals, routing and alerts behind our account-based plays.
Own the syncs between our warehouse and our GTM tools. Build and maintain the reverse ETL syncs, APIs and webhooks that move data from Snowflake into Salesforce, marketing automation, routing and engagement tools. Build on the models the Data team publishes, and make sure every synced field has one owner and every sync is monitored. Support the rollout of our first marketing automation platform by building its Salesforce sync and warehouse feeds, along with the nurture enrollment rules and campaign tracking the Head of Pipeline Operations designs.
Put lead and account scores to work. Data Science owns our scoring models, including product-qualified lead scoring. Partner with them on marketing-qualified lead scoring by bringing in enrichment data, marketing engagement and Sales feedback, and help set the thresholds that trigger action. Make sure scores and their reasons reach Salesforce on time and that Sales understands them.
Close the feedback loop. Track the funnel from lead creation to closed-won. Find where leads stall, which sources and signals predict pipeline, and whether our qualification criteria still hold, then feed that back into routing, Marketing programs and Data Science's scoring work. Capture the campaign and touchpoint data behind attribution, which the Head of Pipeline Operations owns.
Help deliver the BDR prospecting toolset. It combines vendor solutions and internal applications. The Head of Pipeline Operations owns these systems, and BDR leadership decides the sequences and plays that run on them. Implement the vendor tools and integrate them with Salesforce and our data. Build the workflows and agents around them, such as signal-triggered alerts, prioritized outreach queues and pre-call research briefs. Resolve the system and data issues that slow reps down. Supply our GTM Platform team, which builds our rep-facing applications, with the data, signals and requirements they need. Talk to users, track adoption and retire what doesn't get used.
Partner across the business. Work with Marketing, Growth, BDR and Sales leadership, Data Science, Data Engineering, GTM Platform and Sales Systems to turn messy processes into durable systems, and use the scores and product usage signals Data Science and Growth publish to drive routing.
What success looks like
In your first 30 days:
Audit enrichment coverage, routing rules, warehouse-to-Salesforce syncs and lead SLAs, and document the gaps that cost us pipeline.
In your first 60 days:
Ship an enrichment waterfall with measurable gains in fill rate and accuracy.
Ship routing that sends every marketing and product lead to nurture or sales within an agreed SLA, with dashboards for speed to lead and conversion by route.
Take ownership of the syncs that write scores and lead fields to Salesforce, with monitoring and one owner per field.
Work with Data Science to bring enrichment and marketing engagement data into MQL scoring.
In your first 90 days:
Ship at least one prospecting workflow or agent with sustained weekly use by BDRs and AEs.
Show a measurable lift in lead-to-meeting and meeting-to-opportunity conversion for both MQLs and PQLs.
Qualifications
4+ years in GTM engineering, RevOps or Marketing Ops engineering, growth engineering, or data engineering in B2B SaaS, including 2+ years building enrichment, routing or integration systems.
Commercial instinct. You start from a revenue problem and work back to the data, logic or tool that fixes it.
Working SQL. You pull your own data from a warehouse (Snowflake or similar) and build on the models other teams publish.
AI-first builder. You've shipped integrations, automations or agents that real users depend on, using AI coding tools, and you can read, review and debug what you ship. Language depth matters less than GTM judgment.
Deep working knowledge of the Salesforce data model (leads, contacts, accounts, opportunities, campaigns, ownership), and experience automating and integrating with it.
Hands-on experience with enrichment and intent tools (Clay, ZoomInfo, Apollo, 6sense, Common Room or similar), routing and scheduling tools (Default, Chili Piper, LeanData) and reverse ETL (Hightouch, Census).
Fluency with funnel mechanics: lifecycle design, routing logic, score thresholds, SLAs, attribution data and conversion metrics.
Comfort with REST APIs, webhooks, OAuth, rate limits and error handling.
Operator mindset. You work directly with reps and marketers, ship fixes quickly, and don't need a PM to translate requests.
Nice to have
Hybrid PLG and sales-led motions: product-qualified leads, user-to-account mapping and sales-assist routing.
LLM-powered research, personalization or qualification agents, including evaluation and monitoring.
Working alongside a data science team on lead or account scoring.
dbt, or production work in Python or TypeScript.
Entity resolution and domain matching at scale.
A prior GTM Engineer role at a GTM-tooling or AI-native company.
Source: Perplexity on Ashby · View original posting (opens in new tab)
How this pay compares
Base floor $175,000, above 47% of the 4,892 Software Engineering roles in California on this site; the other 53% list the same floor or a higher one. The employer's range is $60,000 wide, 34% of the floor. Observed open for 7 days so far (since Nov 13, 2026).
Pay in context
Among 4,892 Software Engineering roles in California listed on this site, the median base floor is $176,400 and the middle half runs from $149,100 to $201,762. This role's floor ($175,000) is above 47% of them; 73 others list the same floor.
Base floors of 4,892 Software Engineering roles in California
Table
| Floor band | Share | Postings |
|---|---|---|
| $100K to $125K | 7.8% | 384 |
| $125K to $150K | 17.5% | 856 |
| $150K to $175K | 22.6% | 1,107 |
| $175K to $200K | 22.7% | 1,112 |
| $200K to $225K | 12.8% | 626 |
| $225K to $250K | 6.6% | 323 |
| $250K to $275K | 4.7% | 229 |
| $275K and up | 5.2% | 255 |
How this is calculated
- Statistic
- Base floor distribution of the cohort
- Formula
- count of cohort postings in each $25K band of published base floor / postings in the cohort
- Denominator
- 4,892 open postings with this job family in California
- Sample size
- 4892
- Hidden when
- the cohort has fewer than 30 postings
- Calculation version
- jobpage-analysis-v1
- Data as of
- 2026-11-20
- Employer set
- Open jobs on this site that publish a base salary of $100,000 or more
Only jobs on this site count, and each one publishes a base salary of $100,000 or more, so this compares six-figure jobs with each other, not with the whole market. Computed Nov 20, 2026.
State against nationwide
Median base floor in California vs nationwide
Table
| Value | postings | |
|---|---|---|
| Software Engineering, California | $176,400 | 4,892 |
| Software Engineering, all states | $160K | 13,247 |
| This job's base floor (marked) | $175K |
How this is calculated
- Statistic
- Median floor, state vs nationwide
- Formula
- median published base floor of each cohort
- Denominator
- open postings of this job family
- Sample size
- 4892 in California; 13247 nationwide
- Hidden when
- either cohort has fewer than 30 postings
- Calculation version
- jobpage-analysis-v1
- Data as of
- 2026-11-20
- Employer set
- Open jobs on this site that publish a base salary of $100,000 or more
How Perplexity pays
70 of Perplexity's 99 live roles on this site list a higher base floor and 25 list a lower one. Across them the median floor is $200,000; the middle half runs from $172,500 to $220,000.
Base floors of Perplexity's 99 live roles
Table
| Floor band | Share | Roles |
|---|---|---|
| $100K to $125K | 3.0% | 3 |
| $125K to $150K | 7.1% | 7 |
| $150K to $175K | 15.2% | 15 |
| $175K to $200K | 19.2% | 19 |
| $200K to $225K | 38.4% | 38 |
| $225K to $250K | 2.0% | 2 |
| $250K to $275K | 10.1% | 10 |
| $275K and up | 5.1% | 5 |
How this is calculated
- Statistic
- Employer base floor distribution
- Formula
- count of the employer's open roles in each $25K band of published base floor / its open roles
- Denominator
- 99 open public roles at this employer
- Sample size
- 99
- Hidden when
- this employer has fewer than 5 roles
- Calculation version
- jobpage-analysis-v1
- Data as of
- current
- Employer set
- Open jobs on this site that publish a base salary of $100,000 or more
Similar pay elsewhere
Other employers' Software Engineering roles in California with the nearest published base floor to $175,000, one per employer.
- Senior Software Engineer The Electric Plant · base floor $175,000
- Founding Engineer Clera · base floor $175,000
- Founding Product Engineer AgentMail · base floor $175,000
- Software Engineer - Full-Stack Cardless · base floor $175,000
- Software Engineer - C++ On-Vehicle Data Zoox · base floor $175,000
This listingGrowth GTM Engineer, Revenue Operations$175K – $235K
Member of Data Staff (Analytics Engineer)$175K – $330K
Member of Data Staff (Data Acceleration)$175K – $330K
Member of Data Staff (Data Scientist)$175K – $330K
Member of Technical Staff (GTM Engineer, Growth)$180K – $270K
Web Designer$180K – $210K
Member of Technical Staff (TPM, Compute)$170K – $265K
Chart as a table
| Role | Published base |
|---|---|
| Growth GTM Engineer, Revenue Operations (this listing) | $175K - $235K |
| Member of Data Staff (Analytics Engineer) | $175K - $330K |
| Member of Data Staff (Data Acceleration) | $175K - $330K |
| Member of Data Staff (Data Scientist) | $175K - $330K |
| Member of Technical Staff (GTM Engineer, Growth) | $180K - $270K |
| Web Designer | $180K - $210K |
| Member of Technical Staff (TPM, Compute) | $170K - $265K |
Observed changes
No changes to the pay or listing since we first observed this role on Nov 13, 2026 (7 days ago).
- First observed on the employer's board, already publishing a qualifying base salary
- Observed since
- Employer-stated posting date
- 2026-11-13
Where this pay comes from
Location as the employer wrote it: San Francisco • Austin • New York City
USD 175,000 – 235,000 · 1 YEAR · Salary
- Method
- Structured pay field published by the employer
- Checked
- Rule set
- us-base-v2
The employer's job board publishes this pay as a dedicated data field. We read the field directly; no interpretation was needed.
What we verified
- The pay figures come from the employer's own listing, quoted exactly above.
- The pay is an annual base salary in US dollars with a minimum of at least $100,000.
- The role was publicly listed on the employer's job board when last checked.
We do not verify what the employer will actually offer, whether the employer is still recruiting for the role, or anything beyond what the employer published. Full methodology.
