How to Structure a CRO Team: Roles, Hiring Order, and Salary Benchmarks
CRO teams are built wrong twice as often as they’re built right. The most common mistake: hiring a head of optimization before anyone is actually shipping tests. The second: hiring a designer before having an analyst who can decide what to design.
This is the hiring sequence we recommend, with salary benchmarks (US + EU), the structural decisions you’ll face, and when each hire is worth it. Calibrated from working with brands between $1M and $400M revenue.
The Hiring Order (and Why It Matters)
The order below is the reverse of how most teams hire. Most teams start with a head of optimization or a CRO designer because those roles sound senior and tangible. They produce nothing without the analyst layer underneath.
| Order | Role | Trigger revenue | Reports to (initially) |
|---|---|---|---|
| 1 | Optimization Analyst | $1M–3M | Marketing / Growth lead |
| 2 | Optimizer (Strategist) | $3M–8M | Head of growth |
| 3 | UX Researcher | $5M–15M | Head of optimization or product |
| 4 | CRO Designer | $8M–20M | Design lead |
| 5 | CRO Developer | $10M–25M | Engineering lead |
| 6 | Head of Optimization | $15M–40M | CEO / CMO |
Below: what each role actually does, when it’s needed, what to pay, and the failure mode of hiring out of order.
1. Optimization Analyst — Your First Hire
The single highest-ROI CRO hire most teams ever make. Owns analytics, instrumentation, test measurement, and dashboards. Without this role, the rest of the team is flying blind.
Responsibilities:
- Maintains GA4, GTM, event taxonomy, and a basic CRO data pipeline if applicable
- Designs the measurement plan for every test (primary metric, guardrails, sample size)
- Performs the funnel and segment analysis that feeds the backlog
- Runs the weekly reporting and the monthly executive dashboard
- Cleans the data the testing tool gets wrong
Skills: SQL, GA4, GTM, basic statistics, spreadsheet fluency. Bonus: dbt, Python, BigQuery.
Salary benchmarks (2026):
| Region | Junior (1–2 yrs) | Mid (3–5 yrs) | Senior (5+ yrs) |
|---|---|---|---|
| US (remote) | $65K–85K | $90K–120K | $125K–160K |
| US (NYC/SF) | $80K–110K | $115K–150K | $160K–200K |
| EU (Western) | €45K–60K | €60K–85K | €85K–115K |
| EU (Eastern) / LATAM | $35K–50K | $50K–75K | $75K–100K |
Hire when: You’re at $1M–3M revenue and running at least 1 test per month. Below that, contract an analyst through an agency or freelancer.
Failure mode of skipping this role: Tests run, but no one trusts the numbers. The team relitigates every result. The program loses credibility.
2. Optimizer (Strategist) — The Engine of Test Velocity
The role that owns the hypothesis backlog, runs the prioritization scoring, and operationally ships tests. This is the role you might externally call a “CRO manager” or “experimentation strategist.”
Responsibilities:
- Owns the test backlog and weekly experiment review
- Translates research insights into testable hypotheses
- Runs AXR scoring or ICE on every backlog item
- Briefs design and engineering on each test
- Writes test plans, post-test learnings, and quarterly reviews
- Holds the line on no-HiPPO-overrides
Skills: Behavioral psychology, statistics fluency, copywriting, basic UX, project management. Domain knowledge (ecommerce, SaaS, lead-gen) matters.
Salary benchmarks (2026):
| Region | Mid (3–5 yrs) | Senior (5–8 yrs) | Lead (8+ yrs) |
|---|---|---|---|
| US (remote) | $95K–130K | $140K–180K | $180K–230K |
| US (NYC/SF) | $120K–160K | $170K–220K | $220K–280K |
| EU (Western) | €65K–90K | €90K–120K | €120K–160K |
Hire when: Analyst is in place and shipping at least 2 tests/month. Optimizer is what gets you to 4+ tests/month.
Failure mode of skipping: Analyst becomes overloaded trying to be both measurement and strategy. Quality drops on both. Backlog stalls.
3. UX Researcher — The Insight Engine
Owns qualitative research: user interviews, usability sessions, surveys, support ticket synthesis. Feeds the optimizer with insight the analytics alone won’t surface.
Responsibilities:
- Conducts 4–8 customer interviews per month
- Runs unmoderated usability tests on prototypes and live pages
- Maintains a synthesized voice-of-customer database
- Translates qualitative findings into testable hypotheses
- Validates findings from session recordings and surveys
Skills: Interviewing technique, JTBD framework, synthesis, light statistics, tooling (Dovetail, Maze, UserTesting). See conversion research methods for the methodologies this role owns.
Salary benchmarks (2026):
| Region | Mid (3–5 yrs) | Senior (5–8 yrs) | Lead (8+ yrs) |
|---|---|---|---|
| US (remote) | $90K–125K | $130K–170K | $170K–215K |
| US (NYC/SF) | $115K–150K | $160K–200K | $200K–260K |
| EU (Western) | €60K–85K | €85K–115K | €115K–150K |
Hire when: Backlog quality has plateaued. The optimizer is generating hypotheses from analytics alone and they’re getting more incremental. Typically $5M–15M revenue.
Failure mode of skipping: Tests keep winning but lift sizes shrink. The team is testing surface-level patterns without understanding the underlying customer. Wins stop compounding.
4. CRO Designer — The Velocity Multiplier
A designer embedded in the CRO function, not borrowed from product design. Designs variants that respect the test hypothesis (not their own aesthetic preference).
Responsibilities:
- Designs every test variant
- Maintains a CRO component library (so each test isn’t designed from scratch)
- Pairs with the optimizer in test ideation
- Builds responsive variants (mobile parity is where most tests fail)
Skills: Figma fluency, design systems thinking, copywriting fluency, conversion psychology, willingness to test “ugly” hypotheses without ego.
Salary benchmarks (2026):
| Region | Mid (3–5 yrs) | Senior (5–8 yrs) | Lead (8+ yrs) |
|---|---|---|---|
| US (remote) | $95K–130K | $135K–175K | $175K–220K |
| US (NYC/SF) | $120K–160K | $170K–215K | $215K–270K |
| EU (Western) | €60K–85K | €85K–115K | €115K–150K |
Hire when: Design is the bottleneck. You have 10+ validated test ideas waiting on design resources. Usually $8M–20M revenue.
Failure mode of skipping: Tests get stuck in the design queue. Product designers (rightly) prioritize product features. CRO velocity caps at 3–4 tests/month no matter how good the analyst and optimizer are.
5. CRO Developer — The Other Velocity Multiplier
A frontend engineer dedicated to CRO test implementation. The tooling does a lot, but ambitious tests (multi-page flows, personalization, server-side variants) require code.
Responsibilities:
- Implements test variants the testing tool’s WYSIWYG can’t handle
- Builds custom personalization
- Maintains the test instrumentation layer
- Pairs with the analyst on event tracking
- Owns the technical guardrails (flicker prevention, performance impact)
Skills: JavaScript/TypeScript, the codebase of the testing platform, familiarity with the company’s stack (Shopify Liquid, Next.js, etc).
Salary benchmarks (2026):
| Region | Mid (3–5 yrs) | Senior (5–8 yrs) | Lead (8+ yrs) |
|---|---|---|---|
| US (remote) | $110K–145K | $150K–195K | $200K–250K |
| US (NYC/SF) | $140K–180K | $190K–240K | $250K–320K |
| EU (Western) | €70K–95K | €95K–130K | €130K–170K |
Hire when: Engineering bottleneck mirrors the design bottleneck. Usually $10M–25M revenue. Until then, retainer a contractor.
Failure mode of skipping: Ambitious tests don’t happen. The backlog gets capped at what the testing tool’s UI supports — meaning incremental tests dominate and the program ceiling drops.
6. Head of Optimization — The Last Hire, Not the First
Owns strategy, the executive relationship, the cross-functional governance, and the long-arc roadmap. Almost everyone hires this role too early.
Responsibilities:
- Defines the annual experimentation strategy
- Owns the executive dashboard and the quarterly business review
- Negotiates testing rights with product, marketing, design, engineering
- Manages the CRO team (analyst + optimizer + researcher + designer + dev)
- Reports to CEO, CMO, or Chief Product Officer
Skills: Senior strategy, executive communication, organizational design, deep CRO domain expertise, P&L thinking.
Salary benchmarks (2026):
| Region | Director | VP / Head of |
|---|---|---|
| US (remote) | $180K–250K + equity | $230K–330K + equity |
| US (NYC/SF) | $230K–310K + equity | $300K–430K + equity |
| EU (Western) | €130K–180K | €170K–230K |
Hire when: You have at least 3 CRO ICs already (analyst + optimizer + one of researcher/designer/dev). At $15M+ revenue with a stage 3+ maturity per the CRO maturity model.
Failure mode of hiring first: Senior strategist with no team to execute, no data infrastructure to work with, and no executive buy-in earned through results. Becomes a frustrated change agent and usually leaves within 12 months.
T-Shaped vs I-Shaped People
The single most useful hiring heuristic for CRO is T-shaped — deep in one discipline (analytics, UX, copy, design, dev), broad enough to operate across the whole testing cycle. I-shaped specialists (deep in one thing, useless outside it) create handoff overhead that kills small teams.
For your first 3 hires, hire only T-shaped. After 4+ people, you can afford one I-shaped specialist (typically the researcher or the developer).
The interview signal for T-shaped: ask the candidate to walk through a recent test end-to-end. A T-shaped analyst will talk about the hypothesis, the design choices, and the dev implementation alongside the measurement. An I-shaped analyst will only talk about the SQL.
Centralized vs Embedded: The Org Structure Decision
Once you have 3+ people, you face a structural choice.
Centralized CRO team (one team owning all experimentation across the company):
- Pros: consistent methodology, shared infrastructure, easy governance, faster culture-building
- Cons: bottleneck on the central team, less domain context, perceived as outside service
- Best fit: $5M–50M revenue, single product, web-heavy business
Embedded CRO (analysts and optimizers sit inside product/marketing teams):
- Pros: deep domain context, faster decision-making, scales beyond what one team can ship
- Cons: methodology drift, duplicated infrastructure, harder governance
- Best fit: $50M+ revenue, multiple product lines, mature culture
Hybrid (most common at scale): Central platform team owns tooling, infrastructure, methodology, and training. Embedded analysts/optimizers sit inside product teams and run the actual tests. Booking, Amazon, and Airbnb all run this model.
For most teams reading this, centralized is the right answer for the next 18–24 months. Switch to embedded only when the central team has become the bottleneck.
In-House vs Agency: When to Make the Switch
This is the most common question we field. The right answer is staged, not binary.
Pure agency / consultant (revenue < $3M): You don’t have enough testing surface to justify a dedicated hire. Retainer a CRO agency or freelancer for 6–12 month engagements.
Hybrid (revenue $3M–15M): Hire your first dedicated analyst. Keep an agency or consultant for strategy and overflow execution. The agency teaches the analyst the methodology you’ll build on. See CRO agency vs in-house for the cost math.
Mostly in-house with specialist external (revenue $15M+): Build the 4–6 person internal team. Use external specialists for one-off work (research sprints, technical CRO audits, hiring a senior consultant for strategy).
The mistake to avoid: dropping the agency the moment the first internal hire starts. The first analyst needs 6–12 months to ramp. Cutting external support during that window kills program velocity at the exact moment culture is forming.
A Realistic Org Chart by Revenue Stage
What a healthy CRO function looks like at each scale.
$1M–3M: 1 part-time analyst (often a marketer wearing the CRO hat) + agency / freelancer for strategy and execution. Spend $4K–10K/mo.
$3M–8M: 1 full-time analyst + 1 contracted optimizer (or agency). Spend $12K–25K/mo.
$8M–15M: Analyst + optimizer + UX researcher (full-time) + design and dev borrowed from product. Spend $30K–55K/mo including tooling.
$15M–40M: Full team: head of optimization + analyst + optimizer + researcher + CRO designer + shared CRO developer. Spend $70K–130K/mo.
$40M+: Multiple analysts and optimizers, embedded into product teams. Central platform team owns infrastructure. Spend $200K+/mo.
Frequently Asked Questions
Who should I hire first for CRO?
An optimization analyst — someone who owns measurement, instrumentation, and test analysis. This is the highest-ROI first hire because every other CRO role depends on trustworthy data. Hire a head of optimization or designer first and they’ll be blocked on measurement quality.
When should I hire a head of optimization?
After you already have 3+ CRO ICs in place — typically at $15M+ revenue with Stage 3+ maturity. Hiring a head of optimization before there’s a team to lead and infrastructure to build on usually fails within 12 months.
What does a CRO analyst earn in 2026?
US remote: $65K–160K base depending on experience. US major metros: $80K–200K. Western Europe: €45K–115K. Mid-level (3–5 years) typically lands around $90K–120K in the US remote market in 2026.
Should CRO be centralized or embedded in product teams?
Centralized for most teams under $50M revenue — methodology consistency and culture-building outweigh the bottleneck cost. Embedded once you exceed $50M and have multiple product lines. Hybrid (central platform + embedded analysts) is what Booking, Amazon, and Airbnb run at scale.
