Issue #2 · May 16, 2026

Product Analytics Is the Q2 Hire. Here's What the Brief Now Requires.

Career Snapshot

The companies that named AI revenue in Q1 now have a Q2 problem: proving it. That proof is a hiring event.

Product Analytics Manager is the seat absorbing the pressure. Not funnel analytics. Not retention modeling. The brief: instrument the AI feature, isolate the lift from the baseline, and confirm whether the revenue claim holds. The PM cannot design that test. That’s the gap. That’s the hire.

Pinterest opened a Senior Product Analytics Manager role for the Performance+ business — the AI-priced inventory that cleared roughly 30% of lower-funnel revenue in Q1. The brief requires familiarity with auction-model attribution and AI feature lift measurement. One job. Two distinct frameworks.

LinkedIn has open analytics engineering and data product roles in the advertising division. B2B attribution methodology is a stated screen: match-rate, attribution windows, first-party signal versus UTM.

Hot this week:

  • Product Analytics Manager. Senior IC comp at the companies running this search: $185K–$240K base. The companies that named AI revenue in Q1 are hiring the person who can instrument it.
  • Staff / Principal Analytics Engineer. The title is splitting into two distinct hiring families. Details in Skill Market Shifts.
  • Director / Head of Analytics. Fewer reqs, longer searches. Internal candidates are winning. External closes are leading with decisions framed, not infrastructure built.

Reading the tape: the Q1 AI-revenue claims are on trial in Q2. The analytics talent needed to run the trial is the hire.

Skill Market Shifts

1. Product Analytics Manager JDs now list AI feature instrumentation as a required competency — not a preferred one.

The shift: six months ago, senior product analytics JDs noted “AI/ML experience a plus.” Today, the companies running these searches screen for AI feature measurement on the front pass — specifically, the ability to design an incrementality test for a non-deterministic feature.

The evidence: Pinterest, Duolingo, and several growth-stage SaaS companies have made AI attribution methodology a stated screen in 2026 senior product analytics JDs. The top of the senior IC band now matches early people-manager comp at the same companies. That’s a scarcity signal.

The career translation: “designed and ran A/B tests” without naming AI features doesn’t screen you out — but it doesn’t screen you in. One documented AI feature instrumentation exercise closes the gap: hypothesis, baseline, instrument, result.

2. The Staff Analytics Engineer job is now two jobs.

The shift: one “Staff AE” posting now surfaces as two separate briefs — semantic layer engineering (building and governing the metric definitions layer) and data product ownership (governing access, contracts, and SLAs downstream). Signal’s May 18 issue noted the “data product owner” title was “sometimes. mostly real.” The structural split is now in the JDs, not just the titles.

The evidence: Airbnb, Stripe, and LinkedIn have separated these into distinct reqs in the past two quarters. The semantic layer brief routes to dbt Semantic Layer or MetricFlow fluency. The data product brief routes to contract and governance fluency. Different interviews. Different portfolios.

The career translation: pick a lane. A resume claiming both suggests depth in neither. Name the half you’re applying for.

3. RevOps Director postings at social ad platforms are adding an AI-forecast audit screen.

The shift: in 2024, RevOps Director JDs at ad platforms asked for Salesforce fluency, pipeline methodology, and forecasting experience. Today, the same JDs add a screen: describe your process for reviewing — and overriding — an AI-generated forecast. The role is shifting from building the forecast to auditing the one the system produced.

The evidence: LinkedIn’s Revenue Operations and Sales Strategy leadership reqs (advertising division) and Pinterest’s Sales Operations briefs reference AI-enabled forecasting workflows and expect a stated candidate position on human-in-the-loop judgment.

The career translation: the interview question is no longer “walk me through your forecast methodology.” It’s “your AI called Q2 pipeline at $42M. The field says $35M. What’s your process?” Candidates answering with a Clari feature walkthrough lose to candidates answering with a specific override story — signal, override, outcome.

Next Action Plan

Portfolio. Target: Product Analytics Manager. Build one AI feature effectiveness spec — one page. Pick a real or hypothetical AI feature. Define the hypothesis (what behavior it’s supposed to change), the baseline metric, the instrument (why incrementality over correlation), and the failure condition (what result kills the feature). The companies hiring for this seat are evaluating whether you can design the test, not whether you’ve run one.

Networking. One outreach message to a product analytics leader at a company that named AI revenue in Q1 — Pinterest, Duolingo, Salesforce, or a growth-stage SaaS you already track. Three sentences. Specific question: “How are you isolating AI feature lift when the control condition is noisy — incrementality testing, or correlation with stated limits?” That signals you know where the hard part is.

7-day micro-skill. Write one AI feature instrumentation spec. Pick any AI product feature you use. Write the measurement plan: metric, baseline, control condition, minimum detectable effect, and the one confound you’d flag before running the test. One page. By Friday you have a portfolio artifact.


Sources

Crafting runs weekly. The job is to be useful, not to sell. If a line in here is close to a move you're working on, the email reaches a person.

Hiring rather than hunting? Signal is the letter for your side of the desk.

Get next week's issue Email me

← All Crafting issues · Drafted with Claude · Edited by Paul Brown