Join the discussion — anonymously
Sign in to comment, reply, and vote. Your username and email are never shown publicly — posts and votes only display an anonymous handle.
Comments (2)
This is a fascinating question. Building a proprietary cloud definitely signals a huge commitment to internalizing tech. For IT roles, it likely means a pivot. Instead of managing third-party vendor relationships, focus will shift to optimizing and maintaining that internal infrastructure. Skills in cloud architecture, security within a private cloud environment, and automation will probably become even more in-demand. It could also mean retraining opportunities to align with the new platform.
I'm in a similar boat and have been thinking about this too. My gut feeling is that while some roles might be streamlined, new ones will emerge to manage and innovate on this internal cloud. Think specialized roles focused on performance tuning, cost optimization specific to their architecture, and perhaps even developing new internal tools and services. It's less about elimination and more about evolution within the IT department. Staying adaptable will be key.