tezvyn:

Implementing a consistent-assignment A/B test

Source: interviewintermediate

WHAT IT TESTS: End-to-end experiment engineering. OUTLINE: Need an assignment service, exposure logging, and event tracking; ensure stickiness by hashing a stable user id; analyze conversion per variant. RED FLAG: Bucketing on session or device.

WHAT IT TESTS: Whether you can build a correct experimentation pipeline. ANSWER OUTLINE: Components are a feature-flag assignment service, exposure logs, and event tracking. Consistency across sessions and devices comes from deterministic bucketing, hashing a persistent user id plus experiment key, so the user always maps to the same variant; fall back to device id when logged out. Analysis joins exposures to purchase_complete events and computes conversion per variant.

Read the original → interview

Get five bites like this every day.

Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.

Implementing a consistent-assignment A/B test · Tezvyn