Interim CTO / Senior Technical Lead & Full Stack Support Volunteer

Volunteer Vacancy: CTO Office & Technical Delivery Team

20-Week Volunteer / Interim Technical Leadership Opportunity Supporting NESA-Africa, SCEF, EduAid-Africa and Related Digital Platforms

Organization: Santos Creations Educational Foundation / NESA-Africa

Location: Remote / Hybrid

Duration: 20 weeks

Time Commitment: 8–15 hours per week preferred

Role Type: Volunteer / Interim Technical Leadership / Senior Technical Support / Full Stack Support

Focus Areas: CTO Office support, technical leadership, full stack review, MVP readiness, codebase review, frontend/backend integration, DevOps, hosting, database readiness, QA, documentation and technical handover

About Santos Creations Educational Foundation

Santos Creations Educational Foundation is a Pan-African education-focused organization working to advance education, digital learning, advocacy, scholarships, school support, recognition, media engagement and sustainable community impact across Africa and the diaspora.

Our major platforms and initiatives include:

NESA-Africa;

EduAid-Africa;

Rebuild My School Africa;

SCEF Media;

NESA TV;

It’s In Me Radio;

Local Chapters;

My Career My Life;

Education Online Africa;

eLibrary Nigeria.

We are currently strengthening our digital platforms and technical delivery structure to support MVP readiness, codebase review, technical documentation, hosting stability, QA, dashboard planning and future platform expansion.

About the Opportunity

Santos Creations Educational Foundation is creating a stronger CTO Office & Technical Delivery Team to support the technical readiness of NESA-Africa, SCEF, EduAid-Africa and related platforms.

This opportunity is suitable for senior technical volunteers, full stack developers, technical leads, DevOps-aware developers, software architects, engineering managers, QA/release leads and civic-tech builders who can help review, stabilize, document and improve our existing MVP and future platform structure.

The NESA-Africa website was initially built using Lovable AI and related AI-assisted development tools. We now need experienced technical contributors who can help review what has been built, identify what should be kept, refactored, rebuilt, documented or improved, and guide the platform toward a stable MVP launch.

The backend may involve Contabo VPS or similar backend hosting, so experience with hosting, SSL, deployment, backups, monitoring, server access, environment setup and rollback planning is helpful.

This is not only an advisory role. The CTO Office should be able to provide technical leadership and, where necessary, directly support critical frontend, backend, API, database, DevOps, deployment or QA issues.

Why We Need a CTO Office

As our platforms grow, we need a stronger technical leadership structure that does not depend on only one person.

The CTO Office will help ensure that:

the MVP is properly reviewed before launch;

the Lovable AI-generated codebase is technically assessed;

frontend and backend integration is properly reviewed;

critical bugs are identified and prioritized;

technical contributors receive clear guidance;

hosting and deployment risks are understood;

database and data flow readiness are reviewed;

QA and release readiness are properly defined;

technical documentation and handover are created;

future modules such as voting, dashboards, local chapters, wallet/AGC, NRC and judges’ workflows are technically planned.

Our operating principle is:

No technical launch without review.

No code acceptance without evidence.

No deployment without rollback planning.

No MVP approval without must-fix and can-wait classification.

No technical dependency on one person alone.

Relationship With the Product Management Office

The CTO Office will work closely with the Product Management Office.

The Product Management Office will support:

task boards;

deadline tracking;

volunteer allocation;

blocker logs;

requirements documentation;

daily delivery coordination;

QA tracking;

leadership reporting.

The CTO Office will support:

technical review;

architecture guidance;

codebase review;

frontend/backend validation;

database and hosting review;

deployment readiness;

technical acceptance criteria;

technical risk classification;

technical documentation and handover.

The CTO Office is not expected to manage all daily PM administration.

The Product Management Office is not expected to make CTO-level technical decisions.

Both offices must work together to move the platform from scattered development into structured delivery.

Available CTO Office / Technical Volunteer Roles

Applicants may apply for one or more of the following roles:

1. Interim CTO / Senior Technical Lead Volunteer

This person provides senior technical leadership and helps guide MVP readiness.

Responsibilities include:

reviewing the existing NESA-Africa MVP;

reviewing the Lovable AI-generated codebase;

identifying what should be kept, refactored, rebuilt or documented;

defining technical acceptance criteria;

reviewing frontend/backend integration;

reviewing backend/API readiness;

reviewing database readiness;

reviewing hosting and deployment risks;

classifying must-fix versus can-wait issues;

guiding volunteer developers;

supporting technical documentation and handover;

advising on future voting, local chapters, wallet/AGC, dashboards, NRC and judges’ workflows.

1. Senior Full Stack Support Volunteer

This person supports frontend/backend integration and critical implementation issues.

Responsibilities include:

reviewing React / Next.js frontend structure;

reviewing Node.js / TypeScript backend structure where applicable;

checking API connections;

reviewing forms and data submission flows;

supporting nomination flow stability;

supporting certificate download flow review;

fixing or guiding fixes for critical bugs;

supporting developer handover notes;

helping prepare MVP technical readiness evidence.

1. Frontend Technical Support Volunteer

This person supports frontend review and improvement.

Responsibilities include:

reviewing page structure;

checking UI consistency;

checking mobile responsiveness;

reviewing routes and navigation;

testing buttons, links and forms;

reviewing Lovable AI frontend output;

identifying frontend bugs;

supporting accessibility and usability improvements;

working with QA and Product Office on frontend readiness.

1. Backend / API Support Volunteer

This person supports backend and API readiness.

Responsibilities include:

reviewing backend/API structure;

checking API routes and response patterns;

reviewing validation logic;

checking connection between frontend, backend and database;

supporting authentication or protected flow review where applicable;

documenting backend gaps;

supporting must-fix backend issue classification;

working with the CTO Office on technical acceptance criteria.

1. DevOps / Hosting Support Volunteer

This person supports hosting, deployment and server readiness.

Responsibilities include:

reviewing Contabo VPS or similar hosting setup;

checking SSL readiness;

reviewing deployment process;

checking backup planning;

reviewing monitoring needs;

supporting staging and production environment planning;

supporting rollback planning;

documenting hosting risks;

supporting secure access control recommendations.

1. Database / Data Flow Support Volunteer

This person supports database and data readiness.

Responsibilities include:

reviewing database structure where available;

checking data flow from forms to backend or dashboard;

supporting nominee data readiness;

reviewing Google Forms / Google Sheets pipeline where applicable;

supporting duplicate detection planning;

documenting required data fields;

supporting dashboard data requirements;

working with Product Office and CTO Office on data quality.

1. QA / Release Readiness Technical Volunteer

This person supports technical testing and release readiness.

Responsibilities include:

creating technical test cases;

testing frontend/backend flows;

tracking bugs;

checking nomination and certificate flows;

testing mobile and desktop behavior;

supporting regression testing;

preparing launch readiness checklists;

separating critical bugs from non-critical issues;

supporting release decision reports.

1. Technical Documentation & Handover Volunteer

This person supports technical documentation.

Responsibilities include:

documenting codebase structure;

documenting setup instructions;

documenting deployment process;

documenting APIs and technical dependencies;

documenting known issues;

documenting handover notes for future developers;

organizing technical decisions;

supporting CTO Office knowledge transfer.

Platforms You May Support

Volunteers may be assigned to one or more of the following platforms:

NESA-Africa;

Santos Creations Educational Foundation website;

EduAid-Africa;

Rebuild My School Africa;

SCEF Media;

NESA TV;

It’s In Me Radio;

Local Chapters;

My Career My Life;

Education Online Africa;

eLibrary Nigeria.

First 72-Hour Expectations

Selected CTO Office volunteers may be asked to support one or more of the following within their first 72 hours:

review the current MVP;

review the Lovable AI-generated codebase;

identify critical technical risks;

review frontend/backend/API gaps;

review nomination flow;

review certificate download flow;

review Contabo/backend hosting status;

review database readiness;

review dashboard/admin foundation;

prepare a critical bug list;

prepare technical acceptance criteria;

prepare must-fix versus can-wait recommendations;

document what should be kept, refactored, rebuilt or delayed.

Every volunteer will be assigned a clear role, supervisor, first task, deadline and evidence requirement.

Ideal Candidates

This opportunity is ideal for people who can:

provide senior technical judgment;

review existing codebases;

work with AI-generated or no-code-assisted code;

support frontend/backend integration;

guide volunteer developers;

review MVP readiness;

identify launch risks;

write technical documentation;

support deployment planning;

work with limited supervision;

communicate clearly with product, leadership and technical teams;

contribute to an education-focused social impact platform.

Preferred Skills

You do not need to have all the skills listed below. However, experience in any of these areas will be helpful:

React / Next.js;

Node.js / TypeScript;

API design and integration;

database structure and data validation;

dashboard/admin systems;

GitHub workflows;

Lovable AI or AI-generated codebases;

Bolt, Replit AI, Webflow, Framer, Bubble or similar tools;

Contabo VPS or similar hosting;

SSL, deployment, backups and monitoring;

QA and release readiness;

technical documentation;

software architecture;

technical leadership;

mentoring developers or volunteer teams.

Experience with voting systems, wallet/ledger logic, membership systems, local chapter portals, dashboards or nonprofit platforms is a plus.

Time Commitment

Preferred commitment: 8–15 hours per week

Duration: 20 weeks

Location: Remote / Hybrid

We welcome applicants who can contribute consistently, communicate clearly and support technical readiness within their available time.

What You Will Gain

Volunteers and technical contributors will gain practical experience in:

technical leadership;

CTO Office operations;

full stack platform review;

AI-generated codebase review;

frontend/backend integration;

DevOps and hosting readiness;

QA and release planning;

technical documentation;

nonprofit technology operations;

education advocacy platforms;

digital product readiness;

remote technical collaboration;

social impact project delivery.

Outstanding contributors may be considered for expanded responsibility, leadership roles, references, certificates of service, or future paid opportunities where available.

Application Questions

Please answer the following when applying:

1. Which CTO Office or Technical Delivery role are you applying for?
2. Have you served as a CTO, technical lead, engineering lead, senior full stack developer or DevOps lead before?
3. What frontend and backend technologies do you use?
4. Have you worked with React, Next.js, Node.js or TypeScript?
5. Have you reviewed AI-generated or no-code-assisted codebases before?
6. Have you worked with Lovable AI, Bolt, Replit AI, Webflow, Framer, Bubble or similar tools?
7. Have you worked with Contabo VPS or similar hosting?
8. Can you support frontend/backend integration and critical bug fixing?
9. How would you review whether the current MVP is launch-ready?
10. How would you separate must-fix issues from can-wait issues?
11. Can you help guide volunteer developers without owning daily PM administration?
12. Can you commit 8–15 hours per week for 20 weeks?
13. What would you do in your first 72 hours?
14. Do you have GitHub, LinkedIn, portfolio, technical documentation or platform examples to share?

How to Apply

Please submit:

a short introduction;

your preferred CTO Office or technical support role;

your technical leadership experience;

your full stack, DevOps, QA or documentation experience;

examples of platforms or teams you have supported;

your weekly availability;

tools and technologies you use confidently;

GitHub, LinkedIn, portfolio or references if available;

what you would do in your first 72 hours.

Short Summary for Idealist Preview

Santos Creations Educational Foundation is seeking volunteers and interim technical leaders to join its CTO Office & Technical Delivery Team for a 20-week opportunity supporting NESA-Africa, SCEF, EduAid-Africa and related digital platforms.

Volunteers will help review and improve the existing MVP, assess the Lovable AI-generated codebase, support frontend/backend integration, review hosting and database readiness, guide volunteer developers, support QA, document technical risks and prepare the platform for launch readiness.

This opportunity is ideal for senior full stack developers, CTOs, technical leads, software architects, DevOps-aware developers, QA/release leads and civic-tech builders who want to support a high-impact education platform across Africa.

Duration: 20 weeks

Time Commitment: 8–15 hours per week

Location: Remote / Hybrid

• Role Type: Volunteer / Interim Technical Leadership