Read Elon Musk’s Friday emails to Twitter engineers asking them to come to the office

Technology

In this article

The Twitter logo is displayed on the exterior of Twitter headquarters on October 26, 2022 in San Francisco, California.
Justin Sullivan | Getty Images

After Twitter told employees it would be closing its offices until Monday, new owner and CEO Elon Musk has called engineering staff into the San Francisco headquarters office, according to internal emails obtained by CNBC.

Late Thursday, Twitter sent out a companywide email saying its offices would be closed from Friday until Monday, and badge access would cut off during that temporary closure.

Then, in a pair of widely distributed emails sent at the start of business Friday, Musk called for “anyone who actually writes software” to report to Twitter’s headquarters by Friday afternoon. First, though, he asked them to send him a high-level report of the best code they have worked on in the last six months.

After the initial call for engineers to come into the office, he also sent a follow-up encouraging people to fly to San Francisco to present in person. He said, in one of his emails, he would be working late into the night at the company’s headquarters office Friday and again on Saturday morning.

Musk said the point of sharing all this code and meeting with him in the office would be to do “short, technical interviews” that would help him “better understand the Twitter tech stack.”

Musk said those authorized to work remotely could request to speak with him by video. But quixotically he also said, “Only those who cannot get to Twitter HQ or have a family emergency are excused.”

The mixed messages on returning to the office come after a wave of Twitter employees resigned Thursday.

Their new “Chief Twit,” as Musk humorously calls himself, had issued an ultimatum a day earlier telling them they would need to commit to his vision for Twitter 2.0, and agree to work “long hours at high intensity.”

Three employees who resigned Thursday told CNBC they still had access to some internal systems at Twitter on Friday morning.

One believed that so many people from Twitter’s human resources and IT teams had resigned or been laid off that it may take a long time for the company to figure out whose access to email, Slack and other systems should be switched off.

These people asked to remain unnamed, citing fear of professional repercussions.

Here are the emails sent from Elon Musk to employees at Twitter early on Friday (transcribed by CNBC) over the first few hours of the business day in San Francisco:

From: Elon Musk

To: Team

Subj. All Software Engineers

Date: Nov. 18, 2022 [time stamp removed]

Anyone who actually writes software, please report to the 10th floor at 2 p.m. today.

Before doing so, please email me a bullet point summary of what your code commits have achieved in the past 6 months, along with up to 10 screenshots of the most salient lines of code. 

Thanks,

Elon

From: Elon Musk

To: Team

Subj. All Software Engineers

Date: Nov. 18, 2022 [time stamp removed]

If you’re working remotely, please email the request below nonetheless and I will try to speak to you via video. Only those who cannot physically get to Twitter HQ or have a family emergency are excused.

These will be short, technical interviews that allow me to better understand the Twitter tech stack.

Thanks,

Elon

From: Elon Musk

To: Team at Twitter

Subj. All Software Engineers

Date: Nov. 18, 2022 [time stamp removed]

If possible, I would appreciate it if you could fly to SF to be present in person. I will be at Twitter HQ until midnight and then back again tomorrow morning.

Products You May Like

Articles You May Like

Researchers Unveil New Theory on the Formation of Jupiter-Mass Binary Objects
No ‘immediate’ plans to ban Musk giving Farage’s Reform UK large donations – government
Mufasa: The Lion King – six key things to know
Who will be the UFC champions on Dec. 31, 2025?
Usyk cements legacy as best heavyweight of his generation

Leave a Reply

Your email address will not be published. Required fields are marked *