Everyone Talks About Culture. Nobody Has Seen It. Cloud Engineers by Role, Second-Class Citizens by Treatment
Pros
Nothing for now. It was actually a great place before, at least according to people who were here then, but recently there's been an impressive commitment to micromanaging even the smallest details. Efficiency may have left the building, but oversight is thriving
Cons
What an extraordinary workplace experience. In over 14 months, management has demonstrated an unwavering commitment to ensuring employees remain focused on work by carefully eliminating distractions such as team outings, team dinners, employee engagement activities, recognition programs, or any visible investment in employee morale. The probation process deserves special recognition. Officially, it's six months. In practice, it appears to be an open-ended subscription service that renews automatically unless employees repeatedly follow up for updates. The company has successfully transformed a simple HR process into an exciting treasure hunt where employees search for information that should have been communicated in the first place. One of the most fascinating aspects of the organization is that it seems to operate as two entirely different companies sharing the same logo. One world is led by the CTO, and the other by an EVP. The contrast between these worlds is so remarkable that new employees may occasionally wonder if they accidentally joined two organizations at once. The development team, under the CTO, appears to enjoy the benefits of a highly evolved workplace culture, including extensive work-from-home flexibility and various other privileges. Meanwhile, teams such as Cloud and DevOps seem to live under a different constitution altogether, where even requesting a week of remote work can feel like a high-level diplomatic negotiation. It's truly impressive how company policies can adapt so dynamically depending on which department happens to be reading them. I've also learned a valuable leadership lesson here. Apparently, it is entirely possible for a CTO to be deeply involved with one department while having little to no interaction with entire teams such as Cloud and DevOps. If this is the future of organizational leadership, then this company is clearly ahead of its time. The leadership team's commitment to employee well-being is especially inspiring. The CEO regularly addresses employees during town halls, ensuring everyone receives a steady supply of motivational speeches, strategic visions, and promises of positive change. The execution part appears to be handled by a different department that has unfortunately not attended any of those meetings yet. Town halls have become a truly unique experience. Employees gather to hear about culture, growth, transparency, employee-first values, and exciting future plans. It's almost like watching a documentary about a company everyone wishes they worked for. The contrast between what is discussed on stage and what employees experience on a daily basis is so impressive that it deserves its own category in performance reviews. Another remarkable achievement is the company's ability to discuss employee wellness extensively without allowing it to interfere with actual employee wellness. In all my time here, I have seen plenty of presentations about culture and engagement, but very little evidence that those concepts successfully escaped the PowerPoint slides. The organization also maintains a healthy atmosphere of uncertainty through periodic layoffs, including members of the HR team itself. Nothing builds employee confidence quite like watching the people responsible for employee support suddenly disappear. Over time, the workplace has become increasingly political and toxic, with favoritism often appearing to carry more weight than fairness. Equal treatment across teams seems to function more as an inspirational slogan than an operational principle. The most impressive achievement, however, is the sense of unity. It is genuinely difficult to find another workplace where employees from so many different teams can agree on one thing. Regardless of department, title, or reporting structure, a significant number of people seem united by the common goal of updating their resumes and exploring opportunities elsewhere. For anyone considering joining, I would strongly recommend understanding which side of the organizational divide you're entering. If you're joining as a developer, your experience may be significantly different. If you're considering a Cloud or DevOps role, ask detailed questions about work culture, flexibility, management involvement, and growth opportunities before accepting an offer. The company has already mastered the art of treating employees differently. The next challenge is learning how to treat them equally.
