Task library RTELEMETRY Privacy engineering · Phased project Measure a workflow without collecting its private content A fictional document workspace wants to measure upload completion and failure. Its prototype sends filenames, document titles and raw errors to general analytics. Replace that path with a minimal event contract using synthetic traffic.
Practice brief · Version 5
Project scope 10 tickets / 3 phases
Total focused work estimate 29h + setup
Suggested stack TypeScript · JSON Schema · HTTP collector double · SQL Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.
Choose a bounded subset for an assessment or practice session. Prerequisites and remaining project work must be agreed separately.
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Pattern topics identify design choices to practice. Read the ticket's acceptance criteria and justify the simplest suitable approach. Tags are not capability or ownership evidence; an untagged ticket has no curated pattern topic assigned.
Recommended next step Start with RTELEMETRY-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice minimization, safe failure handling and correct aggregates.
What the team gains Produce useful operational measurements with a reviewable collection boundary and disclosure regression suite.
Before you start Create synthetic upload workflows and a local collector that captures received payloads. Define measurement questions and a separate restricted diagnostic store fixture. Delivery agreement Ten tickets using synthetic data. No claim of anonymization, privacy certification or measured customer behavior is made.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Define useful questions and an allowlisted event schema.
PHASE 2 Reject accidental content, separate diagnostics and bound retention.
PHASE 3 Reconcile aggregates and test disclosure under failures.
Specify minimal measurement Define useful questions and an allowlisted event schema.
RTELEMETRY-101 Entry ticket; project setup still required Estimated field mix
Privacy engineering 80% Data engineering 20% RTELEMETRY-102 Depends on RTELEMETRY-101 Estimated field mix
Privacy engineering 60% Security 40% RTELEMETRY-103 Depends on RTELEMETRY-101, RTELEMETRY-102 Enforce collection limits Reject accidental content, separate diagnostics and bound retention.
RTELEMETRY-104 Depends on RTELEMETRY-102 Estimated field mix
Privacy engineering 70% Site reliability 30% RTELEMETRY-105 Depends on RTELEMETRY-103, RTELEMETRY-104 Estimated field mix
Privacy engineering 60% Security 40% RTELEMETRY-106 Depends on RTELEMETRY-102, RTELEMETRY-104 Estimated field mix
Privacy engineering 60% Site reliability 40% RTELEMETRY-107 Depends on RTELEMETRY-103, RTELEMETRY-105, RTELEMETRY-106 Estimated field mix
Privacy engineering 60% Data engineering 40% Verify useful reporting Reconcile aggregates and test disclosure under failures.
RTELEMETRY-108 Depends on RTELEMETRY-101, RTELEMETRY-103, RTELEMETRY-107 Estimated field mix
Privacy engineering 70% Data engineering 30% RTELEMETRY-109 Depends on RTELEMETRY-101, RTELEMETRY-106, RTELEMETRY-107 Estimated field mix
Site reliability 50% Data engineering 30% Privacy engineering 20% RTELEMETRY-110 Depends on RTELEMETRY-102, RTELEMETRY-104, RTELEMETRY-105, RTELEMETRY-106, RTELEMETRY-107, RTELEMETRY-108, RTELEMETRY-109 Estimated field mix
Privacy engineering 50% Quality engineering 50% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.