Lead with privacy scope
Put your current privacy title, years of experience, and the main laws or regions you cover near the top. Show the company setting and the teams you advise, such as product, marketing, security, and procurement. This helps employers understand whether your work fits their footprint. Avoid implying that a US-based role is a formally appointed GDPR DPO unless it was.
Show the work and outcome
Describe the privacy process you changed, how you worked through it, and a credible result. Useful measures include DPIAs completed, vendor reviews handled, request turnaround time, or teams brought into a review workflow. Explain the baseline and period when you can. Do not claim that a program made an organization fully compliant; show the specific control, decision, or improvement you contributed.
List credentials precisely
Give the full name and issuer for credentials such as CIPP/E or CIPP/US, and make clear whether each is current. These are professional certifications, not government licenses. If a role expects legal advice, distinguish your privacy operations experience from bar admission and include a jurisdiction only if you are admitted there. Leave out expired or unearned credentials.
Name tools and frameworks
Include privacy platforms such as OneTrust only if you have used them, and describe the task they supported, such as request routing or records management. Mention DPIAs, data mapping, Standard Contractual Clauses, or incident response where they fit your actual work. Keep the resume focused on relevant systems and methods; omit generic office software and confidential details about incidents or customers.