Proton to re-interview staff on AI, with jobs at stake, 404 Media reports
THE SO WHAT
A security-focused company telling engineers to stop hand-writing code and re-interviewing staff on AI usage is a hard pivot toward “AI-native” productivity expectations. If you lead engineering, you need a stance on AI fluency as a job requirement — and a plan for how to measure it without burning trust.
READ THE SOURCE
MORE FROM THE WIRE
Applied AIHow Dylan Anderson became founding engineer at Adam
AI agents are moving from generic copilots into deep verticals like CAD—founding engineers here are effectively re-architecting how physical products get designed. If you build in tools or PLG SaaS, assume your power users will expect agentic workflows embedded directly into their core creation environments.
Applied AIHow Andrew HunzekerHesed became Employee #1 at 10x Science
Top consumer-scale engineers are defecting into AI-native scientific tooling—R&D is becoming a first-class software market, not just a cost center. If you sell into labs or pharma, expect your buyers to demand workflows that assume AI-first analysis rather than bolted-on dashboards.
Applied AIHow Max Friedlander became founding operations at Petrarch
Data supply for frontier labs is now a standalone business with "founding ops" roles doing high-stakes deals, not just scraping. If your product depends on proprietary or curated data, treat data acquisition and governance as a go-to-market function, not an afterthought.
Applied AIHow Yair Alon went from building Portrait Mode at Google to founding researcher at Poetiq
A decade of Google Research and DeepMind experience flowing into a startup focused on self-improving AI is a talent reallocation story—frontier research is decentralizing. If you're a smaller lab or applied team, assume the bar for "novel capability" is rising as ex-big-tech researchers spin out with their own agendas.