Design Audio Fingerprinting

Hard45 min
1 / 30
understanding•7 min read

Fingerprinting Context and Product Goals

How Fingerprinting Context and Product Goals (understanding) informs Audio Fingerprinting architecture and interviewer depth.

Fingerprinting Context and Product Goals

Design a Shazam/Spotify-scale audio fingerprinting platform: Chromaprint-style landmark hashes, inverted indexes for sub-second identification, catalog ingestion, and rights-aware duplicate detection.

Problem framing
  • 80M MAU, 12M peak concurrent identify queries during live events
  • p95 identify latency < 800ms on 15s microphone snippets; false-positive rate < 0.01%
  • Catalog: 100M reference tracks, 400B landmark postings in the inverted index
Design choices
  1. Landmark peak-pair hashing with time-skew tolerant inverted index lookups
  2. Dual-path ingest: batch catalog build plus real-time snippet identify API
  3. Shard index by hash prefix with hot-partition isolation for charting releases
  4. Content-ID workflow with confidence thresholds and human review queue
Deep dive

Explain how product goals and identify use cases affects hash stability, index fan-out, and identify latency.

javaOne Dark Pro
1public final class LandmarkMatcher {
2  private final int minVotes;
3  private final double maxSkewSec;
4 
5  public LandmarkMatcher(int minVotes, double maxSkewSec) {
6    this.minVotes = minVotes;
7    this.maxSkewSec = maxSkewSec;
8  }
9 
10  public MatchResult score(Map<Long, List<Posting>> hits) {
11    Map<String, Integer> votes = new HashMap<>();
12    for (var entry : hits.entrySet()) {
13      for (Posting p : entry.getValue()) {
14        votes.merge(p.trackId(), 1, Integer::sum);
15      }
16    }
17    return votes.entrySet().stream()
18        .max(Map.Entry.comparingByValue())
19        .map(e -> new MatchResult(e.getKey(), e.getValue()))
20        .orElse(MatchResult.none());
21  }
22}
pythonOne Dark Pro
1from dataclasses import dataclass
2 
3@dataclass(frozen=True)
4class FingerprintPeak:
5    time_sec: float
6    freq_hz: float
7    amplitude: float
8 
9def chromaprint_landmarks(peaks: list[FingerprintPeak]) -> list[int]:
10    """Pair consecutive peaks into 32-bit landmark hashes."""
11    landmarks: list[int] = []
12    for i in range(len(peaks) - 1):
13        dt = int((peaks[i + 1].time_sec - peaks[i].time_sec) * 100)
14        df = int(peaks[i + 1].freq_hz - peaks[i].freq_hz)
15        landmarks.append(((dt & 0xFFFF) << 16) | (df & 0xFFFF))
16    return landmarks
typescriptOne Dark Pro
1interface IdentifyRequest {
2  sessionId: string;
3  sampleRateHz: number;
4  pcmBase64: string;
5}
6 
7export function rankCandidates(
8  voteHistogram: Record<string, number>,
9  minVotes: number,
10): string | null {
11  const sorted = Object.entries(voteHistogram).sort((a, b) => b[1] - a[1]);
12  const [topId, topVotes] = sorted[0] ?? [null, 0];
13  if (!topId || topVotes < minVotes) return null;
14  return topId;
15}
Interviewer positioning

Tie every component to measurable identify SLOs: p95 latency, precision/recall, and catalog freshness.

Extended Notes
  • Appendix note 1: product goals and identify use cases.
  • Appendix note 2: product goals and identify use cases.
  • Appendix note 3: product goals and identify use cases.
  • Appendix note 4: product goals and identify use cases.
  • Appendix note 5: product goals and identify use cases.
  • Appendix note 6: product goals and identify use cases.
  • Appendix note 7: product goals and identify use cases.
  • Appendix note 8: product goals and identify use cases.
  • Appendix note 9: product goals and identify use cases.
  • Appendix note 10: product goals and identify use cases.
  • Appendix note 11: product goals and identify use cases.
  • Appendix note 12: product goals and identify use cases.
  • Appendix note 13: product goals and identify use cases.
  • Appendix note 14: product goals and identify use cases.
  • Appendix note 15: product goals and identify use cases.
  • Appendix note 16: product goals and identify use cases.
  • Appendix note 17: product goals and identify use cases.
  • Appendix note 18: product goals and identify use cases.
  • Appendix note 19: product goals and identify use cases.
  • Appendix note 20: product goals and identify use cases.
  • Appendix note 21: product goals and identify use cases.
  • Appendix note 22: product goals and identify use cases.
  • Appendix note 23: product goals and identify use cases.
  • Appendix note 24: product goals and identify use cases.
  • Appendix note 25: product goals and identify use cases.
  • Appendix note 26: product goals and identify use cases.
  • Appendix note 27: product goals and identify use cases.
  • Appendix note 28: product goals and identify use cases.
  • Appendix note 29: product goals and identify use cases.
  • Appendix note 30: product goals and identify use cases.
  • Appendix note 31: product goals and identify use cases.
  • Appendix note 32: product goals and identify use cases.
  • Appendix note 33: product goals and identify use cases.
  • Appendix note 34: product goals and identify use cases.
  • Appendix note 35: product goals and identify use cases.
  • Appendix note 36: product goals and identify use cases.
  • Appendix note 37: product goals and identify use cases.
  • Appendix note 38: product goals and identify use cases.
  • Appendix note 39: product goals and identify use cases.
  • Appendix note 40: product goals and identify use cases.
  • Appendix note 41: product goals and identify use cases.
  • Appendix note 42: product goals and identify use cases.
  • Appendix note 43: product goals and identify use cases.
  • Appendix note 44: product goals and identify use cases.
  • Appendix note 45: product goals and identify use cases.
  • Appendix note 46: product goals and identify use cases.
  • Appendix note 47: product goals and identify use cases.
  • Appendix note 48: product goals and identify use cases.
  • Appendix note 49: product goals and identify use cases.
  • Appendix note 50: product goals and identify use cases.
  • Appendix note 51: product goals and identify use cases.
  • Appendix note 52: product goals and identify use cases.
  • Appendix note 53: product goals and identify use cases.
  • Appendix note 54: product goals and identify use cases.
  • Appendix note 55: product goals and identify use cases.
  • Appendix note 56: product goals and identify use cases.
  • Appendix note 57: product goals and identify use cases.
  • Appendix note 58: product goals and identify use cases.
  • Appendix note 59: product goals and identify use cases.
  • Appendix note 60: product goals and identify use cases.
  • Appendix note 61: product goals and identify use cases.
  • Appendix note 62: product goals and identify use cases.
  • Appendix note 63: product goals and identify use cases.
  • Appendix note 64: product goals and identify use cases.
  • Appendix note 65: product goals and identify use cases.
  • Appendix note 66: product goals and identify use cases.
  • Appendix note 67: product goals and identify use cases.
  • Appendix note 68: product goals and identify use cases.
  • Appendix note 69: product goals and identify use cases.
  • Appendix note 70: product goals and identify use cases.
  • Appendix note 71: product goals and identify use cases.
  • Appendix note 72: product goals and identify use cases.
  • Appendix note 73: product goals and identify use cases.
  • Appendix note 74: product goals and identify use cases.
  • Appendix note 75: product goals and identify use cases.
  • Appendix note 76: product goals and identify use cases.
  • Appendix note 77: product goals and identify use cases.
  • Appendix note 78: product goals and identify use cases.
  • Appendix note 79: product goals and identify use cases.
  • Appendix note 80: product goals and identify use cases.
  • Appendix note 81: product goals and identify use cases.
  • Appendix note 82: product goals and identify use cases.
  • Appendix note 83: product goals and identify use cases.
  • Appendix note 84: product goals and identify use cases.
  • Appendix note 85: product goals and identify use cases.
  • Appendix note 86: product goals and identify use cases.
  • Appendix note 87: product goals and identify use cases.
  • Appendix note 88: product goals and identify use cases.
  • Appendix note 89: product goals and identify use cases.
  • Appendix note 90: product goals and identify use cases.
  • Appendix note 91: product goals and identify use cases.
  • Appendix note 92: product goals and identify use cases.
  • Appendix note 93: product goals and identify use cases.
  • Appendix note 94: product goals and identify use cases.
  • Appendix note 95: product goals and identify use cases.
  • Appendix note 96: product goals and identify use cases.
  • Appendix note 97: product goals and identify use cases.
  • Appendix note 98: product goals and identify use cases.
  • Appendix note 99: product goals and identify use cases.
  • Appendix note 100: product goals and identify use cases.
  • Appendix note 101: product goals and identify use cases.
  • Appendix note 102: product goals and identify use cases.
  • Appendix note 103: product goals and identify use cases.
  • Appendix note 104: product goals and identify use cases.
  • Appendix note 105: product goals and identify use cases.
  • Appendix note 106: product goals and identify use cases.
  • Appendix note 107: product goals and identify use cases.
  • Appendix note 108: product goals and identify use cases.
  • Appendix note 109: product goals and identify use cases.
  • Appendix note 110: product goals and identify use cases.
  • Appendix note 111: product goals and identify use cases.
  • Appendix note 112: product goals and identify use cases.
  • Appendix note 113: product goals and identify use cases.
  • Appendix note 114: product goals and identify use cases.
  • Appendix note 115: product goals and identify use cases.
  • Appendix note 116: product goals and identify use cases.
  • Appendix note 117: product goals and identify use cases.
  • Appendix note 118: product goals and identify use cases.
  • Appendix note 119: product goals and identify use cases.
  • Appendix note 120: product goals and identify use cases.
  • Appendix note 121: product goals and identify use cases.
  • Appendix note 122: product goals and identify use cases.
  • Appendix note 123: product goals and identify use cases.
  • Appendix note 124: product goals and identify use cases.
  • Appendix note 125: product goals and identify use cases.
  • Appendix note 126: product goals and identify use cases.
  • Appendix note 127: product goals and identify use cases.
  • Appendix note 128: product goals and identify use cases.
  • Appendix note 129: product goals and identify use cases.
  • Appendix note 130: product goals and identify use cases.
  • Appendix note 131: product goals and identify use cases.
  • Appendix note 132: product goals and identify use cases.
  • Appendix note 133: product goals and identify use cases.
  • Appendix note 134: product goals and identify use cases.
  • Appendix note 135: product goals and identify use cases.
  • Appendix note 136: product goals and identify use cases.
  • Appendix note 137: product goals and identify use cases.
  • Appendix note 138: product goals and identify use cases.
  • Appendix note 139: product goals and identify use cases.
  • Appendix note 140: product goals and identify use cases.
  • Appendix note 141: product goals and identify use cases.
  • Appendix note 142: product goals and identify use cases.
  • Appendix note 143: product goals and identify use cases.
  • Appendix note 144: product goals and identify use cases.
  • Appendix note 145: product goals and identify use cases.
  • Appendix note 146: product goals and identify use cases.
  • Appendix note 147: product goals and identify use cases.
  • Appendix note 148: product goals and identify use cases.
  • Appendix note 149: product goals and identify use cases.
  • Appendix note 150: product goals and identify use cases.
  • Appendix note 151: product goals and identify use cases.
  • Appendix note 152: product goals and identify use cases.
  • Appendix note 153: product goals and identify use cases.
  • Appendix note 154: product goals and identify use cases.
  • Appendix note 155: product goals and identify use cases.
  • Appendix note 156: product goals and identify use cases.
  • Appendix note 157: product goals and identify use cases.
  • Appendix note 158: product goals and identify use cases.
  • Appendix note 159: product goals and identify use cases.
  • Appendix note 160: product goals and identify use cases.
  • Appendix note 161: product goals and identify use cases.
  • Appendix note 162: product goals and identify use cases.
  • Appendix note 163: product goals and identify use cases.
  • Appendix note 164: product goals and identify use cases.
  • Appendix note 165: product goals and identify use cases.
  • Appendix note 166: product goals and identify use cases.
  • Appendix note 167: product goals and identify use cases.
  • Appendix note 168: product goals and identify use cases.
  • Appendix note 169: product goals and identify use cases.
  • Appendix note 170: product goals and identify use cases.
  • Appendix note 171: product goals and identify use cases.
  • Appendix note 172: product goals and identify use cases.
  • Appendix note 173: product goals and identify use cases.
  • Appendix note 174: product goals and identify use cases.
  • Appendix note 175: product goals and identify use cases.
  • Appendix note 176: product goals and identify use cases.
  • Appendix note 177: product goals and identify use cases.
  • Appendix note 178: product goals and identify use cases.
  • Appendix note 179: product goals and identify use cases.
  • Appendix note 180: product goals and identify use cases.
  • Appendix note 181: product goals and identify use cases.
  • Appendix note 182: product goals and identify use cases.
  • Appendix note 183: product goals and identify use cases.
  • Appendix note 184: product goals and identify use cases.
  • Appendix note 185: product goals and identify use cases.
  • Appendix note 186: product goals and identify use cases.
  • Appendix note 187: product goals and identify use cases.
  • Appendix note 188: product goals and identify use cases.
  • Appendix note 189: product goals and identify use cases.
  • Appendix note 190: product goals and identify use cases.
  • Appendix note 191: product goals and identify use cases.
  • Appendix note 192: product goals and identify use cases.
  • Appendix note 193: product goals and identify use cases.
  • Appendix note 194: product goals and identify use cases.
  • Appendix note 195: product goals and identify use cases.
  • Appendix note 196: product goals and identify use cases.
  • Appendix note 197: product goals and identify use cases.
  • Appendix note 198: product goals and identify use cases.
  • Appendix note 199: product goals and identify use cases.
  • Appendix note 200: product goals and identify use cases.
  • Appendix note 201: product goals and identify use cases.
  • Appendix note 202: product goals and identify use cases.
  • Appendix note 203: product goals and identify use cases.
  • Appendix note 204: product goals and identify use cases.
  • Appendix note 205: product goals and identify use cases.
  • Appendix note 206: product goals and identify use cases.
  • Appendix note 207: product goals and identify use cases.
  • Appendix note 208: product goals and identify use cases.
  • Appendix note 209: product goals and identify use cases.
  • Appendix note 210: product goals and identify use cases.
  • Appendix note 211: product goals and identify use cases.
  • Appendix note 212: product goals and identify use cases.
  • Appendix note 213: product goals and identify use cases.
  • Appendix note 214: product goals and identify use cases.
  • Appendix note 215: product goals and identify use cases.
  • Appendix note 216: product goals and identify use cases.
  • Appendix note 217: product goals and identify use cases.
  • Appendix note 218: product goals and identify use cases.
  • Appendix note 219: product goals and identify use cases.
  • Appendix note 220: product goals and identify use cases.
  • Appendix note 221: product goals and identify use cases.
  • Appendix note 222: product goals and identify use cases.
  • Appendix note 223: product goals and identify use cases.
  • Appendix note 224: product goals and identify use cases.
  • Appendix note 225: product goals and identify use cases.
  • Appendix note 226: product goals and identify use cases.
  • Appendix note 227: product goals and identify use cases.
  • Appendix note 228: product goals and identify use cases.
  • Appendix note 229: product goals and identify use cases.
  • Appendix note 230: product goals and identify use cases.
  • Appendix note 231: product goals and identify use cases.
  • Appendix note 232: product goals and identify use cases.
  • Appendix note 233: product goals and identify use cases.
  • Appendix note 234: product goals and identify use cases.
  • Appendix note 235: product goals and identify use cases.
  • Appendix note 236: product goals and identify use cases.
  • Appendix note 237: product goals and identify use cases.
  • Appendix note 238: product goals and identify use cases.
  • Appendix note 239: product goals and identify use cases.
  • Appendix note 240: product goals and identify use cases.
  • Appendix note 241: product goals and identify use cases.
  • Appendix note 242: product goals and identify use cases.
  • Appendix note 243: product goals and identify use cases.
  • Appendix note 244: product goals and identify use cases.
  • Appendix note 245: product goals and identify use cases.
  • Appendix note 246: product goals and identify use cases.
  • Appendix note 247: product goals and identify use cases.
  • Appendix note 248: product goals and identify use cases.
  • Appendix note 249: product goals and identify use cases.
  • Appendix note 250: product goals and identify use cases.
  • Appendix note 251: product goals and identify use cases.
  • Appendix note 252: product goals and identify use cases.
  • Appendix note 253: product goals and identify use cases.
  • Appendix note 254: product goals and identify use cases.
  • Appendix note 255: product goals and identify use cases.
  • Appendix note 256: product goals and identify use cases.
  • Appendix note 257: product goals and identify use cases.
  • Appendix note 258: product goals and identify use cases.
  • Appendix note 259: product goals and identify use cases.
  • Appendix note 260: product goals and identify use cases.

Why interviewers care

Audio Fingerprinting interviews reward crisp scope, explicit trade-offs, and failure stories—not generic microservice diagrams.

Interview checkpoint

Name one failure story for Fingerprinting Context and Product Goals that proves you understand real outages, not happy-path diagrams.

Key Highlights

  • •Landmark hashes plus inverted index for sub-second identify
  • •Offset histograms tolerate speed change and noisy microphones
  • •Blue/green index versions keep catalog fresh without read corruption
Interview Tip
Quantify identify latency, false-positive rate, and index freshness before diving into shards.
What Impresses
Separate ingest, index build, and identify paths; show vote aggregation for noisy mics.
Avoid This
Do not compare raw waveforms at scale—landmark indexes exist for sub-linear retrieval.

Section Rescue Kit

Buzzwords to use:

Landmark hashInverted indexChromaprint

Safe statements:

  • "I optimize for p95 identify latency and measurable precision, not feature count."
  • "Catalog freshness and index versioning are first-class alongside query speed."
Design Audio Fingerprinting - System Design | WinJob | WinJob