Kelly reviews

I initially loved working with Kelly on the Apple project as an Advisor and was excited about the opportunity to become a Team Lead. However, my experience drastically changed once I stepped into that role. As a Team Lead, I quickly realized that job security was tenuous at best. The most stable position on the Apple project is to be an Advisor, regardless of the financial incentives that might lure you into other roles. Unfortunately, I've observed that layoffs often begin at the top, impacting management positions significantly. If you’re in management and truly enjoy your job, be prepared: the excitement may not last long, as there seems to be a prevailing culture that discourages enthusiasm and meeting metrics. From a Team Lead's perspective, the training we receive underscores a troubling practice: we are instructed to scrutinize every call for flaws. The expectation is that we must identify issues, even if they are outside of the Advisor's control. If we can't find something wrong, we are directed to select another call that does have a deficiency. This relentless focus on criticism creates an environment where coaching feels more like a witch hunt than constructive feedback. Team Leads are also required to have one coaching with each Advisor every week for 30 minutes. We also need to have reviewed at least three calls in that week per Advisor. Advisor's work their shift and go home, if a call runs you over they get paid overtime. Not so for Team Lead's, if you're going to meet your goals & requirements you will easily work 60 to 80 hours a week no overtime pay; no exceptions. In summary, while my initial experience was positive, the realities of the Team Lead role have highlighted significant concerns about management practices and job security. I urge potential applicants to consider these factors carefully.