Senior Software Engineer (Fundraising) — Remote

We need to produce HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - About This Role: description of role: using engineering to support fundraising, delight donors, help fundraisers, record donations, tell donors about gifts, website dev, plumbing. - The Good News About This Position: bullet points: make a difference, work independently, work directly with lovely people from fundraising teams. - The Trade-offs: bullet points: only one other fundraising engineer, mostly solo, tech mixture boring and legacy, growing but role values depth and impact over fast title ladder. - The maybe good maybe bad news about the role depending on who you are: AI focus, if want bigger team, Python, complex tasks, look elsewhere. - This Role Is Right For You If: list of conditions: care about mission, agree with values, right to work in eligible countries, happy remote and meetings across time zones, happy to travel few weeks a year, fluent English, 4+ years engineering experience, happy working autonomously, comfortable on-call peak donation days, happy with boring/legacy tech, happy and skilled at working directly with non-engineers on messy tasks. - Compensation: details for US, UK, Kenya base salary, bonus, total comp, benefits stipend. Also note remote role salary benchmark for other countries. - Why work at GiveDirectly? bullet list: positive supportive team, opportunities for advancement, commitment to staff development, competitive salary including bonus, robust health benefits (varies by country), unlimited PTO, desk allowance and flexible work location. - About This Specific Hiring Process: take-home coding assignment, live coding, systems design, project deep dive + behavioral. Note possible adjustments. - Also location info: fully remote but must overlap with East Africa Time and US Eastern Time by at least 3 hours. Example. If Eastern US, being regularly available for 8AM meetings and some 7AM ones. Encouraged to set schedule that works as long as sufficient overlap. Note eligible countries list, visa sponsorship not available for US/UK. We need to map to sections: About the role (maybe combine About This Role and The Good News etc). Responsibilities: likely the duties: using engineering to support fundraising, delight donors, help fundraisers, record donations, tell donors about gifts, website dev, plumbing, on-call, working with non-engineers, etc. Requirements: maybe the eligibility: right to work in eligible countries, fluent English, 4+ years experience, etc. Qualifications: maybe similar to requirements? Could combine. Skills: maybe technical skills: Laravel, PHP, plain JS, HTML, CSS, Salesforce, Wordpress, SQL, wrangling CSV, AI usage? Also autonomous work, on-call, etc. Benefits: health benefits, unlimited PTO, desk allowance, flexible work location, benefits stipend. Pay: compensation details. Schedule: overlap requirement, remote, schedule flexibility, meeting times. We must not create sections with filler like "commensurate with experience". Ensure we only include sections with real content. We need to output only HTML fragment, using

for section headings,

• for lists,

  for prose. We must not include markdown fences. Let's craft. First, maybe a short paragraph for meta: location and overlap? Could be part of Schedule section. We need to ensure we don't repeat job title. Let's draft sections:

  About the role

  This role uses engineering to support fundraising: delighting donors, helping fundraisers, recording donations and getting them safely to recipients, and telling donors and the public what happens to their gifts. It involves some website development and a lot of plumbing work.

  Responsibilities

  • Delight donors and support fundraisers through engineering solutions.
  • Record donations and ensure they are safely started on their journey to recipients.
  • Communicate to donors and the public how gifts are used.
  • Perform website development tasks.
  • Maintain and integrate legacy systems (Laravel, PHP, plain JS, HTML/CSS, Salesforce, WordPress, CSV wrangling).
  • Work autonomously: define work, implement, test, launch, fix bugs, and drive progress daily.
  • Be on‑call during peak donation periods (Giving Tuesday and year‑end) to own incidents, communicate with fundraisers, and debug on legacy or others’ code when no other engineers are available.
  • Collaborate directly with non‑engineers on messy, poorly defined, rapidly changing, sometimes boring tasks.
  • Contribute to AI initiatives that help direct more funds to people in extreme poverty.

  Requirements

  • 4+ years of engineering experience.
  • Fluent in English.
  • Legally authorized to work in one of the countries GiveDirectly is able to hire from (check the current list of eligible countries).
  • Willing to work remotely with sufficient overlap (≥3 hours) between East Africa Time and US Eastern Time.
  • Happy to travel a few weeks per year to meet colleagues in the US, Europe, and Africa.
  • Comfortable being on‑call during peak donation days.
  • Comfortable using the organization's “boring and legacy” technology stack (Laravel, PHP, plain JS, HTML/CSS, Salesforce, WordPress, SQL, CSV wrangling) and eager to work with it.
  • Skilled at working directly with non‑engineers on ambiguous, rapidly changing tasks.

  Qualifications

  In addition to the requirements above, candidates should:

  • Align with GiveDirectly’s mission and values.
  • Enjoy working autonomously with few constraints.
  • Value depth and impact over a fast‑track title ladder.
  • Be excited about using AI where it increases cash transfers to people in extreme poverty.

  Skills

  • Laravel, PHP, plain JavaScript, HTML, CSS.
  • Experience with Salesforce, WordPress, SQL, and CSV file wrangling.
  • Ability to work independently and prioritize tasks.
  • Strong communication skills for interacting with donors, fundraisers, and non‑technical teammates.
  • On‑call incident response and debugging.
  • Comfort with AI‑assisted workflows aimed at increasing impact.

  Benefits

  • Competitive salary including performance‑based bonus.
  • Annual benefits stipend (varies by country: US $21,393, UK £2,760, Kenya $8,453; other locations receive a benchmark stipend during hiring).
  • Robust health benefits plan (details vary by country).
  • Unlimited PTO (encouraged to take).
  • Desk allowance and flexible work location.
  • Opportunities for professional growth and advancement.
  • Supportive, candid, analytical, non‑hierarchical culture.

  Pay

  • United States: Base salary $181,130; target bonus 15% (~$27,170, potential upside ~$31,789 in 2025); estimated total compensation at target $208,300+.
  • United Kingdom: Base salary £124,370; target bonus 15% (~£18,656, potential upside ~£21,827 in 2025); estimated total compensation at target £143,026+.
  • Kenya: Base salary $112,350; target bonus 15% (~$16,853, potential upside ~$19,717 in 2025); estimated total compensation at target $129,203+.
  • For remote hires outside the US, UK, or Kenya, GiveDirectly will provide an estimated salary benchmark for the candidate’s country during the hiring process.

  Schedule

  This role is fully remote but requires at least 3 hours of overlap between East Africa Time and US Eastern Time each day. For example, 6 PM EAT equals 11 AM ET in summer and 10 AM ET in winter. If you are based in the Eastern US, this typically means being regularly available for 8 AM meetings and some 7 AM ones. You are encouraged to set a schedule that works for you as long as the required overlap is maintained.

  We must ensure we didn't include any boilerplate like EEO, legal, etc. We omitted those. Also we omitted the "About This Specific Hiring Process" details? That is substantive; maybe we could include a section "Hiring Process". But the instruction says to use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It didn't forbid other headings, but says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we can use those headings; we could also add others if needed, but better to stick to those. The hiring process info is substantive; maybe we could fold into About the role or Responsibilities? But it's about interview steps, not job duties. Could be omitted? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep hiring process info somewhere. Could add a section "Hiring Process" with

  Hiring Process

  . The instruction didn't forbid other headings; it gave examples. So we can add. Similarly, location and visa info we already placed in Schedule and Requirements. We also have info about "We are unable to sponsor or take over sponsorship of employment Visas in the U.S. or U.K. at this time." That's substantive; we could put in Requirements or a separate note. Let's add a

  Additional Notes

  maybe. But better to incorporate into Requirements: mention visa sponsorship not available for US/UK. We also have info about "We know people have commitments like school drop-offs, so you’re encouraged to set a schedule that works for you -- as long as there’s sufficient overlap with the team." Already in Schedule. We have "Please note that we can only employ people in certain places at the moment, so it's worth checking our current list of eligible countries to see if yours is included. If you're based elsewhere, it's not an automatic no, but do flag it early with your recruiter." That's in Requirements. We have "We are unable to sponsor or take over sponsorship of employment Visas in the U.S. or U.K. at this time." Add to Requirements. We have "Our culture is candid, analytical, and non-hierarchical. We support high ownership and real professional growth." Could be in Benefits or About the role. We have "Curious about what it's really like to work here? Read our values and hear from the people who do. If they resonate, this could be a great fit!" Could be in About the role. We have "Why work at GiveDirectly?" we already captured in Benefits. We have "About This Specific Hiring Process" we need to include. We have "Working at GiveDirectly" EEO etc we