Senior Software Engineer, Core Experiences (Contract)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes summary, responsibilities (list of duties), requirements, qualifications (maybe overlapping), skills, benefits (maybe none), pay (they gave pay range), schedule (they gave time zone requirement). Also "About The Wikimedia Foundation" could be "About the role"? Actually "About The Wikimedia Foundation" is about company, not role. The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content accordingly. We have: - Summary: description of role, contract length, focus. Could go under "About the role". Should not repeat job title. - Responsibilities: list of duties (Delivery and enablement, Frontend Implementation, Backend Implementation, Quality..., Cross-functional collaboration, Prioritization, Culture and standards, Operational Awareness). Those are bullet points. - Requirements: list of requirements (Bachelor's and 5-10+ years..., Strong professional experience..., Experience building responsive..., Experience designing..., Experience delivering..., Commitment to mission). Also "Additionally, We’d Love It If You Have ..." which are nice-to-have; could be under Skills or Qualifications? The instruction: Use sections for Qualifications, Skills. We need to decide where to put what. We have "Qualities That Are Important To Us" which are soft skills/attributes; could go under Skills or Qualifications? Probably Skills. We have "About The Wikimedia Foundation" which is company description; could be under "About the role"? Actually "About the role" is about the role, not company. But we have no separate heading for company; maybe we can put that under "About the role" as a brief description. Or we could omit because not required. The instruction: include a section ONLY when the posting has real, specific content for it. So we need to decide which sections have content. We have: - About the role: we have summary description. Yes. - Responsibilities: we have list. - Requirements: we have list of mandatory requirements. - Qualifications: maybe we can put education (Bachelor's, master's, or doctorate degree ...) and prior experience with MediaWiki, open source, remote team etc. Those are qualifications. - Skills: we have technical skills (JS/TS, Vue.js, PHP, responsive web, APIs, etc.) plus nice-to-have items (webview-wrapped experiences, native/cross-platform mobile apps, mobile games, data science/ML/AI, familiarity with Wikipedia/wikitext, agentic coding). Also the "Qualities That Are Important To Us" (clear communicator, autonomy, feedback, relationships, comfort with ambiguity, knowledge sharing, outcome-oriented). Those are skills/attributes. - Benefits: The posting does not list benefits like health insurance, etc. It mentions pay range and remote work, but not explicit benefits. So we should not include Benefits section unless there is real specific content. There's mention of remote-first, but that's more about work arrangement, not benefits. Could be considered under Schedule? Not exactly. Probably omit Benefits. - Pay: they gave anticipated annual pay range for US applicants: US$56.07 to US$87.13 (looks like hourly? Actually $56.07 to $87.13 per hour? It says annual pay range but numbers look like hourly. Anyway it's specific pay range. So we include Pay. - Schedule: they gave requirement: at least four hours of work day between 15:00 UTC and 21:00 UTC. That's schedule constraint. So include Schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Pay, Schedule. We must not repeat job title as heading. Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO paragraph, the remote-first organization paragraph, the salary details beyond pay range? Actually pay range is needed. The paragraph about salaries, pay range, location adjustments, etc. We need to keep the pay range info but can discard the rest? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep the pay range details, but we can maybe summarize? It says do not summarize away detail. So we need to keep the specifics: "The anticipated annual pay range of this position for applicants based within the United States is US$56.07 to US$87.13 with multiple individualized factors, including cost of living in the location, being the determinants of the offered pay. For applicants located outside of the US, the pay range will be adjusted to the country of hire. We neither ask for nor take into consideration the salary history of applicants. The compensation for a successful applicant will be based on their skills, experience and location." That's substantive. We should keep it. Also the list of US states and countries where they can hire is substantive? It's about hiring eligibility. Might be considered part of "About the role" or maybe "Qualifications"? It's not a requirement per se but eligibility. Could be included under "About the role" or maybe a separate section? Not in the list of headings. Could be placed under "About the role" as prose. We'll keep it. Also the accommodation contact info is boilerplate? It's about assistance for disability; could be considered part of application instructions, which we should remove. So we remove that. Also the "We are a fully remote team at a global organization. To ensure there are enough opportunities to communicate, this role needs at least four hours of your work day to occur between 15:00 UTC and 21:00 UTC." That's schedule; we keep. Now we need to structure. Let's extract content: Summary (About the role): "The Wikimedia Foundation is looking for a full stack Senior Software web Engineer contractor to join the App Growth team within the Core Experiences engineering on a 3-month full time contract. This is not a native iOS or Android role. It 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. You will build features that create natural handoffs between web and 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. Important: We are a fully remote team at a global organization. To ensure there are enough opportunities to communicate, this role needs at least four hours of your work day to occur between 15:00 UTC and 21:00 UTC." We can split: first part about role, second part about schedule (but schedule separate). We'll keep schedule separate. Responsibilities (list): - 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. - Frontend Implementation - Create mobile Wikipedia product experiences that serve a global, multilingual audience across web and app surfaces. You can design and build accessible, adaptable, scalable and reusable components. - Backend Implementation - Creating RESTful APIs, from schema and contract design through to monitoring and iteration, to serve simple but scalable data pipelines to mobile and web client experiences at scale. Ensures pipelines and APIs remain simple to consume, reliable to operate, and straightforward to evolve over time. - 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. - Prioritization - 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. We could keep each as a list item. Requirements (mandatory): - Bachelor's and 5-10+ years related professional experience with significant experience building production web applications and services. - Strong professional experience with JavaScript/TypeScript, JavaScript frameworks such as Vue.js, and backend languages such as PHP. - Experience building responsive or mobile-first web experiences, with attention to performance, accessibility, and usability. - Experience in designing and integrating with server-side APIs. - Experience delivering in a self-driven, lean environment. - Commitment to the Foundation's Mission and Values. Qualifications (education/experience): - Bachelor's, master's, or doctorate degree in computer science, management information systems, or STEM field (or equivalent certification). - Prior experience with MediaWiki or Wikimedia projects. - A history of open source contributions. - Experience working in a fully remote, distributed team. Skills (technical and soft): - Experience adding webview-wrapped experiences to existing native mobile apps (iOS or Android). - Experience in launching and maintaining native or cross-platform mobile applications (iOS or Android). - Experience building mobile games or other interactive mobile experiences. - Experience with data science, machine learning, and/or AI (e.g., familiarity with prompt engineering, Jupyter notebooks experience, etc.). - Familiarity with Wikipedia / wikitext / markdown editing or content management systems (e.g., MediaWiki, Drupal, WordPress). - Experience leveraging agentic coding to scale the work of small engineering teams. - 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. - Feedback - You give and receive feedback with curiosity and empathy. Helps others resolve misunderstandings productively. - Builds strong relationships - Proactively brings the right people into discussions, identifies process improvements. - Comfortable with ambiguity - You are comfortable with ambiguity and can collaborate to solve complex problems with pragmatic solutions. - Connects ideas and can regularly balance trade-offs across related domains to create well-rounded solutions. - Knowledge sharing - Strong knowledge-sharing practices, documents work for handover and consistently helps others understand and apply shared knowledge. You enjoy working with others to solve problems and are open to feedback. You inspire trust and progress through support, example, and thoughtful contributions. - Outcome-oriented - You prioritise work that delivers value to users and aligns with organizational goals. You balance ideal solutions with the constraints of legacy, user expectations and delivery needs. Pay: - The anticipated annual pay range of this position for applicants based within the United States is US$56.07 to US$87.13 with multiple individualized factors, including cost of living in the location, being the determinants of the offered pay. For applicants located outside of the US, the pay range will be adjusted to the country of hire. We neither ask for nor take into consideration the salary history of applicants. The compensation for a successful applicant will be based on their skills, experience and location. Schedule: - Important: We are a fully remote team at a global organization.