Gab Menachem started as CPO on April 14. The Head of Product Design posting went live July 7. Eighty-four days between arrival and requisition.
A CPO who posts a design leadership role in his first 30 days is filling a seat. A CPO who waits 84 days is building one. Everything about how you engage with this company depends on which one it is.
He built the seat. The window is opening to peak. Move this week.
The events, in order
September 2, 2025. OpenAI acquires Statsig for its experimentation infrastructure. The Statsig team stays at OpenAI. The platform and its customer base are suddenly unattached.
April 14, 2026. Amplitude announces Gab Menachem as CPO. He oversees product management, design, and growth, reporting to CEO Spenser Skates. Note the structure: design sits alongside PM and growth under one executive. The Head of Product Design will have a seat at the product leadership table but will not operate as an independent function. Influence here comes from craft authority and output, not org-chart independence. Gab's background: founded Loom Systems (AIOps, acquired by ServiceNow 2020), then six years scaling ServiceNow's IT Operations Management line past $1B ARR. His public framing at Amplitude: making data actionable at the point where decisions get made.
May 5, 2026. Three weeks after Gab's appointment, Amplitude takes on the Statsig platform and customers through what Amplitude calls a "strategic partnership." (Their own job postings elsewhere use "acquisition" language; the public announcement does not. Cleanest read: Amplitude absorbed the Statsig brand, platform, and customers after OpenAI's $1.1B acquisition brought the original team in-house.) The original Statsig team stays at OpenAI. Amplitude's design team just inherited a second product surface with its own user base, its own design language, its own experimentation paradigm. Nobody at Amplitude designed it.
June 10, 2026. Five weeks later, Amplitude launches Wave, a "proactive product agent" that surfaces opportunities, ships improvements, and helps teams build self-improving products. The docs describe the core workflow as "Opportunities": product signals turned into prioritized, evidence-backed work that humans or agents can approve and ship. A third product surface. And the one with the hardest design problem: the trust handoff between what the system found and what a human decides to do about it.
July 7, 2026. The Head of Product Design posting appears on Greenhouse. Leads a 15-person team. Scope: Core Amplitude, Statsig, and Wave. The language is pointed: "created (not inherited) structure inside of a messy, high-growth organization." The anti-language is equally pointed:
"Not an executive role that manages up and delegates down," "not a pure IC role," "not design ops," "not the approval committee."
Five events. Three changed the trajectory.
The pattern
The Statsig partnership and the Wave launch are the trajectory-changing events. Gab's appointment set the clock. The posting confirmed what the first three events already predicted.
Eighty-four days tells you this: the posting could not have been written before both Statsig and Wave existed, because it explicitly names both. The vocabulary mirrors Wave's product vocabulary. "Created (not inherited)" is a fingerprint: Gab wants someone who builds from ambiguity, not someone who optimizes an existing org chart. He used his first three months to expand the product surface until the design mandate was large enough and specific enough to define. Then he posted.
I found no public evidence that Gab previously hired or replaced a Head of Design, VP Design, or equivalent at Loom Systems or ServiceNow. This may be his first design leadership hire at this level. Not a warning sign. A signal about what he will evaluate. He likely has strong instincts about what he needs but no established playbook for how to assess it. The candidate who names the design problem in his language, not in design-community language, has an asymmetric advantage.
The departure signal
The posting fills a real gap, not a vacuum.
Kim Lenox was profiled as VP of Design in December 2024, leading product design across Amplitude's suite. Jenny Chang was identified as Head of Design in February 2024 after nearly seven years at the company.
Kim Lenox's May 21, 2026 LinkedIn article identifies her as having "founded Lenox Foundry for founders and executives at an inflection point." You do not found a consulting practice while serving as VP Design. The Org lists her as VP and Head of Design but marks the entry "Unverified" and notes she is "not in the org chart." Cal Poly's advisory board still lists her with Amplitude, but institutional pages lag by months.
I cannot confirm Kim's departure date from public sources. That gap is real and I am naming it rather than inferring through it. The convergence of signals points one direction: Kim departed sometime in early-to-mid 2026. Gab inherited a 15-person team without its senior leader. He spent 84 days expanding the product surface, then posted once the mandate was fully formed.
Jenny Chang's current status at Amplitude is also unconfirmed from public sources. If she remains after seven-plus years, she is a potential internal stakeholder in this hire, likely the person who kept the team running through the leadership gap. If she departed, the design leadership vacuum is deeper than a single departure, and the "created (not inherited) structure" language takes on sharper urgency.
The posting's title is Head of Product Design, not VP of Design. A different title for a different scope under a different CPO. This is a new mandate regardless of who left.
The cluster signal (absent)
Amplitude's Greenhouse board shows 44 open roles. One has "design" in the title. No design recruiter. No design engineer. No senior IC design postings.
Adjacent roles worth noting: Principal Product Marketing Manager, Agents (posted April 27), Technical Support Engineer for Statsig (June 8), multiple Customer Data Scientists for Statsig (June), Senior AI Engineer (June 26). Statsig integration and AI engineering hiring is active. Design hiring is a single leadership posting, alone.
Normally a missing cluster is a warning. Here the posting's own language resolves it. "Created (not inherited) structure" means Gab is hiring the leader first and letting them build. The 15-person team exists. The leader does not. He wants someone who will shape team composition, not slot into predetermined headcount.
The prediction
The window is opening to peak.
The posting is 12 days old. Greenhouse first_published and updated_at timestamps are both July 7, consistent with a genuinely new posting that has not been edited. A CPO who took 84 days to define the mandate will be equally deliberate in evaluating candidates. He is not closing this slate in two weeks.
Design leadership searches at this level typically run 8–12 weeks from posting to offer. If Gab's deliberation pattern holds, he is on the longer end. First-round interviews likely fall in weeks 2–5 from posting. Today is the front edge of week 2.
The qualified pool is structurally narrow. Most design leaders have led one product line. This role requires holding three simultaneously: Core Amplitude's analytics maturity, Statsig's experimentation infrastructure, and Wave's agent-human trust problem. The candidate who can credibly speak to all three, especially the Wave trust handoff, has a structural advantage that portfolio polish alone cannot replicate.
If Gab circulated the role through his ServiceNow network or executive recruiters before the Greenhouse posting went live, the slate could be further along than 12 days suggests. No public evidence of this. A retained firm would typically suppress or delay the public posting. The fact that it appeared on Greenhouse without a recruiter cluster suggests this is running through Amplitude's internal talent function. Act as if the window is open. Move quickly anyway.
Contact recommendation
Who: Gab Menachem. He shaped this posting. He is the buyer.
Channel: Apply through Greenhouse as procedural baseline. Direct outreach to Gab is the move that differentiates. The role is fresh enough and specific enough that a well-positioned message will stand out against the application queue.
Why this week: Every week you wait, the slate gets deeper and Gab's preferences get more anchored by the candidates he has already seen. Anchoring bias in hiring panels is well-documented. The first strong candidate sets the frame every subsequent candidate is measured against. You want to be that frame, not measured against it.
The implication
One thing changes because of this reconstruction. This is a mandate-authored role, not a backfill. Gab has a thesis. He spent 84 days building it. Your job in outreach and in the room is to demonstrate you can execute his thesis, not to sell your general capabilities.
The posting tells you what the thesis is: three product surfaces, one coherent design vision, agent-human trust as the hardest unsolved problem. Speak to that. Everything else is secondary.
Positioning angle, outreach message, and warm-path assessment belong in the Opportunity Brief.
- Statsig's Phase 1 integration: A June 17 Statsig post describes a roughly six-week "Phase 0" focused on learning and maintenance before platform expansion begins, which means the design integration work is just starting now.
- Gab's "intelligence layer" framing: Amplitude's CPO welcome post frames his prior work as making data actionable at the point where decisions get made, mirroring the exact trust-handoff language in the posting and in your Trust essay.
- Wave's "Opportunities" workflow: Amplitude's docs describe Wave's core surface as product signals turned into prioritized, evidence-backed work that humans or agents approve and ship, which is the Output Review and Decision Gate handoffs made literal.
- Kim Lenox's Lenox Foundry signal: Her May 2026 LinkedIn article identifies her as having founded a consultancy for founders and executives at an inflection point, which is worth monitoring because it may clarify the departure timeline and whether Jenny Chang is still in seat.