Becoming A Privacy Engineer
Article 25 of the GDPR never mentions engineers. It tells the controller to implement “appropriate technical and organisational measures”, designed to apply principles such as data minimisation “in an effective manner”. A policy can’t be effective in that sense. Only a system can, and a privacy engineer is the person who makes it so. If you are wondering how much of that you already know, the free CIPT assessment gives you a score per domain in about fifteen minutes.
Moreover, the obligation is broad. The European Data Protection Board says in its Guidelines 4/2019 on data protection by design and by default that it is “an obligation for all controllers, irrespective of size and varying complexity of processing”. The Board adopted the final version 2.0 on 20 October 2020. Article 25(2) then adds the default: only data necessary for each purpose, limited in amount, extent of processing, storage period and accessibility.
From a legal text to a design decision
That second paragraph reads like a specification, and a privacy engineer treats it as one. How long does this table keep a record? Who can query that field? Does the app need a birth date, or only whether someone is over eighteen? 22Academy’s career plan for the privacy engineer describes the role the same way: it “turns a legal requirement into a design: what data a system collects, how long it keeps it”. The CIPT course page shows how the exam tests that translation.
Three properties a privacy engineer can test
The GDPR states principles. It doesn’t tell you how to check a system against them. However, NIST filled part of that gap in January 2017 with NISTIR 8062, an introduction to privacy engineering for US federal systems. It defines privacy engineering as a specialty discipline of systems engineering. Then it names three privacy engineering objectives, each of which you can test on a real system:
- Predictability: “Enabling of reliable assumptions by individuals, owners, and operators about PII and its processing by a system.”
- Manageability: “Providing the capability for granular administration of PII including alteration, deletion, and selective disclosure.”
- Disassociability: “Enabling the processing of PII or events without association to individuals or devices beyond the operational requirements of the system.”
PII is the US term for personal information. Our piece on the three privacy engineering objectives works through each one with examples.
What the three properties look like at work
In practice, these are questions a privacy engineer asks in a design review. For example, predictability asks whether the privacy notice and the system tell the same story. Manageability asks whether a deletion request reaches every copy, including the backups and the analytics store. Disassociability asks whether the reporting dashboard really needs user IDs, or only counts. Each question has a yes or no answer. The CIPT course costs €37 a week and opens every lesson on the first day, so you can go straight to the domain you need.
Who becomes a privacy engineer
Despite the title, the field is wider than software development. The IAPP’s definition of privacy engineering, written by its Privacy Engineering Section Advisory Board, covers software development and system design. It also covers data science, process design, IT infrastructure and user experience design.
That opens the role to people from several directions. A security engineer brings threat modelling and access control. Likewise, a data scientist brings an understanding of what aggregation and de-identification can and can’t do. In turn, a UX designer brings the screens where consent and choice actually happen. Meanwhile a privacy professional without a technical background brings the legal requirement that everyone else has to meet. The UK’s Information Commissioner’s Office even writes its guidance on privacy in the product design lifecycle for product and UX designers, software engineers, QA testers and product managers.
What the day-to-day work looks like
The career plan lists design reviews, deletion and retention jobs, tooling for access requests and data maps. A privacy engineer works with product, security and legal teams “to make sure what is promised is what the system does”. So the job is half technical and half translation. The free CIPT assessment shows which half needs more work in your case.
The CIPT and the route for a privacy engineer
No law requires a certificate. Employers, however, may ask for evidence that a privacy engineer understands the requirements as well as the technology. The IAPP’s CIPT page says the credential shows that you understand “how to use technical solutions to build data protection into products and services”.
The career plan suggests the CIPT first and the CIPP/E second, at about a month each on average at three hours a day. If you already hold the CIPT, start with the CIPP/E. Our CIPT study guide covers the exam itself in detail.
Check which Body of Knowledge you study from
The Body of Knowledge is the IAPP’s outline of what an exam covers. For the CIPT, version 4.0.0 took effect on 1 September 2025, with five domains instead of seven. When we checked in November 2026, a link on the IAPP’s CIPT page still opened version 3.2.0. So check the version number on the first page of whatever you study from. The CIPT course page follows the current version.
A first design review of your own
First, start with one system you already know. Map what it collects, where the data goes, how long it stays and who can reach it. Then test it against the three NIST properties. That exercise is the job in miniature, and it shows quickly whether the legal side or the technical side needs more study.
Next, measure before you plan your study. The free CIPT assessment takes about fifteen minutes and comes with a study-time estimate. If you want to practise with others, our CIPT Study Group on Facebook and Privacy Study Group on LinkedIn post a scenario and a practice question every week.
