Pros
If you like working remote 100% of the time, this is a great fit; most of the quality engineering team is distributed around the world and remote teaming is required. Solid benefits offerings and compensation. Most folks are engaged and highly opinionated about technology, sometimes ad-nauseum. This level of passion is a good thing for a company that is focused on technology and collaboration. The variety of technologies and learning opportunities available mean that you'll have plenty of chances to brush up on the latest Red Hat sponsored open-source technologies. If you like to learn and grow, this is a good place to be.
Cons
The remote work aspect is an impediment to collaboration between development and quality engineering; expect things to move much more slowly than an environment with co-located team members. Sometimes quality engineering work can feel like a "rubber stamping" charade at this company. Heavy emphasis on correspondence via e-mail. Conversations and decisions that would be made more effectively via a real-time discussion are often taken care of via e-mail or online chat. There is an emphasis on being receptive to feedback, but this openness doesn't always extend to taking action, even if the benefits are obvious. Sometimes feedback is simply passively ignored. Some things can be changed. Some can't because of inertia. For an open source company, the source code for test automation is strangely kept private. This is reflective of the internal structure of the company - quality engineering is not formally included in the engineering part of the organization.