How the interviewer opens it
“Design a service that estimates whether a request comes from a device it has seen before. Client signals can change or be false.”
The prompt is vague on purpose. The first minutes are for you. Reduce the prompt to the core features and agree on the numbers before you draw.
What to clarify first
- Meaning of a match
- Available signals
- Scale
- Read and write mix
- Latency and freshness
- Consistency and durability
- Match quality
- Record sizes and retention
- Privacy and erasure
- Excluded behavior
The interviewer has the answers. In a SysRound round, Alex gives these answers, as a real interviewer does.
Scope of a strong answer
Core requirements
- Estimate a device match within one tenant and return confidence or unknown
- Record eligible observations and tolerate normal signal changes
- Measure precision and repeat-device coverage with independent labels
- Enforce consent, retention, and data erasure
Usually out of scope
- Identify a person
- Link devices across tenants or websites
- Make final authentication or fraud decisions
- Collect hardware identifiers or invasive browser signals
What interviewers ask about
- Match quality
- Many devices share the same signals. The service must improve useful coverage without exceeding the false-match limit.
- Signal changes and false reports
- Normal changes and false reports can look alike. Unsafe profile updates let an attacker alter future match results.
- Lookup latency
- Common signals can describe millions of devices. The service must bound lookup work without losing all useful coverage.
- Consent and erasure
- Observations spread into profiles, indexes, caches, and journals. Delayed work and recovery can restore data after erasure.
Common mistakes
- Treats a fingerprint as a unique device identifier.
- Reports high precision while ignoring near-zero coverage.
- Uses previous match decisions as independent device labels.
- Lets uncertain matches change profiles without limits.
- Ignores large lookup workloads from common device traits.
- Deletes profiles but retains recoverable evidence in indexes, journals, caches, or backups.
The bar by level
- Senior (L5/E5)
- Bounds lookup work and defines a valid precision and coverage evaluation. Handles signal drift, unsafe updates, and delayed observations. Covers index history and payload keys in the erasure design.
- Staff (L6+/E6+)
- Defines release decisions under uncertain labels and population changes. Controls tenant interference and recovery capacity. Traces erasure through concurrent writes, journals, key copies, unavailable replicas, and restores.
Sources · 1 reference
These records explain where the question appears. A company tag or candidate report does not guarantee a future interview question.
SysRound · 1 record
No company association
Design a device fingerprinting service
Reported date not specified
Source snapshot: Nov 12, 2026
View source