Wikimedia Foundation Interview Questions
& Process

So I had five interviews with Wikimedia Enterprise, and honestly, it was one of the worst experiences I've had. Communication was terrible. I always had to chase them for updates after pretty much every single step. The recruiter I was talking to changed four times, which was confusing and made it hard to get consistent info. It's weird to see so many recruiters involved but no one seems to be coordinating. The invite emails were super vague, just saying I'd have a one-hour call with two people, no idea what to expect or prepare for. After the last interview, total silence. I reached out, got nothing. Then I contacted a different recruiter who promised a decision by a certain date. That date came and went, it's been over two weeks since the final interview, and still no word. Had to follow up again just to get feedback. It felt really one-sided, like they were just exploring other options and didn't care about my time. The lack of communication shows no respect. It all just felt very disorganized internally.

First, we had a casual chat to see if we'd vibe and fit the team culture. Then, there was a technical session where we did some pair programming and worked on refactoring some existing code. Overall, it was a really pleasant experience for both parts.

The process was pretty organized and scheduling went smoothly. The recruiter knew their stuff, was upfront, and helpful. On the downside, it was a bit slow overall. I had an interview with a technical manager, not my actual hiring manager, and it was kinda rough. The questions were vague, and it felt like there was only one right answer they were looking for. If you didn't get their specific answer, it seemed like you were out. At one point, the interviewer couldn't even answer their own question and just went off on tangents instead of clarifying, which felt unprofessional. Honestly, it felt like there was some internal politics or power struggles, not a focus on teamwork.

So I applied for this QA Manager role that was weird because it wanted someone to manage both test engineers and technical writers/trainers. I have experience with both so I applied. The first step was a recruiter call where they mostly talked about Wikimedia's businesses. When we discussed compensation, it turned out the salary was much lower than advertised, about 30% less in my moderate cost of living area, and the benefits weren't great either, as expected from a non-profit. The recruiter mentioned the hiring process would take about two months and include a take-home project. Despite these drawbacks, I continued because I'm interested in Wikimedia. Round two, three weeks later, was with the hiring manager. They did most of the talking, describing how messy the company's processes and codebase are. They only asked a few questions, mostly checking if I was still interested. They seemed unenthusiastic about their own job, didn't ask about my leadership skills, and only briefly touched on my technical experience. When I asked about managing two different teams, they said they needed a manager for both but only had budget for one. They said they'd let me know about next steps in two weeks after talking to other candidates. Three weeks later, I received a rejection email saying they wanted someone with more open-source experience, despite that only coming up once in the interviews and me having that experience.