How do I hire an A/B test developer?

Decide whether you need build capacity only or research and strategy as well, write a brief with the page, the change, the audience and the goal, shortlist two or three developers, ask each how they handle single-page apps, flicker and a split that does not match your analytics, and start with one paid test before agreeing to volume.

Where can I find a freelance A/B test developer?

On their own websites, on marketplaces such as Upwork, Arc and Malt, and through agencies that resell build capacity. A shortlist of twelve, with platforms, proof and published rates, is at arafatcro.com/guides/best-freelance-ab-test-developers-2026.

What should an A/B test brief include?

The URL and pages in scope, the testing platform, the hypothesis, a design or description of each variation, the audience and targeting, the goals and the events that measure them, the devices and browsers to QA on, and the date you need it live.

What are the red flags when hiring an A/B test developer?

Only ever using the visual editor, hiding the whole page to stop flicker, no named person who will write the code, no plan for removing the test afterwards, and leaving the tracking for you to sort out.

Do I need a developer if my testing tool has a visual editor?

For copy and colour changes, often not. For anything that adds behaviour, runs on a React or Next.js site, changes a form or a basket, or has to pass your engineering team's review, yes. The visual editor writes code too; it just writes it for the simple case.

How to hire a freelance A/B test developer

The hiring process for an A/B test developer in four steps, choose the model, write the brief, ask the questions, run one paid test, beside the red flags to watch for.

Disclosure: I am an A/B test developer, and I am one of the twelve on the shortlist below. The advice holds whoever you hire.

The short answer

Start by working out what you are buying. If you already have test ideas and a testing platform, you need build capacity, and a freelance developer is usually the quickest and cheapest way to get it. If you need someone to decide what to test, talk to a CRO consultant or agency first. Then write a brief precise enough to quote against: the page, the change, the audience, the goal and the platform. Ask every candidate the same six questions (they are further down). The answers show quickly who writes variation code and who drags things around in a visual editor. Finally, pay for one test before you agree to volume, and judge the code, the QA and the handover. Rates vary a lot, from fixed prices per test to day rates, so compare what each quote includes as well as the figure.

Freelancer, small shop, agency or marketplace?

Option	What you get	Watch for	Best when
Solo freelancer	One named developer who writes and QAs the code	Capacity is one person; check holidays and hours overlap	You have a backlog of ideas and want consistent builds
Small build shop	A team that builds to a queue, often per test or on a retainer	Who actually writes your test; handovers between people	You need more volume than one person can carry
CRO agency	Research, design, build and analysis in one retainer	You pay for strategy even if you only need builds	You need someone to decide what to test
Marketplace (Upwork, Arc, Malt)	A large pool and the platform's payment protection	Profiles describe skills, not shipped variation code	You can vet candidates yourself with the questions below

What it costs

Published rates for this work vary by model. On the shortlist, the published figures include €150 to €500 per test on fixed pricing, €80 an hour for a solo builder, €700 a day on the French market, and a team starting at $25 an hour. Most developers do not publish a rate and quote per brief.

Whatever the number, check what is in it. A complete build includes the variation code, QA across the devices and browsers you care about, the tracking for each goal, and a clean way to remove the test when it ends. A low quote that leaves the tracking or the QA to you is not a lower price.

Write a brief a developer can quote

A developer can only price what they can see. Include:

The URL and the pages in scope, including any single-page app routes the test has to survive.
The testing platform you already use, and who has access to it.
The hypothesis, in one sentence.
Each variation, as a design or a precise description.
The audience and targeting: devices, traffic sources, logged in or not.
The goals, and the events that measure them.
Where to QA: browsers, devices and any staging environment.
The date you need it live.

Six questions to ask before you hire

"Show me a test you shipped on a single-page app. How did it survive a route change?" A good answer describes re-applying the variation when the route changes and removing it when the visitor leaves. A vague answer about "the platform handles it" is a warning.
"How do you stop flicker?" Listen for "hide the element I change, not the whole page", and for a Core Web Vitals number they watch. The flicker guide explains why.
"The platform says 50:50 and GA4 says 60:40. What do you check?" Someone who has debugged it will talk about event timing, lost beacons on navigation and missing page views. The sample ratio mismatch write-up lists the usual causes.
"Who writes the code?" You should know which developer will build your test, whatever the rate.
"How is the test removed when it ends?" There should be a plan that leaves the page exactly as it was.
"What does QA cover?" Expect named browsers and devices, the targeting, the tracking and keyboard access for anything interactive.

Red flags

They have only ever used the visual editor.
Their anti-flicker approach hides the whole page.
No named person will write the code.
There is no plan for removing the test.
Tracking is left for you to sort out.
They will not show any code they have written, even with client details removed.

Start with one paid test

Before you agree to a retainer, pay for one real test on your own site. Pick something with a little complexity, a form, a basket interaction or a component on a single-page app, so you see how they handle the hard part. Then read the code, the QA notes, the tracking and the handover. Looking right in the preview is the easy part. For what it's worth, I would rather be judged on one real build than on a sales call, and I would expect anyone worth hiring to feel the same.

Twelve to shortlist

These twelve people and shops build A/B tests for clients. Each one has a full entry, with platforms, proof, published rates where they exist and a caveat, in Freelance A/B test developers worth hiring in 2026. Listed alphabetically within each group; I am one of them.

Name	Model	Platforms named on their page (selection)
abtestdev.com	Solo	VWO, AB Tasty, Adobe Target
Adrien Millet	Solo	AB Tasty, Kameleoon, Optimizely
Arafat Islam (arafatcro.com)	Solo	Optimizely, VWO, Convert, Adobe Target
Chad D. (Arc.dev)	Solo	VWO, Convert, Shopify
Ellen Goettsch (A/B Testing Studio)	Solo	VWO, Convert, Optimizely
Richard Forbes-Simpson	Solo	Intelligems, Shopify
ABTestDeveloper.com	Small shop	Optimizely, VWO, Convert, Adobe Target
DesignerAshish.org	Small shop	Optimizely, Convert, VWO, Adobe Target
Mondaysys	Small shop	Optimizely, Convert, AB Tasty, VWO
Optyv	Small shop	Optimizely, VWO, Convert, AB Tasty
BrillMark	Team	VWO, Optimizely, AB Tasty, Convert
EchoLogyx	Team	VWO, Convert, Optimizely, AB Tasty

Optyv and Mondaysys publish the same addresses and are likely the same operator; the full list explains.

Before you sign

Agree in writing that the variation code is yours once it is paid for. Give the developer their own login to the testing platform rather than a shared one, and remove it when the work ends. If a test touches unreleased products or prices, sign an NDA first. And ask for the code, the QA notes and the tracking plan for every test, so you can move to someone else at any point without starting over.

Last updated 27 September 2026. Corrections to [email protected].

← Back to all work