Former Meta engineering director testifies Zuckerberg allegedly prioritized growth over child safety on Facebook and Instagram

Arturo Béjar’s testimony introduces a direct allegation that Meta’s leadership, specifically Mark Zuckerberg, systematically favored growth and engagement over child safety on Facebook and Instagram. The claim suggests this was not an oversight but a cultural and operational priority. For engineers, this raises questions about how product decisions are weighted when safety features conflict with business metrics. If corroborated, it could force Meta to re-examine its internal governance and the autonomy of safety teams within the company.

The testimony arrives amid broader regulatory and public scrutiny of Meta’s handling of user safety, particularly for minors. While the material does not detail specific technical mechanisms, the implication is that safety features were either deprioritized in development cycles or overridden by engagement-driven algorithms. Engineers working on similar platforms may need to anticipate increased demands for auditability and explainability in their systems, especially where safety and engagement objectives collide.

The lack of corroborating feeds or additional context limits the immediate technical implications. However, the testimony’s framing, linking executive priorities to systemic outcomes, could accelerate calls for external oversight of platform algorithms. For engineers, this may translate into stricter compliance requirements or mandatory safety impact assessments for new features. The event also highlights the reputational and operational risks of misaligned incentives in large-scale systems.

The material does not specify whether Béjar’s claims are tied to documented incidents, internal communications, or specific product changes. Without such details, the testimony remains an allegation rather than a technical critique. Still, it serves as a reminder that engineering decisions are not neutral; they reflect the priorities set by leadership. Teams building user-facing platforms may need to proactively document safety trade-offs to mitigate future legal or regulatory exposure.