TL;DR
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
Proton published an internal engineering memo that calls for engineers to shift from writing code themselves to directing AI tools and agents. The memo says Proton has not yet moved beyond using AI to speed up existing tasks, but the supplied source ends before laying out the rest of its proposed adoption plan.
Proton has published an internal engineering memo arguing that its software teams must change how they work with AI coding tools, shifting engineers from writing code directly to directing and reviewing work done by models. The company’s chief executive describes AI adoption as a matter of competitiveness, while acknowledging the memo is a statement of direction rather than a detailed engineering or security plan.
The memo, published on Proton’s blog as an “AI @ Proton, Engineering Manifesto,” says AI models can now write code, produce documentation and tests, handle boilerplate, and contribute to architecture discussions. The author says some engineering work that once took substantial time may become less central as models take on more of it. These are the memo’s assessment of the technology and its implications, not independently measured results for Proton.
The author says Proton has so far been “almost completely stuck at phase 1” of AI adoption: using language models to speed up tasks within existing workflows. The memo argues the company should move beyond that approach, with engineers helping models work more autonomously and addressing recurring failures so the tools can perform better in future tasks. The source material supplied here cuts off after introducing this second point, so it does not show the rest of the memo’s phases or recommendations.
The author also says the memo is not an in-depth engineering document and does not detail security, reliability or infrastructure. It was written initially as an internal memo, the author says, both to set a direction for Proton and to persuade colleagues that their experience is needed as the company adopts AI. The publication does not announce a specific product, staffing change, deadline or completed rollout.
How AI Could Reshape Proton’s Engineering
The memo matters because it frames AI use as a proposed change to engineering roles and workflows, rather than just a new tool for individual developers. If Proton puts the approach into practice, engineers may spend more time defining tasks, supplying context, checking model-generated work and improving shared processes, and less time producing routine code by hand. The memo does not establish how quickly that shift will happen or how much it will change output.
There is also a direct connection to Proton’s public identity. The company sells privacy-focused services, making questions about how AI tools are used in development relevant to users concerned about data and security. But the manifesto, as provided, does not explain which models Proton will use, what information they can access, or what safeguards will govern their use. It should not be read as confirmation that customer data is being sent to AI services.
For employees, the author’s language signals that Proton expects its engineering teams to adapt to AI-assisted work. The memo also says human expertise remains necessary for judgment, accountability and spotting errors. That stated role for people sits alongside a push for more autonomous AI agents, leaving the practical balance between automation and human review open.
Products Worth Considering
Jackery Explorer 300 Portable Power Station with 40W Solar Panel
LG UltraGear 32GS60QC-B 32-inch Curved QHD Gaming Monitor (180Hz, 1ms, 1000R, AMD FreeSync, HDR10)
Bose QuietComfort Wireless Noise Cancelling Headphones, Twilight Blue
As an affiliate, we earn on qualifying purchases.
From Internal Memo to Public Manifesto
The author says the memo was written about a month before the blog post, though the supplied source does not identify the post’s date. Its stated purpose was to explain an AI adoption path Proton should follow and to address what the author viewed as shortcomings in the company’s organization. The memo was later published in full, according to the blog introduction.
The author places Proton’s decision within a broader change in software development, arguing that models have become capable enough to write useful code and assist with other engineering work. The memo also points to competitor investment as a reason Proton should respond. Those statements are the author’s rationale; the provided material contains no independent comparisons of Proton’s productivity, its competitors’ spending or the effects of AI adoption across the industry.
The headline supplied with the request characterizes Proton as doing the opposite of what users want, but the source text does not document a user request, survey, public response or specific decision that contradicts user feedback. The confirmed development in the material is the publication of an internal memo advocating wider AI use in engineering. Claims about users’ views or their reaction cannot be established from that source alone.
“Your job is to help the LLM write better code faster.”
— Proton’s memo author
The Missing Adoption Details
The supplied source does not include the full manifesto: it ends midway through the section describing why Proton has not made greater use of AI. It is consequently unclear what the memo’s later adoption phases involve, what specific changes Proton plans to make, or whether the company has approved a formal implementation plan.
There are no details here about model selection, data access, security review, human approval requirements or timelines. The author expressly says the memo does not cover security, reliability or infrastructure in depth. The material also does not provide productivity figures or evidence that AI has increased output at Proton.
Despite the user-focused framing in the supplied headline, the source does not show what Proton users have asked for or how they have responded to the manifesto. It also does not announce layoffs or connect the memo to a particular staffing decision. The author discusses job disruption in the software industry broadly, but that is not confirmation of a workforce change at Proton.
Proton’s Implementation Remains Open
The next concrete step depends on whether Proton turns the manifesto’s direction into specific policies and engineering practices. The supplied material does not name a rollout date or a follow-up announcement. Readers will need further information from Proton to know which teams will adopt more autonomous agents, what checks will apply to generated code and how the company will evaluate results.
Further detail would also be needed to assess the implications for privacy and reliability: which tools are used, what data they can process, how access is restricted, and who is accountable for reviewing their output. Until Proton publishes those details, the memo is best understood as a statement of intent about engineering work, not proof of a completed transformation or a change to Proton’s user-facing services.
Key Questions
What did Proton announce?
Proton published an internal engineering memo that calls for staff to use AI coding tools more extensively and to guide models as they take on more software development work.
Does the memo say Proton is replacing its engineers with AI?
No. The author says human expertise, judgment and accountability remain important. The memo does advocate more autonomous AI work, but the supplied source does not announce job cuts or a plan to replace engineers.
Does the manifesto explain how Proton will protect data?
Not in the material provided. The author says the memo is not an in-depth document on security, reliability or infrastructure. It does not specify the AI models, data access rules or safeguards Proton will use.
Did Proton act against what its users requested?
The supplied source does not document a specific user request or show user reactions. It supports reporting that Proton published a memo advocating broader AI use in engineering, but not a claim that this directly contradicts users’ stated preferences.
What happens next?
No timeline or implementation milestone is given in the supplied material. Further details from Proton would be needed to establish how the proposed changes will be applied and evaluated.
Source: proton.me
