Search⌘ K
AI Features

Practice: Designing an Operational System With Access Control

Work through a complete FDSE-style System Design for an operational review workflow with real access control, as practice for Palantir's System Design round. Enforce facility scope on the server, coordinate permission, freshness and version checks in one transaction before recording a decision, and trace an incident through replay, schema failure and recovery. Keep exports behind current authorization, calculate workload honestly, and defend trade-offs with clear reconsideration triggers.

Give a supervisor a usable failed-inspection review list without exposing another facility’s records or inspector contacts,even when the inspection feed stops advancing. Your deliverable is a complete operational design whose arrows explain what the supervisor can see, what they can record ,and what survives failure. The difficult boundary is the moment a review selection becomes durable: permission, source freshness and both versions must agree there.

What must your five-facility design deliver?

The official FDSE posting describes customer-facing architecture and design, business-critical data, custom applications and end-to-end implementation. Those responsibilities support this practice’s relevance; they do not establish that this exact task appears in interviews.

Use the complete packet below before attempting your design.

Authority, ownership and source contract

  • Workflow: Supervisors decide which failed equipment inspections need a follow-up review. Version one covers five facilities. Recording a selection does not dispatch technicians, change equipment controls or certify equipment safety.

  • Source ownership: Inspection identity, equipment reference, result, revision, event time, and restricted inspector contact details.

  • Local ownership: Facility placement, reviewer assignment, review disposition, and local version. Ingestion must preserve these fields.

  • Permissions: Supervisors can view and act only within their currently authorized facilities. Inspector contacts must be excluded from supervisor views and exports. Background work receives only the access its responsibility requires.

  • Source guarantees: Monotonically increasing per-inspection revisions, canonical content comparison, replayable change pages, explicit deletion markers, and a source-confirmed complete-through UTC timestamp after each completed bounded catch-up.

  • Freshness: Poll every minute. Coverage older than three minutes makes the list stale and blocks source-dependent review selections on the server. Previously committed records may remain visible within current permissions, retaining their original cutoff.

  • Exports: Acceptance records a request; generation and retrieval must enforce current requester permissions. A ready file must not bypass revocation.

Workload and operating targets

There are 12,000 inspection updates per ten-hour day and 24 active clients refreshing every 15 seconds. Apply a fivefold peak multiplier to both streams. Retain updates for 180 days at 1 KB each. Ordinary requests target one second; export generation may take 15 seconds. Other request traffic and storage overhead are unspecified.

Incident inputs

All timestamps below are UTC on 2026-10-29.

  1. At 2026-10-29T08:00:00Z, I64 has accepted revision ...