[Hiring] Senior Product Manager @Wikimedia Foundation

Role Description

Wikimedia is looking for an experienced product manager (contract) for the Mobile Apps team in our Product department. This is an opportunity to have a tremendous impact with one of the most beloved parts of the internet.

As a product manager with the Mobile Apps team (contract), you will work with engineers, designers, community members, other product managers, and our volunteer community to deliver on the reader strategy, focusing on improving the experience of our most committed app users.

This role will report to the Readers Group Product Manager.

This is a hands-on, individual contributor role. You will:

• Lead the product development process from ideation and discovery through scoping, requirements, release, and analysis.
• Scope work realistically, breaking ambitious ideas into MVPs and phased releases.
• Write clear, complete kick-off decks, requirements, and user stories in Phabricator.
• Set success metrics and define hypotheses and measurement plans.
• Experiment, release, and iterate intentionally to provide incremental value rapidly.
• Coordinate with the Group PM and collaborate with Communications, Marketing, and Legal functions.
• Collaborate with fellow apps product managers to stay aligned on strategic priorities.
• Own the information for your workstreams, documenting decisions, notes, and open questions.
• Produce and update community-facing documentation and gather feedback from volunteer communities.

Qualifications

• 3+ years of experience managing user-facing products in a mobile-first environment.
• A track record of personally scoping and shipping features end to end in large-scale consumer apps.
• A hands-on, self-directed working style.
• Strong organization and documentation habits.
• Experience working with cross-functional teams.
• Success making decisions in fast-changing and ambiguous situations.
• Experience working in an agile or iterative software development environment.
• Commitment to diversity, equity, and inclusion.
• Strong listening skills.
• Ability to clearly communicate plans and results to stakeholders.
• Bachelor’s degree or equivalent in relevant work experience.
• A desire to make meaningful contributions to knowledge equity, free culture, and open access.

Requirements

• Experience with a two-sided platform or marketplace product.
• Experience with personalization features.
• Comfort using AI prototyping or “vibe coding” tools.
• Experience with push notifications, re-engagement, or other mobile growth features.
• Proficiency with data, reporting, analytics, or A/B testing.
• Experience building products that support positive user habits, engagement, or ongoing value creation over time.
• Experience with fully remote, geographically distributed, and asynchronous teams.
• Experience working with communities, volunteers, or open source projects.
• Experience editing Wikipedia or contributing to other wiki projects.
• Experience with users in emerging markets.
• Fluency in a language other than English.

Expected Deliverables

• Fun space in mobile apps with initial features in partnership with Marketing.
• Based on an A/B/C test, scope and launch a new game in the app.
• Overhaul reader Notifications in the app.
• Scope and release a consent flow for donors to sync their status with their account.
• Bring support for semantic queries at scale to the apps and improve search discovery and functionality in the mobile app.
• Scope and release at least two new reader-focused features from our new feature backlog.
• Scope and release at least one donor retaining experiment in partnership with Fundraising.
• Scope and release at least one web feature integration that brings engaged readers from Wikipedia on mobile web to the apps.
• Kick off and narrative decks, measurement plans agreed with the data analyst, public project pages, Phabricator epics and user story tasks, as well as project close-out decks for every project you are responsible for.
• Weekly progress updates in Asana, regular MediaWiki project page updates, and a running log of product decisions made and why.
• Handoff documentation covering outcomes, learnings, open questions, and next steps for all work in progress.