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.
Today's usable audience competes with the cost of maintaining another mapping.
Preserving the destination's existing imports leaves the customer responsible for an adapter.
Who you’d be doing this for
“My preview has 3,600 fewer people than the approved list, and the review is this afternoon.”
Moraa Mutua · Marketing Operations Manager · a character in this brief
Waiting to use the first audience in an existing engagement channel.
What is at stake
An audience export rejects 3,600 eligible profiles because their identifiers lose leading zeros. You must weigh a maintained adapter against changing a destination shared by other imports.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- local adapter ownership vs shared configuration change
- today's acceptance proof vs broader regression coverage
- export success vs usable membership
Why Databricks
Unity Catalog retains the identifiers needed for activation while Lakewatch exposes the loss at the destination boundary.
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
- Partner Solutions Architect specializing in Customer Lake and Lakewatch , you are an expert-level technical leader responsible for accelerating platform adoption and scaling growth across our strategic partner ecosystem (SIs, GSIs, ISVs, and Cloud Providers).
- 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.
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 make the background systems nobody sees behave dependably even under heavy, high-volume real-world load.
Eleven of the 18 committed workflows still need manual follow-up to provision accounts or hand over equipment, and hiring dates are fixed.
You have to weigh a faster launch against the risk of wrong access or a dropped handoff.
Deal managers are opening dozens of document views to infer which reviewers are engaged.
You have to weigh a faster deal signal against permission-safe visibility.
Incorrect confirmations are sending patients into clinic callbacks and invalid appointment slots.
You have to weigh rapid restoration against the proof needed before changing a live scheduling workflow.
