See how candidates think and approach the work this role demands, before the phone screen. We'll build a video challenge from this posting, and you can edit or share it before it goes live.
Perplexity is building an in-product system that converts self-serve Computer usage into account-level sales intent and enterprise pipeline, signaling that a consumer-adopted agentic AI product is being deliberately wired into a bottoms-up enterprise sales motion.
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 the Growth team owns the loops that turn that adoption into lasting usage and revenue.
We're hiring a Growth GTM Engineer to build the systems that turn product usage into revenue and turn self-serve usage into enterprise pipeline. You'll turn first-party Computer and Enterprise usage into account-level signals. You'll ship the in-product paths that capture sales intent, and build and validate those signals with data science. Alongside product engineers, you ship production code, instrument the product and run experiments. You'll partner closely with Revenue Operations, who own Salesforce, CPQ, routing and sales reporting.
Tech Stack: TypeScript | Next.js | React | Python | PostgreSQL | Snowflake | Eppo | AWS
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.
Build account-level PLG signals: map users and workspaces to accounts, and define the activation, expansion and intent signals that predict an enterprise deal. Publish them as trusted models that sales use for scoring and routing.
Own the in-product paths from self-serve to sales, like contact-sales entry points, high-intent upsells and meeting booking, across web and app. Decide who sees them, when and with what context, and measure them end to end, from surface to booked meeting to pipeline.
Lead experiments end to end on sales-assist surfaces and targeting, from hypothesis and instrumentation through analysis and rollout. Partner with Data Science to measure meetings and qualified opportunities, not just clicks.
Build the internal tools and automation Growth and GTM teams run on
Partner closely with Sales, Sales Systems, Data Science, Marketing and Product to turn product signals into pipeline. Be upstream partner to sales systems that own Salesforce, CPQ and routing
2+ years as a growth, GTM, data or full-stack engineer, shipping production code (TypeScript/React, Python).
Strong SQL and comfort building data models in a warehouse (Snowflake, dbt-style).
Experience instrumenting product events and running A/B experiments end to end.
Commercial instinct: you start from a revenue problem ("trial-to-enterprise conversion won't move") and work back to the signal or surface that fixes it.
Comfort with REST APIs, webhooks and integrating third-party GTM tools.
Operator mindset: you talk to customers directly, ship fixes, and don't need a PM to translate requests.
Experience in a PLG-to-enterprise motion: product-qualified leads, scoring users into accounts, sales-assist flows.
Experience as a GTM or growth engineer at a B2B SaaS or GTM-tooling company.
Entity resolution, dedup or domain enrichment.
Familiarity with Salesforce, Default, Chili Piper, Intercom, Clay, Hightouch/Polytomic or similar (as a consumer and integrator, not an admin).
Experience building LLM-powered internal tools or agents.
perplexity:3b523d3a-23bd-4887-8e3c-239d14d66b06See how we measure for definitions, or our corrections log for known issues. Found something wrong? Flag a correction.
perplexityThis posting hasn't been probed by our closure verifier yet. Stream C runs on a rolling schedule against postings approaching the close-decision threshold.