Pros: Remote friendly. Nice colleagues (in engineering at least).

Cons: Limited support to staff. Far too many steps and processes to jump through before shipping a finished feature or project to production. If you want to move at a "quick" clip with your work, then it isn't for you.

Pros: Everyone here believes strongly in the mission. Many of the problems faced by the Wikimedia Foundation are unique; you don't feel like you are re-inventing the wheel. You get to work with amazing people and impact the lives of half a billion people a year.

Cons: Compensation is not competitive for the tech industry due to non-profit status. There is a very vocal community from the projects that often does not trust anything that the WMF does.

Pros: Awesome goal Very well known product Non-profit with a tech side Good life/work balance Open source, and community focused Ok salary Remote

Cons: Surprisingly, in the tech department, collaboration is extremely hard and painful, to the point of being avoided. Due to the lack of collaboration, all work is individualized: you do your work, don't touch anybody's. The same lack of collaboration, and a layered org/responsibilities, make any work that requires more than a layer extremely painful. That means that any meaningful work is either not done, or slow and painful, so there's an increasing pile of tech debt that nobody wants to tackle (and is encouraged not to). The focus on individual and hand-over-the-fence type of work also ends up with little project management knowledge in the org; one-person projects don't need it. This also creates a very damaging "us vs them" culture. Little learning opportunities. Limited progression opportunities. So, if you only want to do small things by yourself, it's a great place to be. If you want to do anything else, you will probably not last much.