Design AR Platform - System Design | WinJob

Problem Statement: Cross-Platform AR Runtime

Design AR Platform-class spatial computing stack: device SLAM, cloud anchors, recognition, and creator experiences. This section covers problem statement: cross-platform ar runtime in the understanding phase.

Operational detail

Quantify anchor resolve p95, mesh upload MB/s, and recognition QPS before naming GPUs. State AP for ephemeral poses and CP for published experiences and billing.

Failure and edge cases

drift without relocalization

duplicate cloud anchors on retry

shipping raw camera frames to object storage

Interview checkpoints

javaOne Dark Pro

1  
2 public record AnchorPose(String anchorId, long seq, float[] transform16, long capturedAtMs) {}
3

pythonOne Dark Pro

1  
2 def geohash_tile(lat: float, lon: float, precision: int = 7) -> str:
3     import hashlib
4     return hashlib.sha256(f"{lat:.5f}:{lon:.5f}:{precision}".encode()).hexdigest()[:12]
5

typescriptOne Dark Pro

1  
2 export function shouldUploadMesh(vertexCount: number, maxVertices: number): boolean {
3   return vertexCount > 0 && vertexCount <= maxVertices;
4 }
5

Why interviewers care

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

Interview checkpoint

Name one failure story for Problem Statement: Cross-Platform AR Runtime that proves you understand real outages, not happy-path diagrams.

Key Highlights

•on-device tracking loop
•cloud anchor resolution
•creator experience distribution
•privacy-first camera pipeline

1
2	public record AnchorPose(String anchorId, long seq, float[] transform16, long capturedAtMs) {}
3

1
2	def geohash_tile(lat: float, lon: float, precision: int = 7) -> str:
3	import hashlib
4	return hashlib.sha256(f"{lat:.5f}:{lon:.5f}:{precision}".encode()).hexdigest()[:12]
5

1
2	export function shouldUploadMesh(vertexCount: number, maxVertices: number): boolean {
3	return vertexCount > 0 && vertexCount <= maxVertices;
4	}
5