I did this as my first job out of college and then within the core dev team at a large corporation serving multiple brands. You definitely see patterns and can

I did this as my first job out of college and then within the core dev team at a large corporation serving multiple brands. You definitely see patterns and can help identify problems inside developers and managers do not see or dare admit. However you can also be seen as a warm body churning billable hours paid to the company at 4x your salary until you burn out. The lack of ownership of outcomes also means a lot of the real valuable lessons you get after your hard work are lost to you. It is however great for engineering roles where you are implementing tech the core team is new to. If you are an open source contributor or a specialist in a niche architecture, consulting would be a great gig, just make sure you make it a point to learn about the outcomes or decisions that come out to your work.