EU remote
Senior Software Engineer, Android (Contract)
About this role
The Wikimedia Foundation is looking for a Senior Software Engineer, Android to support the App Experience and App Growth teams within the Core Experiences engineering group. Our teams have a clear and ambitious goal: make our apps the destination for knowledge lovers and grow our active readership. Availability It’s important to state that we are a fully remote team at a global organisation. To ensure there are enough opportunities to communicate, this role needs at least four hours of your workday to occur between 15:00 UTC and 21:00 UTC.
You are responsible for: Delivery and enablement - Delivery of medium complexity initiatives from technical discovery through delivery. Breaks down initiatives into features, drive estimation and manage scope. Identifies risks early, and helps the team make pragmatic tradeoffs across quality, velocity, maintainability, and user impact. Implementation - Improving the mobile Wikipedia product experiences that serve a global, multilingual audience on Android.
Leads system design for medium-sized projects and can design and build accessible, adaptable, scalable components. Quality, testing and observability - Consistently builds software that is easy to test, observe and debug. Instruments features that enable deeper analysis by Product Analysts. Cross-functional collaboration - Partners with product managers, designers, analysts, and native app engineers to shape pragmatic solutions that balance user needs, technical constraints, platform expectations, and delivery timelines.
Prioritisation - Proactively identifies high-impact technical opportunities and risks across the engagement timeframe, works with the team to clarify priorities and sequencing. Actively keeps the team aligned on outcomes, capacity, and shared goals. Culture and standards - Complies with team standards in code review, technical design, testing, documentation, accessibility, observability, and decision-making - fostering transparency, empathy, and collaboration.
Operational Awareness - Plans work with awareness of downstream or upstream effects. Qualities that are important to us: Clear communicator - You can explain your ideas simply and adapt your communication to different audiences across engineering, product, and non-technical audiences in both synchronous and asynchronous channels. Autonomy - Operates with high autonomy in a team setting and cross-team settings. You own your work end-to-end and practice a culture of responsibility and follow-through.