The developer your CRO agency can hand tests to.
I build A/B tests and set up their goals and tracking for CRO agencies. You send the approved design. I hand back a flicker-free variant, checked across devices with its goals firing, ready for your QA team.
- Flicker-free builds
- Goals & metrics checked
- SPA-safe code

- A/B and multivariate tests built
- 300+
- as a development partner to CRO agencies
- 5+ yrs
- agency teams, eCommerce and B2B SaaS
- US + UK
- set code review and JS standards
- Team lead
Builds in your stack
- Optimizely
- VWO
- Adobe Target
- AB Tasty
- Convert
- Kameleoon
- Monetate
- GA4
- Google Tag Manager
- Segment
- React
- Vue
- Angular
- WordPress
- Drupal
One developer for every step between “approved” and “live.”
Pick one service or bring me in for the whole pipeline.
From copy swaps to full page rebuilds.
I build variations in your testing platform with JavaScript, React and SCSS, straight from the Figma. Code is written to load without flicker and to survive single-page app route changes.
- Flicker-free rendering
- SPA-safe, route-aware scripts
- Pixel-matched to the design
- Reusable helpers across tests
Your strategists shouldn’t be waiting on dev.
- You say“Approved tests sit in the backlog for weeks.”I doAdd build capacity when you need it, so the roadmap moves at the pace you planned.
- You say“The variant flickers, or breaks on the client’s app.”I doWrite route-aware scripts that run safely in React, Vue and Angular apps without hurting Core Web Vitals.
- You say“We ran it for a month and the goal never fired.”I doMap and check every event before launch, so each test ends with data you can call.
How a test moves through my pipeline.
I work in your Jira, your Slack and your client’s platform. To your client, I’m simply your agency’s developer.
Feasibility
I review the brief and the Figma designs against the live page and flag blockers before any code is written.
- Feasibility notes
- Blockers flagged early
- Hours estimate
Every variation starts from the same tested skeleton.
So it drops onto a live page without clashing with the host site, the platform, or other tests running on the same page.
((w) => {
"use strict";
const tag = 'cv-x-y';
const window = typeof unsafeWindow !== "undefined"
? unsafeWindow : w;
// everything for this experiment lives in here
utils.init();
})(window);Every variation is wrapped in its own function scope and gets one unique tag that namespaces everything it touches.
- Nothing leaks into the host page or other running tests
- One tag scopes the CSS, injected elements, storage keys and logs
- The same file runs on the platform and in Tampermonkey for local checks
Hi, I’m Abu Zaher. I’ve spent five years building other agencies’ tests.
At Brillmark I built more than 300 A/B and multivariate tests for eCommerce and B2B SaaS brands, then led the front-end team, setting up our code review process, JavaScript standards and documentation. Today I build tests and site features for This is Gain in London.
- EducationM.S. Computer ScienceWestern Illinois University, in progress
- How I codeProduction‑grade test codeReviewed, documented, easy to hand over
EXPERIENCE
- This is Gain · London (remote)
Front-End Developer (CRO)
2024 — nowA/B variations and new features in JavaScript, React and SCSS from Figma. SPA-safe scripts, flicker and Core Web Vitals guardrails, cross-device checks and code review.
- Brillmark · California (remote)
Senior CRO Developer & Team Lead
2023 — 2024Led and mentored the front-end team. Helped client engineers turn winning experiments into permanent React, Vue and Angular components.
- Brillmark
Front-End Developer (CRO)
2021 — 2023Built 300+ A/B and multivariate tests. Event tracking and data layer integrations. Scrum sprints with PMs, QA and client developers.
Questions agencies ask first.
Straight answers on turnaround, scope and how I work with your team.
Ask me something else- How fast can you build an A/B test?
- Most standard builds are ready within 48 hours of an approved brief. Simple copy and styling changes often go out the same day, while complex multi-page or funnel tests take three to five days. If something is urgent, tell me up front and I’ll plan around it.
- Do you do the QA as well?
- I run an initial check across the main browsers and devices and confirm every goal and metric is firing before handover. Full QA stays with your QA team, and I fix whatever they find until the test is ready to launch.
- What happens if a test breaks after launch?
- I fix it. In practice it rarely comes to that: before launch, your QA team checks the experiment on the live site using a QA cookie, and a post-launch QA pass follows once it goes live. After that, a test should only break if the client updates their site, and if they do, I’ll update the test to match.
- Do you also design the tests or analyse results?
- No, and that’s deliberate. I focus entirely on development. Your team owns the research, hypotheses, designs and analysis; I turn them into clean, reliable tests with the tracking your analysts need. That keeps the line between strategy and build clear, and the client relationship firmly yours.
- Do I need to give you access to the client’s codebase?
- No. I work inside your testing platform, which runs on top of the site. A platform login with editor access and a preview link are all I need. No repository access, no deployment permissions, and no changes to production code.
- Can you work white-label?
- Yes. I work as part of your agency’s team, under your name and inside your tools. If your client sees me in a call, a Slack channel or a ticket, they see me as your developer, not an outside contractor.
- Which platforms do you work in?
- Optimizely, VWO, Adobe Target, AB Tasty, Convert, Kameleoon and Monetate for testing, with GA4, Google Tag Manager and Segment for tracking. If a platform accepts custom JavaScript and CSS, I can build in it.
- Can I see how you write code?
- Yes. My GitHub has 200+ real experiments, anonymised to protect client confidentiality, all built on the same skeleton shown above.
Need a developer on your testing program? Let’s talk.
Email me, message me on LinkedIn, or leave a note here. I’ll get back to you soon.