Suggestions
Richard Gaywood
Privacy Engineer at Google
Richard Gaywood is a Privacy Engineer working on Android at Google. He is based in London, England, United Kingdom.1 Here are some key details about his professional background and current role:
Current Position
Richard currently serves as a Privacy Engineer for Android at Google, a position he has held since June 2022.1 In this role, he:
- Performs privacy design reviews and provides expert consultation on meeting privacy requirements
- Consults at all project stages, from requirements gathering to final launch approval
- Helps product teams navigate complex privacy landscapes
- Specializes in Enterprise and Wear OS within the Android platform
Previous Roles at Google
Before his current position, Richard held other roles at Google:
- Senior Software Engineer, Android Telemetry (June 2018 - June 2022)
- Tech Lead / Senior Software Engineer (February 2014 - June 2018)
Skills and Expertise
Richard describes himself as a Java architect with wide-ranging commercial experience.1 His areas of expertise include:
- Software architecture
- Design patterns
- Scalability engineering
- Test-driven development
- Build automation
- System administration
Professional Qualities
Richard highlights several professional qualities, including:
- Proven track record of reliable delivery
- Exceptional problem-solving and analysis skills
- Excellent written and verbal communication abilities
- Customer awareness and focus on commercial issues during technical work
Richard Gaywood's LinkedIn profile provides a comprehensive overview of his professional experience and skills, showcasing his progression within Google and his current focus on privacy engineering for Android.
Highlights
"Yes change jobs every few years to raise salary and gain breadth. But it is crucial, nay critical, that at some point you stay somewhere for 4 years or more. Nothing teaches you software architecture like dealing with your own crap from 3+ years ago. You cannot call yourself an experienced engineer if you haven’t done this." -- Swizec Teller, https://lnkd.in/ekJeyatT
I'm not sure it's "critical" exactly but I sure did learn a lot this way.
got a cold call from a recruiter earlier (I think it was a recruiter, I wasn't paying attention to the pitch) who wants to "introduce me to their client" (some fintech outfit) because "my skills are a match"...
me: "where did you get my number" them: "via {didn't catch this, sounded like 'zoom'}, which collects it from LinkedIn profiles" me: "so if you can see my LinkedIn you can see I am a privacy policy expert right" them: "yes" me: "so do you want to discuss how many ways you're breaking the GDPR right now, or do you want to hang up and go about your day" them: "ok thank you goodbye"
(aside: my linkedin profile doesn't have my phone number on it)
this is maybe a bluff on my part; perhaps somewhere in some labyrinth TOS I "consented" to being contacted in this way. But it sure shut the conversation down fast, which was my goal.
