The setting
' is a customer data platform that merges scattered customer records into single profiles and builds audiences for marketing. It lets marketing and data teams use customer data without copying it into a separate system.
A reusable evaluation integration needs a stable contract before the retailer agrees what evidence it wants.
Operators need a credible purchase result, while delayed POS outcomes and competing evaluation questions pull the first version in different directions.
Who you’d be doing this for
“Someone asked how many purchases happened because of the recommendations, and I had to send another attributed-sales chart.”
Som Boonmee · Marketing Operations Manager · a character in this brief
Must explain whether personalized recommendations justify expanding audience activation into more stores.
What is at stake
A retailer needs proof of additional store purchases, but its POS outcomes arrive two to seven days late. You must choose what reusable integration operators can trust and run themselves.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- credible lift evidence vs accessible operation
- one customer's conventions vs reusable contracts
- early results vs delayed purchases
- one-off study speed vs independent repeatability
Why Databricks
Governed audience decisions in Unity Catalog and operational signals in Lakewatch provide the foundation for a customer-operated evaluation pattern.
Written with these in mind
Not your kind of problem? 115 more at Databricks, 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 Databricks. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Sr. Solutions Architect (CustomerLake) (opens in a new tab)
- Sr. Partner Solutions Architect - Customer Lake & Lakewatch (opens in a new tab)
- Expand Lakewatch Observability: Guide partner engineering teams on deploying Lakewatch to deliver automated data quality monitoring and health telemetry across customer implementations
- You serve as the definitive technical authority and trusted advisor for partner technical practices, empowering them to architect, position, and deploy enterprise solutions built on o ur Customer Lake platform, while leveraging Lakewatch for data quality and system monitoring.
- Sr. Solutions Architect, Customer Lake (opens in a new tab)
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.
Retailers who placed a first order are not returning despite follow-up ads.
You must decide where the system's proposed test stops and the strategist's choice of audience, message or offer begins.
Opening Soon strategists are drawing different next-test conclusions from the same LinkedIn results.
You must decide what AI recommends, what evidence it cites, and where strategist judgment remains required.
Ten newly live retailers need a shared way to show whether digital commerce is changing household behavior within 90 days.
You have to weigh a repeatable coverage model against the retailer-specific evidence executives will trust.
The same setting, from another role
Each is set around Databricks’s CustomerLake, written for a different role. They’re separate briefs, not the same scenario.
Campaign totals change after platform refreshes, leaving marketing operations unable to tell a restatement from a broken normalization path.
You must decide what evidence AI can assemble and what engineers must still confirm.
Marketing operations cannot reliably forecast what a large audience activation will consume.
You must weigh a fast estimate against the governance and accuracy needed for it to be trusted.
Incorrect Android identity merges have put household members into each other’s audiences.
You must weigh immediate consent protection against preserving the event history needed to rebuild profiles.
Other problems with a similar purpose
In each of these, as in this one, the aim is to turn a person's earliest brush with a product into a habit they keep coming back to.
Sixty-two percent of newly activated workspaces do not return for a second production session within 21 days.
You must weigh a scalable configuration-and-enablement path against a simpler setup change that uses the same capacity.
New enterprise accounts are starting tables but not returning to run a second workflow.
You have to weigh a fast activation path against a promise that still feels safe for RevOps.
New desktop users are skipping iOS setup and staying in a single-device inbox habit.
You need to decide how prominently mobile setup belongs before users reach their first inbox.
