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.

Pros: Flexible working hours: 32-40 a week. Get to travel every once in a while. Learn as you go and grow.

Cons: Meetings. Meetings all the time! The Agile process employed is taken out of proportion, leading to meetings all the time. It's a slow environment, which is fine because the decision process to approve features is long, as they work with a lot of legacy code.

Pros: You get to work on famous, very nice products. Most of the work is done 'in the open'.

Cons: Sometimes endless discussions with community members on how to do things. These discussions can get quite violent. Somewhat intransparent communication between local Wikimedias which drive other projects. Wikidata, a product mainly developed by Wikimedia Germany for example, could be a great product with more international support.