Discovery must become faster without turning governed data into a guessing game.
Data engineers need a credible route to reusable assets, while asset owners need permissions and context to remain intact.
Who you’d be doing this for
“I spent half the morning opening tables with the same name, then my analyst asked why the numbers still didn’t match.”
Arnav Tiwari · Senior Data Engineer
Maintains shared ingestion and transformation pipelines for an enterprise data team with a large governed catalog.
What is at stake
Enterprise data engineers are opening multiple lookalike assets before finding one they can use. You must weigh faster discovery against permission-aware relevance and trust.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- faster asset discovery vs governed access clarity
- learned relevance vs explainable catalog rules
- popular results vs fresh authoritative assets
- interactive latency vs ranking depth
Why Databricks
Unity Catalog metadata and Databricks usage signals make governed discovery a product surface rather than another manual inventory.
Written with these in mind
Not your kind of problem? 107 more at Databricks, 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.