Project Manager, Experiential Education Framework

Position: Project Manager, JUMP! Experiential Education Framework

Location: Based in Bangkok with extensive travel to Singapore, Hong Kong, Budapest, Ghana, Zambia, Switzerland, Canada and elsewhere. 

Contract Term: 1 year with options to extend

Why is this Role/Position Important?

Education is at an inflection point. Artificial intelligence, automation, and rapid cultural shifts are dismantling the assumptions that have driven school design for decades. The schools that will flourish, and the students who will thrive, are those who learn by doing, by reflecting, by taking risks, and by connecting learning to the real world. Experiential education is no longer a nice-to-have. It is the answer.

JUMP! has spent 20+ years proving this on the ground. The Experiential Education Framework (EEF) is the vehicle through which JUMP! takes everything it knows about transformational learning, program design, safety, curriculum integration, and youth development, and puts it directly into the hands of schools. But right now, the EEF has a scalability gap. World-class work is being delivered every day across flagship schools and the broader partner network. That work generates extraordinary artifacts (trip leader trainings, crisis response frameworks, curriculum sequences, student leadership programs, risk management SOPs) but those artifacts live locally at the schools that built them. They are not captured as EEF assets. They are not branded. They are not standardized for reuse. They are not shared across the network. The institutional knowledge JUMP! generates each week is accumulating faster than it is being productized. 

The Project Manager of the EEF exists to close that gap. They are the connective tissue of the EEF. The person who connects with flagship schools, evaluates what is working, and translates lived practice into the standardized, school-agnostic framework that schools across the network can deploy. This is the person who ensures that when JUMP! does great work at one school, every other school in the network benefits. The person who makes the EEF feel like a real product rather than a series of bespoke engagements.

This is not a strategic visionary role. It is not a commercial role. It is the operational backbone that makes the strategic and commercial vision executable. The Project Manager works under the direction of the Director of the EEF and serves as a force multiplier, turning vision into shipped artifacts, replicable systems, and a coherent framework that compounds in value over time.

The core challenge this role solves: JUMP! has the practice. JUMP! has the partner schools. JUMP! has the framework on paper. What JUMP! does not yet have is the disciplined, full-time capacity to convert practice into product and connect that product across the network. Without this role, the EEF stays dependent on a small number of senior leaders carrying institutional knowledge in thei

RESPONSIBILITIES:

EEF Capture, Standardization & Resource Library

• Embed at flagship schools for extended periods to observe, document, and extract operational practice across all 8 units of the EEF.
• Build and maintain a comprehensive, EEF-branded resource library: training decks, SOPs, checklists, facilitation guides, dashboards, templates, and self-use tools across all 8 units.
• Apply consistent EEF branding, version control, and naming conventions across every artifact, ensuring schools and consultants always know which version is current and authoritative.
• Translate school-specific artifacts into school-agnostic EEF templates that can be deployed at any partner school with minor customization.
• Maintain the central EEF asset repository as the single source of truth for all framework materials.

Cross-School Integration & Network Connective Tissue

• Serve as the operational bridge across flagship and partner schools, ensuring that innovations at one school flow into the framework and reach other schools.
• Identify, document, and propagate best practices across the network so that strong practice at one school benefits all partner schools.
• Maintain a working map of what each school is doing across all 8 units, where the strongest practice lives, and where gaps exist that the EEF should fill.
• Support the operational delivery of the JUMP! EE Network: shared resource access, member communications, event coordination, and engagement rhythm
• Coordinate cross-school learning opportunities (shared trainings, joint working sessions, peer benchmarking) that make network membership tangibly valuable.
  

Engagement Operations & Delivery Support

• Develop and maintain standardized onboarding playbooks for new EEF partner schools so that engagements run on consistent rails rather than bespoke build.
• Lead trainings, workshops, and consulting engagements as they happen, both to support delivery and to produce the next-iteration version of every artifact used.
  
• Coordinate logistics, timelines, and deliverables across multiple concurrent EEF engagements to ensure nothing falls through the cracks.
• Build and maintain the operational tools that support EEF delivery: trip management dashboards, progress trackers, scorecard templates, and reporting structures.

Documentation, Knowledge Management & Operating Rhythm

• Establish and maintain documentation standards across the EEF team, ensuring that institutional knowledge is captured rather than lost to staff transitions.
• Maintain clear records of what has been built, what is in progress, and what is committed across all 8 units.
  
• Use Pipedrive and other CRM tools to track engagement progress, partner school activity, and resource deployment across the network.
• Build the operating rhythms that keep EEF productization work on track: weekly capture sprints, monthly artifact reviews, quarterly framework updates.

Team Support & Capacity Building

• Work closely with JUMP! team members across the organization to capture their practice and convert it into shared assets, building trust through reliability and follow-through.
• Contribute to the development of standard operating procedures for EEF consulting engagements.
  
• Support the Director of the EEF as a trusted operational partner, freeing the Director to focus on commercial leadership, strategic partnerships, and framework evolution.

DESIRED QUALIFICATIONS, SKILLS AND EXPERIENCE

• A Bachelor's or Master's Degree in education, experiential education, outdoor education, or a related field.
• Minimum of three years of experience operating inside schools as a teacher, program leader, expeditions coordinator, or experiential educator. 
• Demonstrated ability to build and maintain operational systems, templates, and documentation frameworks in complex, multi-stakeholder environments.
  Strong understanding of safety protocols, risk management principles, and SOPs in outdoor and experiential education settings.
• Experience working in or across international schools and comfort navigating the rhythms of school leadership culture.Willingness to travel extensively to flagship school sites across the network for multi-week embeds.
• Comfort with productivity and CRM tools (Pipedrive, Notion, Google Suite or equivalent).
• Excellent written communication and documentation skills. You treat documentation as a craft, not a chore.
• Proven capacity to manage multiple long-cycle workstreams across geographies without losing detail or momentum.
  

REPORTS TO: Director of Experiential Education

About the JUMP! Foundation:

The JUMP! Foundation is a non-profit social enterprise organization committed to inspiring, empowering, and engaging youth through innovative transformational learning programs. We offer a wide range of experiential education opportunities, including leadership activities, outdoor adventure trips, and customized programs for international schools and universities. Our vision is to make transformational learning accessible to all, and we support youth-focused development projects worldwide.

Questions for Application Video: 
1) What about this role gets you fired up and excited?

2) Walk us through a specific example where you took something that existed only in someone's head or in a one-off document and turned it into a reusable system or resource. What did you build, and how did you know it was good enough to share?

3) Describe a time you embedded in someone else's environment (a school, an organization, a team) and had to earn credibility quickly without formal authority. What did you do, and how did you know it was working?

4) This role sits underneath a Director who sets the vision, and your job is to make that vision executable. Tell us about a time you operated in that kind of relationship. What did you own, what did you escalate, and where did the boundaries sit?