|
|
|
|
|
by jlangenauer
1316 days ago
|
|
Twitter has around 190m daily active users. You're going to struggle to run something like that with an engineering team of 20-30 people (although WhatsApp did exactly that for many years), sure. But I don't see why an company and an application of that size couldn't be run by a company of, say, 1500 people, instead of 7000. 250 engineering staff, 250 doing moderation/support, 800 doing sales & account management and 100 in management and 100 doing sundry tasks. |
|
Let's do some napkin math here:
500 million tweets, let's say 10% are reported, and evenly distributed. That would make for reviewing 200,000 tweets per employee per day. That's 7 tweets that need to be moderated per second for a standard 8 hour day.
190m active users, .1% of which need support daily. On top of 7 tweets per second, that's just shy of three user support tickets per second that they need to manage as well.
And that's without weekends, holidays, sick days, etc.
EDIT: Let's go the other way with napkin math too.
Let's say each content moderator can review 6 tweets per minute.
50m tweets to be moderated at that velocity means you need around 136,000 man hours per day. For an 8 hour day, that's 17,000 employees. Too many.
So you make an ML algorithm that processes the reported tweets, but needs backup and spot checking on 10% of those. 1,700 content moderators (and a team dedicated to building/maintaining the ML report checking algorithm).
Now, about those support requests. Based on my experience from being a CSR for Amazon years ago, you'll probably want 2-3 minutes per support request, and that's if you're sending a form letter back. 1.9m requests at 20 per hour means some 95,000 man-hours per day, or 12k CSRs. Too many. Another ML algorithm (and team to maintain it) and we're down to 1,200 CSRs.
About 3 thousand employees plus their support structure, just to handle tweet reports and CSR requests.
Based on napkin math, 7,000 employees makes a lot of sense to me.