← Duolingo
Bringing AI in at Duolingo

Trace test failures before learners abandon the purchase flow

You’re the software engineer. Your team is in the room. Printed Oct 15, 2026.

Fast subscription experiments lose value when evidence is scattered across the purchase flow.

The investigation needs speed for active experiments and proof before an engineer changes a high-traffic surface.

Who you’d be doing this for

“I picked a plan after my lesson, then the screen sent me back where I started.”

Farid Zamani · Daily Practice Learner

A learner trying to subscribe after a regular lesson session during an active purchase-flow experiment.

What is at stake

Subscription experiments are showing different purchase results after the same paywall change. You must weigh faster diagnosis against the evidence an engineer needs before changing a live flow.

Why it isn’t already fixed

Every obvious fix costs something else. That’s the part you’d have to decide.

  • diagnosis speed vs. engineer verification
  • Android signals vs. backend evidence
  • experiment velocity vs. learner exposure
  • AI ranking vs. causal proof

Why Duolingo

Subscriber Conversion experiments shape how daily learners move from free practice into paid access.

Written with these in mind

forward deployed engineerAI systems integratorproduct infrastructure engineer

Not your kind of problem? 19 more at Duolingo, or browse every organization.

This is the setup. The work is inside.

Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.