Pros
Nice buildings to work in. Team members are mostly lovely, although some are less competent than needed. The job is intentionally kept vague - which is both a pro and con. It is a pro as it can mean that you can develop in several different areas. It is a con as it means that an unfair workload can (and usually does) fall onto the community team. Good Annual Leave package offered.
Cons
Workload and tasks are vastly different between teams in different buildings. As a result, some community team members have significantly less to do than others. This results in some community team members being given far more responsibilities to do and being held to a far higher standard, while others have very little tasks and are praised far more for doing remedial tasks. This also means that some Community Associates are expected to do more in their buildings than even some of the market's most "senior" Community Leads who work in quiet buildings. This unfair division of workload across the markets is made worse by the fact that the significantly heavier workload is neither reflected in job title nor salary. Rather, you are expected to accept additional workloads as recognition for high performance. This would not be an issue if the additional workload came with sufficient financial compensation or viable progression opportunities. Further, and most importantly, all CAs that I've spoken to have complained that when interviewing they were promised a strong "progression culture" within WeWork that does not exist for those in community teams. We have been repeatedly told since passing probation that progression will only become available if someone leaves a more senior role as WeWork has decided to not expand their community teams. This refusal to expand team sizes comes amid a time where many of the markets have higher occupancy than ever with far smaller team sizes than pre-Covid. As such, the teams in the buildings are thinly stretched trying to deal with huge numbers of members and guests visiting daily, heavy account management and building operation workloads, regular event planning, continually touring prospective members, a constant flow of deliveries, answering support tickets and emails, driving NPS scores in the buildings, and training new staff (to name but a few of the tasks required). These overly stretched teams are then placed under even more strain by other teams who expect them to carry some of their workload (including sales, events, billing, etc). As community team members, we are happy to work cross-functionally but it is unfair how much of the work falls on us as we are the front-facing team for members and are usually forced into resolving issues or performing tasks that should lie with other teams.