I would assume that if this could have been automated, Twitter engineers would have done so by now and potentially open sourced a relevant solution. Having engineer bloat does not indicate overlooked engineering opportunities, and none of us knows the technical debt at that company.

I argue that this would have been automated already simply because it's a big opportunity for Productization, and thus a revenue stream, if it would work. A common argument that the engineers wouldn't want to automate because they would automate themselves out of a job is not one I've seen hold water in the real world. Engineers like to solve problems, and hundreds of engineers deciding not to automate is not plausible.

Any company as old as Twitter is also going to have a nasty codebase with old ass code that's held together with gum and tape. All that would need to be refactored, based on my experience, to cohere with a novel solution to automate what was previously not automated. This is a nightmare no company tackles except in trickles here and there.