18Decompose: merge patient records across a network of hospitals.▼hardPalantirDatabricksMicrosoft2 replies○ sign inThe purest data-modeling prompt Palantir asks, the whole interview lives in the entity-resolution edge cases. Twins, maiden names, shared insurance IDs... and one architectural decision about merging that candidates get fatally wrong.Open full answer →
32Decompose: allocate hospital resources, beds, staff, equipment, across competing patient needs▼hardPalantir1 replies◆ premiumA reported Palantir FDSE decomposition where the fatal move is putting triage inside an algorithm. The bed-capability data model, the visibility-before-optimization v1, and the conflicting-priorities answer that keeps clinicians in charge.Open full answer →
20A hospital wants an LLM feature over patient records. What does HIPAA actually require of your design?▼mediumMicrosoftPalantirSalesforce1 replies○ sign inHIPAA-with-LLMs questions test whether you know the three things that gate the deal: the BAA, the minimum-necessary standard, and audit controls. Engineers who can name 45 CFR obligations in design terms win these rooms.Open full answer →
