Meta infrastructure head Janardhan to leave, succeeded by Brown
Summarised from 2 outlets · Updated 12 Nov, 01:08 · Archive
Santosh Janardhan, Meta's head of infrastructure since 2009, will leave in 2027 and be replaced by former AWS executive David Brown.
Santosh Janardhan, Meta's head of infrastructure and co-head of engineering, will leave the company in 2027 after 18 years with the firm. He will be replaced by David Brown, a former Amazon Web Services senior vice president who joined Meta in July. Janardhan announced his departure in an internal memo, saying it was time to 'pass the baton' to Brown.
Brown will lead Meta's infrastructure efforts and serve as chief technical officer of Meta Compute, a company initiative to scale data center investments and AI capabilities. The move reflects CEO Mark Zuckerberg's strategy to expand infrastructure operations under newer leadership. Janardhan will remain in an advisory role and support the transition through the first quarter of 2027.
Meta's infrastructure investments have accelerated as the company competes in the AI race. The company projects full-year capital expenditure of between $135 billion and $145 billion. Earlier this year, Janardhan was tasked with leading Meta Compute, the initiative overseeing the company's data center strategy.
How it is being reported
- Meta is losing its longtime head of infrastructureSantosh Janardhan, who originally joined the company in 2009, will be stepping down from his role.TechCrunch · 11 Nov, 20:12
- Meta head of infrastructure will leave and be succeeded by former AWS cloud execMeta's head of infrastructure and co-head of engineering Santosh Janardhan will leave in 2027, with former AWS senior vice president David Brown taking over.CNBC · 11 Nov, 18:10
In this story: Meta · Santosh Janardhan · David Brown · Mark Zuckerberg · Amazon Web Services · Dina Powell McCormick
This summary was written by AI from the headlines and standfirsts above, and states as fact only what at least two outlets report. How we use AI · Report a problem · Corrections log
Comments (0)