One thing about being an engineer there was that you did actually own the product end-to-end. I remember taking systems from development to production without all the bullshit you normally encounter at large corporations. I would put something into production and my boss (the CTO) would leisurely say "Oh yeah, contact so-and-so in ops to have them secure the server." I would do that, and I didn't get a freak-out like you'd experience in more straight-laced companies: "YOU PUT THIS IN PRODUCTION WITHOUT FILLING OUT ALL THE REQUIRED JIRA TICKETS AND APPROVAL FROM 3 LAYERS OF MANAGEMENT?!?! WE'RE GONNA HAVE TO TAKE THIS DOWN AND HAVE A MEETING!" Nope, a dude in ops, who was usually stoned, would log in, add all the necessary protections and even redeploy the whole stack if he had to. No griping.
One thing about it was that you'd have to be okay with some unscrupulous/unethical practices. Copyright infringement is par for the course in that industry. Studios/companies stealing others' content is unavoidable (and encouraged).
I remember when I wrote a tube site and I was given a list of other tube sites to rip content from. For that particular project the product manager (who was also a high-ranking exec) strongly emphasized two things: every action had to be trackable, and it was a necessary requirement that handling DMCA take-down notices had to be a very streamlined and automated process.
Why? They would have people monitor which videos were heavily viewed and which were taken down frequently. If a particular studio's content generated lots of traffic but were frequently taken down, the sales/ad guys would contact that studio to make a deal. If no deal was struck, then an "anonymous user" would reupload the content to the site; starting the cycle again. Eventually that would wear down the studio into cutting a rev-sharing deal. Sometimes the company would buy the studio outright, if it made enough sense.