> Markdown version of [/jobs/ext/2280493-software-engineer-mediawiki-content-platform-team](https://www.wearedevelopers.com/jobs/ext/2280493-software-engineer-mediawiki-content-platform-team). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Software Engineer, MediaWiki Content Platform Team - **Company:** The Wikimedia Foundation, Inc - **Location:** San Francisco, CA, United States (Remote available) - **Experience:** Expert - **Salary:** $117,000.0 - $181,000.0 - **Contract:** Permanent contract - **Skills:** JavaScript (Programming Language), PHP (Programming Language), Application Programming Interfaces (APIs), HTML5, Compilers, Code Review, Content Analysis, Document Object Model, Drupal, MySQL, Node.Js, Open Source Technology, Open Access, Markdown, Software Engineering, Web Services, WordPress, Integration Tests, Information Technology, Wikimedia - **Published:** August 28, 2026 - **Apply:** https://job-boards.greenhouse.io/wikimedia/jobs/8158048 ## About the Role * 5+ years of related professional experience in software engineering * Experience with one or more of: parser generators, interpreters, language runtimes, compilers, or bringing a language feature through a product cycle * Demonstrated ability to own complex technical projects from problem definition through implementation and delivery, including making and communicating architectural decisions and navigating ambiguity * Experience designing and maintaining reliable, performant software components used by other teams, products, or large numbers of users * Strong engineering practices: you enjoy writing unit and integration tests, proactively addressing security and code review feedback, and balancing architectural tradeoffs * Ability to work effectively across team and organizational boundaries, identify and resolve technical dependencies, and bring projects to completion with limited direction * Experience mentoring other engineers and raising the technical quality of a team, through code reviews, design discussions, documentation, or direct mentorship Qualities that are important to us: * A desire to make meaningful contributions to knowledge equity, free culture, and open access * An emphasis on communicating clearly in both synchronous and asynchronous channels * Self motivated with an ability to navigate through ambiguity and bring a project to completion with limited direction Additionally, we'd love it if you have this: * Familiarity with the HTML5 spec and DOM manipulation * Expertise in Node.js and related technologies * Familiarity with Wikipedia/wikitext/markdown editing or content management systems (e.g., MediaWiki, Drupal, WordPress). We grow and care for MediaWiki and Wikimedia specific services. MediaWiki is an open source, PHP, MySQL, and JavaScript web application that powers Wikipedia and other Wikimedia Foundation websites. It has been incrementally developed for many years to become a richly featured wiki engine and the basis for hundreds of extensions and skins, and has a vibrant volunteer community. * A history of open source contribution * Bachelor's, master's, or doctorate degree in computer science, software engineering, or other STEM field (or equivalent certification) ## Description The Wikimedia Foundation is looking for a software engineer to join our team, reporting to engineering management. As a software engineer, you will be responsible for engineering software that supports our product user experiences. In this role, you will work in a fully-remote environment (with occasional travel for team, department, or organization events), where we value teamwork and a consensus-oriented approach. You get to write open source code for collaborative experiences supporting well over half a billion pages accessed per day, and you get to do it at a place that believes we're all more successful when everyone has a good work-life balance. On the Content Platform team, we work to support and evolve all things wikitext, the markup language behind Wikipedia. We aim to make wikitext easier to write, faster to parse, and less error-prone for humans. We also strive to support editing and content analysis tools with structured representations. We also maintain the web services associated with content rendering and transformation. In this role, you will work in a mostly-remote environment. To ensure there are enough opportunities to communicate, the preferred timezone for this candidate will be GMT-4 to GMT+2. You are responsible for: * Designing and delivering improvements to Wikipedia's wikitext processing infrastructure, balancing user experience, performance, backwards compatibility, and maintainability * Iterating on new features through collaboration with fellow engineers, product managers, designers, client teams, and community members * Writing PHP and JavaScript which supports hundreds of world languages * Creating and maintaining internet APIs with server scripting languages * Instrumenting components to monitor feature and quality characteristics * Leveraging caching and persistence technologies ## Related Videos - [Five things in tech that matter and we have to make work](https://www.wearedevelopers.com/videos/1403-five-things-in-tech-that-matter-and-we-have-to-make-work) - [Decoupling 101 - Why decouple, when not to, progressive decoupling and success stories in decoupling](https://www.wearedevelopers.com/videos/266-decoupling-101-why-decouple-when-not-to-progressive-decoupling-and-success-stories-in-decoupling) - [MySQL Protocol Features You Should Be Aware Of](https://www.wearedevelopers.com/videos/100267-mysql-protocol-features-you-should-be-aware-of) - [The Resilience of the World Wide Web](https://www.wearedevelopers.com/videos/1281-the-resilience-of-the-world-wide-web) - [Coding for Good: Achieving social change with an app](https://www.wearedevelopers.com/videos/1645-coding-for-good-achieving-social-change-with-an-app) - [The Pragmatic Architect: Balancing Necessity vs. Sufficiency in React Systems](https://www.wearedevelopers.com/videos/2101-the-pragmatic-architect-balancing-necessity-vs-sufficiency-in-react-systems) ## Related Articles - [A call for Guest Writers for the WeAreDevelopers Magazine](https://www.wearedevelopers.com/magazine/648-a-call-for-guest-writers-for-the-wearedevelopers-magazine) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 129 - Now that's what I call private data!](https://www.wearedevelopers.com/magazine/468-dev-digest-129-now-that-s-what-i-call-private-data) - [Dev Digest 131 - AI'm not sure about OSS](https://www.wearedevelopers.com/magazine/472-dev-digest-131-ai-m-not-sure-about-oss) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [What is Software Engineering?](https://www.wearedevelopers.com/magazine/289-what-is-software-engineering)