Develop RTIQA: Comprehensive Global EdTech Platform

Build & Deliver RTIQA v1 — Global Multi-Tenant EdTech Platform
Read Before Applying
We are seeking a highly experienced Senior Full-Stack Engineer, Technical Lead, or capable engineering team to take ownership of RTIQA and deliver RTIQA v1 as a complete, functional, scalable, production-ready educational platform.
This is NOT a small feature task, UI redesign, prototype, or demo. The selected freelancer will be responsible for delivering the complete scope described below.
Review the public repositories before applying:
Current implementation:
https://github.com/rtiqa/rtiqa-website.git⁠�
Product vision and architecture:
https://github.com/rtiqa/rtiqa.git⁠�
AI / technical exploration:
https://github.com/rtiqa/rtiqa-ai.git⁠�
After review, provide your technical recommendation: continue, refactor, preserve valuable components and rebuild weak ones, consolidate repositories, or rebuild from scratch if justified.
The engineering approach is open. The required final product scope is fixed.
Generic copy-paste proposals that show no understanding of RTIQA or the repositories will not be considered.
PROJECT VISION
RTIQA is a global, scalable, multi-tenant EdTech SaaS platform combining:
School Management System (SIS)
Learning Management System (LMS)
Student Information Management
Parent Engagement
Assessments and Academic Records
Certificates and Verification
Notifications and Communication
AI-powered educational tools
The architecture must support future growth toward thousands of institutions and millions of users without requiring a complete rewrite.
REQUIRED RTIQA v1 SCOPE
1. Platform, Multi-Tenancy & Security
Build a secure multi-tenant SaaS platform supporting multiple independent schools with strong tenant data isolation, platform and school administration, scalable database/API architecture, authentication, authorization and role-based access control.
Core roles:
Platform Administrator
School Administrator
Academic Administrator
Teacher
Student
Parent / Guardian
Users must only access authorized data and functionality.
2. Arabic, English & Internationalization
RTIQA must support Arabic (RTL) and English (LTR) from day one, including language selection and an architecture ready for future languages, time zones, date formats and localization.
3. Institution & Academic Management
Schools must manage institution profiles, academic years, terms/semesters, grades, classes, sections, subjects, academic structures and teacher assignments.
The data model must remain flexible for different educational systems.
4. Student Management
Complete student workflows including registration, profiles, enrollment, class assignment, academic information/history, promotion between levels and parent/guardian relationships.
Student data must integrate with attendance, learning, assessments, grades, certificates and parent access.
5. Teacher Workspace
Teachers must manage assigned classes and subjects, students, lessons, learning materials, attendance, assignments, assessments, grading and AI educational tools.
6. Student Portal
Students must access a functional dashboard with courses, lessons, learning materials, assignments/submissions, assessments/exams, results, grades, attendance, certificates, notifications and AI learning assistance.
7. Parent / Guardian Portal
Parents are required in RTIQA v1 and must support multiple children, with secure access to attendance, absences, grades, performance, assignments, assessment results, announcements, notifications and certificates.
8. Attendance
Support present, absent and late status, daily/class attendance, student history and reports, with notification integration where appropriate.
9. Learning Management
Manage courses, units, lessons, learning materials, documents/files, educational media, course structure, student access and learning progress where applicable.
10. Assignments
Complete workflow:
Create → assign → deadline → student submission → teacher review → feedback → grade.
11. Assessments & Exams
Support question banks, multiple choice, true/false and short-answer questions, online/timed assessments, automatic/manual grading, results and academic record integration.
12. Grades & Academic Records
Support grade entry, assessment results, academic performance, progress tracking, report cards and academic history, with flexibility for future grading systems.
13. Certificates & Verification
Required in v1:
Certificate templates
Completion/achievement certificates
Institution branding
Unique certificate IDs
PDF generation
QR code
Public verification page
Certificates must be verifiable digital records, not merely PDFs.
14. Announcements & Notifications
Support targeted announcements for all users, teachers, students, parents or specific classes/groups.
Notification foundation must include in-app and email notifications, with an architecture ready for Push/SMS integration.
15. Dashboards, Reports & Export
Role-based dashboards and useful reports covering school activity, students, attendance, academic performance, classes and teacher activity, with export where appropriate.
16. Practical AI Features
AI must provide real educational value, not simply embed a generic chatbot.
Teachers: lesson planning, quiz/question generation, assignment generation and content summaries.
Students: lesson explanations, simplified explanations, practice questions and revision assistance.
AI architecture must consider security, permissions, tenant isolation, cost control, model-provider flexibility and future RAG/knowledge-base integration.
17. Search, Mobile & Connectivity
Provide search for relevant entities/content including students, teachers, courses and educational materials.
The platform must work well on desktop, tablet and mobile browsers.
Provide a practical foundation for unreliable internet where appropriate, including PWA capabilities, local caching, offline access to suitable content, offline action handling, synchronization architecture and conflict-handling strategy.
Avoid unnecessary complexity while establishing a real foundation for low-connectivity environments.
ENGINEERING & PRODUCTION REQUIREMENTS
The project is not complete based only on visible screens.
Final delivery must include:
Clean, maintainable and properly structured code
Clear documented architecture and technical decisions
Proper database design and migrations
API documentation where applicable
Secure authentication and authorization
Strong tenant isolation
Input validation and secure secrets management
Error handling and critical workflow testing
Reliable background processing where applicable
Performance optimization
Environment configuration
CI/CD
Staging and production deployment
Logging and monitoring
Backup and recovery strategy
Documentation sufficient for future maintenance
SCALABILITY
RTIQA must not be designed only for one small school.
The architecture must be capable of evolving toward thousands of institutions, millions of users, high concurrent activity, database growth, scalable APIs, caching, background processing, scalable file storage and observability.
Do not introduce unnecessary microservices or over-engineering.
The goal: simple enough to build and maintain today, but strong enough to scale without a complete architectural rewrite tomorrow.
FINAL ACCEPTANCE CRITERIA
The project will be considered complete only when a real school can:
Manage its institution and academic structure
Add teachers and students
Link parents/guardians
Manage classes and subjects
Record attendance
Create courses, lessons and learning materials
Create assignments and receive submissions
Create assessments/exams and grade students
Maintain academic records and publish results
Generate and verify certificates
Send announcements and notifications
Provide functional teacher, student and parent portals
Provide practical AI educational assistance
Support Arabic and English
Work reliably on desktop and mobile
Be deployed and ready for real-world use
The project is not considered complete simply because code has been written or screens have been designed.
Completion requires the agreed functionality to be implemented, functional, integrated, tested, accessible to the correct roles, free from critical blocking defects, deployed successfully and sufficiently documented.
Major missing functionality listed in this scope means the project is incomplete.
WHAT WE EXPECT FROM APPLICANTS
Before applying:
Review the repositories.
Understand the complete scope.
Form an independent technical opinion.
State whether you recommend continuing, refactoring, partially rebuilding or rebuilding from scratch.
Briefly explain why.
We are looking for strong engineering judgment and product ownership.
We define WHAT must be delivered. You recommend HOW it should be built.
We are not looking for someone to simply add features to a website. We are looking for someone capable of taking responsibility for delivering RTIQA v1 as a complete, functional, scalable, production-ready educational platform.