GiveDirectly [Private] - Product Associate / Product Manager, Training & Enablement

• Build the training materials that make new designs usable in the field • e.g., turning new survey designs, program changes, and Salesforce releases into practical training decks, job aids, quick-reference sheets, and step-by-step guides — written for someone who will use them on a tablet in the field, not read them at a desk • Write internal communications pitched to the level of the reader • e.g., taking a single change and producing the version each audience actually needs: the why and the risk for a Country Director; the timeline, staffing and cost implications for a Program Director; what changes about supervision and quality checks for a Field Manager or Assistant Field Manager; and exactly what to do differently tomorrow for a Field Officer — deciding what each group does not need to know is as much of the job as deciding what they do • Deliver training live, and record it when live doesn't scale • e.g., running training sessions with country teams before a rollout, in person or remotely; recording screen-capture demo videos of new builds and flows so teams can refresh without waiting for a session; and building a library that new staff can be pointed to rather than re-trained from scratch • Own release notes and change documentation • e.g., writing clear release notes as changes ship to the common Salesforce build, so country teams understand what changed, why, and what they need to do — and keeping documentation current rather than letting it drift from what the system actually does • Work across English, Portuguese and French • e.g., producing or adapting materials so Mozambique and DRC teams receive them in a usable language on the same timeline as everyone else, and managing translation support where your own languages don't reach • Be a useful pair of hands to a small, fast-moving product team • e.g., ad-hoc support across the Program Design team — pulling together a briefing, cleaning up a deck before a leadership check-in, taking notes and turning them into actions, chasing an open item across countries. Some of this will be unglamorous. It is also how you will learn the whole system faster than anyone else on the team • Close the loop from the field back to design • e.g., noticing when the same question keeps coming up in training, when a design cannot be explained simply because it isn't simple, or when field teams have quietly worked around a change — and bringing that back to the people who own the design • So the scope is unambiguous, here is what we expect the first three months to look like: • Days 0–30: Get oriented on the 2027 common Salesforce build and the countries moving onto it first. Review the training and documentation that exists today and give us an honest read on what's working and what isn't — you will have a sharper view of this than we do. • Days 30–60: Produce the full enablement package for one country's rollout: training materials, a live session delivered, at least one demo video, release notes, and the layered internal comms from Country Director to Field Officer. This becomes the template for everything after it. • Days 60–90: Adapt that package for a second and third country, including at least one Portuguese- or French-speaking market. Establish a simple intake and prioritization method for training requests, so the queue is visible rather than negotiated ad hoc. • What success looks like: • Every rollout onto the common Salesforce build ships with training and release notes as standard, rather than as an afterthought • A demo video and materials library that country teams actually use, evidenced by repeat access rather than one-off downloads • Materials reaching Portuguese- or French-speaking teams on the same timeline as English-speaking ones • Fewer repeated questions from field teams post-launch — measured however crudely, but measured • A reusable enablement template that any new country rollout or 2028 pilot can be plugged into in days • Documentation that stays current with the system, with a maintenance rhythm rather than periodic rewrites • A track record of catching unexplainable designs before they reach the field, and of the design being changed as a result • Trusted enough by country leadership that they come to you directly when a change needs explaining