Sign In

Mike Cvet

Distinguished Engineer

Mike Cvet is a highly experienced software engineer and technical leader with over 15 years of experience in the industry. He recently worked as a Distinguished Engineer at LinkedIn, focusing on developer experience and product platform strategy for the Product Engineering team.1 Prior to LinkedIn, Cvet held prominent positions at Twitter, including Distinguished Engineer and Group Tech Lead for Core Services.1

Some key highlights of Mike Cvet's career include:

  1. Currently working as a Software Engineer at Meta in Privacy Engineering since May 2024.1
  2. Served as a Distinguished Engineer at LinkedIn from September 2022 to December 2023.1
  3. Spent nearly a decade at Twitter in various roles, including Distinguished Engineer and Senior Staff Software Engineer.1
  4. Co-founded Thoora, a social media and news analytics company acquired by LinkedIn.1
  5. Worked at companies like Cue (acquired by Apple) and Red Hat.1

Cvet's expertise spans areas such as high-scale online serving systems, developer experience strategy, machine learning infrastructure, product safety, and anti-abuse systems.1 He has been involved in significant projects, including the introduction of ranking for Twitter's home timeline, which was considered one of the company's most successful product advancements.1

Throughout his career, Mike Cvet has demonstrated leadership in technical strategy, architecture design, and organizational improvement. He has contributed to defining engineering practices, career ladders, and promotion processes at companies like Twitter.1

Highlights

Dec 15 · linkedin

Building an effective strategy is hard for large engineering teams.

Leaders up and down the org chart often argue over whether the strategy development process should be “tops down” or “bottoms up”. The reality is that any strategy produced by just one side is likely to be ineffective, because both sides are accountable for completely different sets of responsibilities. A tops-down strategy is out of touch. A bottoms-up strategy is a science project. Sometimes, the strategy exists only in some leaders’ heads.

Hundreds or thousands of people need to know what they’re supposed to be doing; can we be certain they’re working on the right things?

Apr 23 · linkedin

Here’s an excerpt from my post “the value of code”: https://lnkd.in/gmXuzYUP

“”” Computer scientist Edsger Dijkstra once said, “If we wish to count lines of code, we should not regard them as ‘lines produced’ but as ‘lines spent’.”

Dijkstra is saying that code is an expenditure. It’s a cost in terms of the time taken to write, test, deploy and maintain, but also a cost in terms of the mind space its occupies in engineers’ brains - or the time it takes to understand it later, after its writers have moved on.

A few points make this more clear:

  • Is it possible that engineers produce lots of output but the team fails to meet its objectives? Yes.

  • Would your team prefer to meet its objectives but own half the code to do so? Yes.

  • Would we prefer to integrate a useful third-party library into the project, rather than trying to manually replicate its functionality in code? Yes.

  • Do software design principles like modularity, re-use and abstractions reduce the LOC necessary to meet an objective? Usually yes.

Code is powerful but ultimately a liability. The capabilities of the software is what brings value. “””

Related Questions

What are Mike Cvet's main responsibilities at Meta?
How did Mike Cvet contribute to Twitter's technical strategy?
What projects did Mike Cvet work on at LinkedIn?
What is Mike Cvet's background in software development?
How has Mike Cvet's career evolved over the years?
Mike Cvet
Mike Cvet, photo 1
Mike Cvet, photo 2
Add to my network

Location

United States