The setting
offers , an add-on for testing versions of a web page and showing different messages to different audiences. Marketers and website teams use it to see which versions perform better.
Experiment results demand fast explanations, while event evidence remains scattered across the serving path.
Marketing managers need a decision they can trust, and engineers need to preserve judgment over incomplete evidence.
Who you’d be doing this for
“My VP asked why last week’s winner disappeared, and I still don’t have an answer I can stand behind.”
Ylva Rasmussen · Marketing Manager · a character in this brief
Runs website experiments and must decide whether a reported winner should change a live customer journey.
What is at stake
Selected investigations must reach an engineer-confirmed cause within one business day in 70% of cases. You decide who picks which event path to follow first when duplicated events, late arrival and a serving change all look alike: the embedded system's ranking or the engineer on the investigation.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- broad event coverage vs high-throughput reliability
- ranked evidence vs incomplete event trails
- marketing reporting window vs late event arrival
- pilot utility vs operational ownership
Why Webflow
Webflow Optimize turns visitor events into experiment decisions for marketing managers running customer-facing websites.
Written with these in mind
Not your kind of problem? 36 more at Webflow, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Webflow. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Senior Staff Software Engineer · no longer posted
- Without ever sacrificing craft or quality for modern marketing teams, helping organizations build, manage, and optimize high-performing web experiences that drive predictable growth and strengthen brand trust.
- Partner effectively with product, design, data science, and ML stakeholders to translate evolving business needs and customer outcomes into scalable technical solutions.
- Staff Software Engineer, Convert · no longer posted
- This is a cross-team technical leadership role, which means you’re working across a large, complex, revenue-generating system and figuring out what it needs to become.
- Senior Software Engineer, Site Discovery & Localization · no longer posted
- Provide technical mentorship and code review for peers within the team.
- We’re looking for a Senior Software Engineer to help us build the next generation of intelligent content experiences — empowering creators to grow their audiences and reach new markets directly within Webflow
- Senior Fullstack Engineer, Analyze Product · no longer posted
- Participate in all engineering activities including incident response, interviewing, designing and reviewing technical specifications, code review, and releasing new functionality.
- Build, document, and test production code that impacts all Webflow customers.
Reporting read before this brief was written
The pieces closest to the situation in this brief.
As of October 2026, MIT Technology Review reports that agentic web traffic tripled from August to September, and that many websites are blocking AI agents that consumers send to their sites.
Making the internet better for AI agents might make it worse for everyone else | MIT Technology Review (opens in a new tab) · technologyreview.com · Oct 19, 2026
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.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these is about figuring out which problem is actually worth solving.
Analysts hit empty drill-down results after a dashboard summary loads, and engineers cannot quickly agree where the failure began.
You have to decide where the AI's trace across the React flow, the SQL request, and Unity Catalog access context stops and where the engineers' own confirmation of the cause starts.
Selected failed research sessions need an engineer-confirmed cause within 30 minutes in 80% of pilot cases.
You have to decide where the AI's reading of request traces, Redis signals and funnel events stops and where the engineers' own confirmation of a cause begins.
Visual planners hit blank board pages after certain return visits, and engineers cannot yet agree on the failure chain.
You must decide what the system can rank from evidence and what engineers must confirm before shipping.
Other problems with a similar purpose
In each of these, as in this one, the aim is to find the real question hiding behind incomplete evidence and choose a reversible next step instead of guessing.
Product managers read homeowner, pro and metric evidence on urgent repairs separately and reach different conclusions.
You have to decide where the AI's clustering of that evidence stops and a product manager's framing of the problem begins before a test is shaped.
A major advertiser may move $1.5 million after finance disputes whether reported sales were incremental.
You must weigh a compelling cross-format growth case against the evidence each claim can support.
A 4,000-seat business program may not renew because executives dispute what learner progress proves.
You have to weigh a fast commercial save against claims the evidence cannot support.
