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 has published an internal engineering memo as an AI manifesto, arguing that software engineers should focus less on writing code and more on directing AI models and agents. The company says it has not yet moved beyond using AI to speed up existing tasks; the supplied text does not describe specific policy changes, deployment dates or workforce plans.
Proton has published an internal AI engineering memo arguing that its software teams must change how they work, with engineers increasingly guiding AI models rather than writing code themselves. The company says it has been stuck using large language models to speed up tasks inside existing workflows, and frames faster adoption as necessary to remain competitive and support its mission.
The memo, published on Proton’s website under the title “AI @ Proton, Engineering Manifesto,” was written by the company’s chief executive, according to the post. Proton says it was first circulated internally about a month before publication. The author describes it as a statement of direction, not a detailed engineering plan covering security, reliability or infrastructure.
The memo says that writing code manually is no longer the central task for software engineers. Instead, it argues, engineers should help models produce better code, identify problems the models cannot solve alone and improve shared resources such as repository-level context, prompts and tools. The author says human expertise still matters for judgment, checking model output and accountability.
Proton identifies three reasons it has not yet seen a major productivity change from AI. The excerpt supplied here details two: engineers have not fully changed their roles and habits, and Proton remains largely at what the memo calls phase one—using language models to speed up individual tasks within current workflows. The material ends as the author begins discussing the second point, so it does not provide the full account of the third reason or the complete proposed adoption path.
A Shift in Proton’s Engineering Roles
The memo matters because it describes a change not just in the tools Proton engineers use, but in what the company expects their work to involve. If implemented, the approach would put more emphasis on delegating work to AI, reviewing its output and improving the systems around it, while leaving people responsible for decisions and quality.
That direction could affect engineering workflows, training and how productivity is measured. Proton argues that models can reduce time spent on boilerplate, documentation and tests, and says organizations that do not adapt risk falling behind competitors. Those are the memo author’s judgments and forecasts, not evidence that Proton has already achieved higher output or that the proposed changes have produced measurable results.
The distinction matters to Proton’s users because engineering priorities can influence the pace and quality of product development. But the post does not announce a specific product change, new AI feature or change to Proton’s privacy practices. It is an organizational argument about how the company wants engineering to evolve.
Products Worth Considering
Logitech MX Mechanical Wireless Illuminated Keyboard, Tactile Quiet, Graphite
LG UltraGear 34GX90SA-W 34-inch WQHD Curved OLED Gaming Monitor
Samsung 27-inch Odyssey G5 QHD Gaming Monitor (G51F)
As an affiliate, we earn on qualifying purchases.
From Internal Memo to Public Manifesto
Proton presents the manifesto against a backdrop of rapid adoption of AI coding tools and concern about employment in technology. Its post says tech companies have laid off more than one million employees in recent years and says Microsoft offered 60,000 buyouts “just last week.” Those figures and the timing are claims in Proton’s post; the supplied material does not identify a data source, define the period behind the layoffs figure or provide a date for the Microsoft statement.
The author says the memo was intended both to outline an adoption path and to persuade Proton employees that they can shape the change. The post also acknowledges that AI industry activity includes superficial marketing, while arguing that competitors’ investments could influence Proton’s future business environment.
The manifesto does not claim that human expertise or engineering practices are obsolete. It says engineers retain experience, judgment and responsibility, and that maintainable architecture, documentation and testing still matter. The author suggests that practices could change if AI reduces the cost of writing and maintaining tests, but offers that as a possibility rather than a confirmed change to Proton’s standards.
“Your job is to help the LLM write better code faster.”
— Proton CEO, in the published manifesto
Implementation Details Are Missing
The published material supplied here does not set out specific targets, deadlines or measures for Proton’s AI adoption. It does not say which teams will change their workflows, what tools will be approved, or how the company will evaluate whether the shift improves productivity, reliability or security.
It is also unclear whether the manifesto changes staffing plans or job expectations in any formal way. The post discusses layoffs across the wider technology sector, but does not announce layoffs, buyouts or other workforce measures at Proton. Nor does the excerpt explain how the company will handle sensitive code or data when engineers use AI tools. The author explicitly says the memo is not a detailed treatment of security, reliability or infrastructure.
Because the source text ends partway through its discussion of the reasons Proton has not moved further with AI, the full set of diagnoses and recommendations cannot be confirmed from the material provided.
Proton’s Next Adoption Steps
Proton says its engineers need to move beyond using language models for isolated tasks and make AI work more autonomously, with less continuous human supervision. The memo points to shared repository context, prompts and reusable skills as ways to help models handle recurring work and improve after failures.
The post does not provide a timetable for that work or name a public milestone. The next concrete indication of progress would be further detail from Proton about how teams will adopt these practices, what safeguards will govern AI use, and how the company will report results. Until it does, the manifesto is best read as a statement of intended direction rather than evidence of a completed transformation.
Key Questions
What did Proton announce?
Proton published an internal engineering memo as an AI manifesto. It argues that engineers should increasingly direct AI models and agents instead of focusing mainly on writing code by hand.
Does the manifesto announce layoffs at Proton?
No. The post discusses job losses across the technology industry, but the supplied material does not announce layoffs, buyouts or staffing cuts at Proton.
What does Proton say is holding back its use of AI?
The excerpt describes engineers’ habits and workflows as one issue, and says Proton remains largely at phase one: using AI to speed up tasks within existing processes. The provided text does not include the full discussion or all the stated reasons.
Does the memo give a timeline or specific targets?
No timeline or measurable adoption target appears in the supplied text. Proton describes a direction for engineering work but does not specify deadlines, tools, or success metrics.
Does Proton say human engineers are no longer needed?
No. The manifesto says engineers still provide judgment, expertise and accountability, including checking model output and addressing problems AI cannot solve on its own.
Source: proton.me
