Receive a problem, not an answer key
Start with a workplace-style assignment, evidence and stakeholder information. Work out what needs investigation before changing settings or code.
Learn privacy engineering by doing the work.
Instead of only reading explanations or selecting multiple-choice answers, students practice investigating technical problems, making implementation decisions and validating outcomes in a simulated organization.
How a lab progresses
The precise tools and tasks vary by week, but the instructional approach follows a consistent engineering workflow.
Explore a simulated environment
Navigate tools, documents and technical evidence related to the problem. The exercises model implementation constraints and downstream consequences without exposing a real organization's private systems.
Make and defend technical decisions
Compare approaches, make configuration or workflow choices, and identify tradeoffs. Some exercises include Low-Code options; others call for more direct technical editing.
Test what actually happened
Validate technical outcomes, investigate failed checks and prepare a QA procedure. A passing result should reflect the work completed, not simply a written assertion.
Communicate a useful handoff
Summarize findings, explain testing evidence and recommend follow-up work for a simulated engineering or privacy team.
Different levels of technical depth
Low-Code mode
Where offered, learners inspect functional descriptions or code locations and choose between plausible implementation changes. Options still require technical reasoning; not every option is correct.
Realistic mode
Where offered, learners work more directly with files, configuration and implementation behavior. The aim is to practice practical troubleshooting, not complexity for its own sake.
Specific modes differ by weekly exercise. Public descriptions do not include assessed code snippets, hidden validation logic or correct challenge sequences.
Testing is part of the assignment
State the expected outcome
Describe the privacy or implementation requirement and the visitor or system state being tested.
Observe the system
Use technical checks and reasonable manual validation to confirm what the application actually does.
Record the result
Document failures, evidence and follow-up testing in a structured procedure that can support an engineering handoff.
Support and assessment integrity
Students can use explanations and troubleshooting guidance to learn. Assessed decisions and implementation work are intended to be their own. Technical validation and private scoring support the learning objectives; individual student-specific scenarios are not part of the current design.
Try the concepts before joining
Our free guides explain why a consent banner can fail, how to investigate data flows, and how to design more reliable DSR workflows.
Want updates on the next cohort?
The bootcamp is still being developed. Join the early-access list to receive announcements when program details and enrollment information are confirmed.