About the role

Testifize is a measurement and experimentation consultancy. We are hiring a senior engineer to lead the technical side of a long-running client platform engagement: embedded alongside the client's product and engineering teams, owning how experimentation and personalisation are delivered across a high-traffic retail web estate.

This is a tech-lead role, not a ticket-taking one. You will own how experimentation sits inside the delivery stack: the feature-flagging platform, the edge and caching layer, the content platform and the customer-data integrations that feed audience targeting. You will be the person product managers and analysts come to when an experiment is not behaving. Expect to spend as much time explaining, reviewing and pushing back as you do writing code.

We are hiring for communication first. The person we want can explain a caching problem to a product manager, argue a design choice in an architecture forum without making enemies, and write a clear Teams message at 5pm on a Friday about why an experiment has to be restarted. If you are technically brilliant but prefer to work heads-down and hand over at the end, this is not the right fit.

What you'll be doing

• Own the feature-experimentation platform implementation across web (server-side and client-side SDKs): decision calls, user-ID strategy, attribute and audience plumbing, event tracking into the analytics stack.
• Lead delivery and ongoing support of edge-side experimentation, including the caching strategy for experiments on server-rendered, CDN-cached pages, variant injection at the edge, and the deployment workflow around it.
• Own the integrations that let non-engineers run experiments: a content-first resolution model with the CMS, audience segmentation fed from the customer-data platform, and the no-code path for editors and PMs to launch tests without a deployment per experiment.
• Run technical investigations when experiments misbehave: sample-ratio mismatches, flicker, consent-timing gaps, redirect and bucketing loss, tag-propagation differences between arms. Find the root cause, fix it or specify the fix, and write it up so the analysts and PMs understand it.
• Review experiment code from product teams before launch and after. Catch wrong activation points, wrong activation scope and missing tracking before they cost a restart.
• Represent experimentation in engineering forums: design authority submissions, architecture reviews, security reviews, long-term support models for the edge layer.
• Maintain a debugging knowledge base and an onboarding path for engineers new to experimentation, so quality holds as more teams ship behind flags.
• Work day-to-day with our experimentation lead and two embedded analysts, and with the client's product managers, web platform engineers and analytics team.