You probably need some capability of working with a team. I'm going to assume you're a developer. Imagine working with a team of 5 to 10 developers. Plus a te

You probably need some capability of working with a team. I'm going to assume you're a developer. Imagine working with a team of 5 to 10 developers. Plus a team of QAs. Plus a team of Ops. Plus a team of DBAs. There's usually a process like working on code in a feature branch, passing it on for code review and then merging the feature branch into a development branch, where the QAs will deploy it to a staging server to check your changes (unless they deploy off the feature branch alone), and then eventually the development branch is merged to master for deploy to production. So basically people aren't merging code to master or development out of the blue. People aren't typically sshing into production servers and changing code on the fly. Developers probably don't even get any access. And so on. Anyways, not sure if you're already familiar with all that or if it gives you new insights into how working for a larger company might be different.