Job Opportunities API

Software Engineer III, Core Experiences The Wikimedia Foundation is looking for two Software Engineer III’s to join the App Growth and Editing Engineering teams within the Core Experiences engineering group. App Growth The App Growth team has a clear and ambitious goal: make the apps the destination for knowledge lovers and grow our active readership. As a web full stack mid-career Software Engineer III supporting the Mobile Apps teams you will build features that create natural handoffs from the web to the app and landing users in exactly the right place — for example, prompting a reader to try a personalized reading list in the app, creating a game that is integrated within the apps as a webview; or when someone tries to edit there is a smooth hand off to the web editing experience. This is not a native iOS or Android role. The role is focused on web-first product experiences, APIs, and platform integrations that can be reused across mobile web and native app surfaces; to help us scale features across platforms and create compelling features that deepen reader engagement and increase user retention.  To ensure there are enough opportunities to communicate, this role with the App Growth team needs at least four hours of your workday to occur between 14:00 UTC and 21:00 UTC. Reader Growth The Reader Growth team focuses on new ways of learning and engagement. We aim to invest in creating innovative experiences that leverage new technologies and formats. This includes tools and features that enable users to browse and discover content more intuitively, contextualize and frame knowledge in novel ways, and engage with visual, audio, and other multimedia formats. To ensure there are enough opportunities to communicate, this role with the Reader Growth team needs at least four hours of your workday to occur between UTC -8 through UTC -3. You are responsible for: Delivery and enablement - Supports delivery of initiatives. Breaks down complex features into tasks, anticipates risks and collaborates to resolve blockers. Implementation  - Can successfully build moderately complex features and components with minimal support and suggests areas for architectural improvements.  Production support - Takes ownership of bug fixes and production problems and communicates in a clear and timely way about impact and resolution. Quality, testing and observability - Designs and improves features with observability and testing as a core consideration. Instruments features that enable deeper analysis by Product Analysts. Contributes to healthier testing and software quality practices.  Cross-functional collaboration - Supports team alignment by asking clarifying questions, reinforcing agreements, and coordinating their work with cross-functional partners. Facilitates team ceremonies.  Prioritisation - Contributes meaningfully to planning. Helps scope work. Identifies risks across multiple sprints. Adapts as priorities shift. Culture and standards - Participates in code reviews, design discussions, and technical planning; shares knowledge proactively; and helps improve team development workflows. Operational Awareness -Thinks through how code affects usage and trust. Contributes to onboarding, documentation, and hiring efforts at the team level. Qualities that are important to us: Continuous Learning - You adapt to ambiguity with desire to learn and discover by self-directing your learning in depth and breadth. You encourage and support learning in others. You proactively share knowledge to make it easier for others to contribute. Autonomy - You work autonomously on most tasks, whilst timely checking in with teammates and sharing workload when blocked.You balance contributing and receiving support within the team. Feedback - You share and receive thoughtful, actionable feedback with peers — both constructive and positive. Collaboration - You