SkySlope reviews

The Design organization at SkySlope is highly centralized around a single leader, which creates a culture of dependency rather than collaboration. Designers have little to no autonomy and are often treated as executors of leadership’s ideas instead of contributors to problem-solving. Every design-related conversation must include Design leadership, and meetings frequently involve micromanagement, public corrections, or lengthy “leadership lesson” discussions that feel performative rather than productive. The environment is tense and compliance-driven. Team members often seem afraid to speak up or ask questions. “Feedback is welcome” is said often, but any differing opinion is usually dismissed or reframed as a “growth opportunity” rather than genuine dialogue. Design critiques or team meetings sometimes turn into emotional or philosophical lectures (for example, about impostor syndrome or personal growth) instead of focusing on work quality or process improvement. The culture rewards agreement and visible admiration rather than thoughtful debate or diverse viewpoints. There is virtually zero cross-collaboration between designers and developers in the normal project workflow. Once Design leadership approves a design, it is considered “delivered.” Designers are expected to write the delivery tickets, defining implementation details without ever discussing technical constraints or feasibility with engineering. There are no quality assurance professionals, so designers also document test notes, that often fall to a backlog task that is never prioritized. Task definitions are often vague or improvised by leadership during sprint grooming based on personal opinions or offhand comments from previous meetings. The Figma files are disorganized and inconsistent with production. Spacing, components, and layouts vary widely, and the existing design system is outdated, poorly maintained, and lacks documentation. There is no Storybook or component library showing states or implementation guidance. Most applications are legacy and show clear signs of UI/UX debt. (I encourage you to go check the UI/UX of Skyslope's products and see for yourself). When these issues are brought up, leadership typically responds that one should “trust the process” before criticizing. Rather than being encouraged to improve things, designers are framed as not being team players or as resistant to leadership. Despite delivering high-quality, polished work, meeting every deadline, and receiving praise for the technical quality of my output, I was terminated after two months without prior notice or any opportunity to say goodbye to teammates. In my exit conversation, I was told that my work was “highly technical and perfect,” but that I “could not adapt to the leadership”, meaning I was expected to comply fully rather than contribute as a peer.