Proton, the company behind ProtonMail and other privacy-focused products, told staff on Monday it would be ‘re-interviewing’ staff across the company about how they use AI in their jobs, with the implication that the interviews may decide whether staffers have “continued employment,” according to an internal Proton email obtained by 404 Media.
“These re-interviews are consequential,” a part of the email reads. “Interviewers will document their assessments, which will inform the broader review of our organization and talent. That review may lead to changes in roles, responsibilities, and continued employment. Individual outcomes will be communicated directly once decisions are finalized.”
Proton’s CEO Andy Yen has steadily pushed the company towards more AI use, including launching AI centered products like Lumo, a privacy-focused chatbot. The leaked email says Yen “interviewed more than 40 senior leaders across Engineering and Product to begin this process.” Now, those interviews are extending across the company.
💡
Do you work at Proton? I would love to hear from you. Using a non-work device, you can message me securely on Signal at joseph.404 or send me an email at joseph@404media.co.
“We need people who can translate AI’s capabilities into better products, stronger execution, and new ways of working — and who approach this change with curiosity, judgment, and urgency,” the email reads.
The email says that not everyone in the company will be re-interviewed, and “any decisions affecting your employment will be communicated separately.” The interviewer will be outside the staff member’s team and reporting line; instead, people may be interviewed by someone from “a pool of leaders who demonstrate strong AI capability and have aligned on the assessment criteria.”
“We recognize that this process creates uncertainty. We will be clear about what has been decided and what remains open, and communicate individual outcomes as soon as we can,” the email adds. It says the re-interviews will take place between November 4 and 11.
Proton did not immediately respond to a request for comment.
