Roxana C.

Moodle specialist, Top Rated Plus with 100% Job Success. I build the parts of Moodle that don't come out of the box: custom plugins, LTI 1.3 integrations, xAPI/SCORM pipelines, and the reporting layer on top. Sixteen years in software, eleven of them on a corporate eLearning platform used by clients across multiple countries, plus independent Moodle work for my own clients. WHAT I'VE ACTUALLY SHIPPED - 40+ Moodle plugins in production: certification (including regulatory compliance for a financial-sector client), learning programs, configurable performance dashboards, payments, web services, and GDPR/Privacy API compliance. Several with PHPUnit suites running hundreds of cases. - 2 plugins published on the official Moodle Marketplace, both approved through Moodle's review process and both awarded the "Privacy friendly" and "Automated testing support" badges: Course link picker (tiny_courselink), a TinyMCE subplugin, and Heading Contents (filter_headingtoc), a text filter with a navigable table of contents. GPLv3, stable releases, CI on a Moodle 4.5 LTS to 5.2 matrix. - LTI 1.3 on both sides. As a tool provider: launching content inside any standards-compliant LMS, with Deep Linking 2.0, multi-tenant auto-registration and cross-site iframe session isolation. As a consumer: a shared course catalog serving multiple Moodle instances from one canonical source. Since AGS only returns the grade, I extended it with web services to also return completion, progress and time spent. - xAPI / LRS analytics. An LRS to ETL to relational pipeline with scheduled jobs and CI/CD. I once found a client's sync that had been silently dead for ~541 days, traced the root cause and recovered 13,000+ missing activity records. - Performance and data work on live systems: a latin1 to utf8mb4 migration across 49 tables and 221 columns (reversible), N+1 query fixes, indexing, and caching that took dashboard widget computation from ~47 ms to ~0.1 ms. HOW I WORK I take the whole problem, not just the ticket: root cause, a plan you can read, the fix, and tests that prove it. Migrations run reversible, with a dry run and a backup first. If I think you're asking for the wrong thing, I'll tell you before I build it, not after. I'm fully independent, architecture through deployment (nginx, PM2, Docker, AWS, VPS), so I don't need someone else's infrastructure team to finish. Beyond Moodle: Node.js/Express, React/TypeScript, Angular, PHP, Python/FastAPI, MySQL/MariaDB, PostgreSQL, MongoDB, REST APIs, OAuth 2.0/OpenID Connect. A NOTE ON LANGUAGE - PLEASE READ I work in English in writing only: code, documentation, specs, issues, pull requests, async updates. I do not take calls in English. If your process requires voice or video meetings in English, I'm not the right fit, and I'd rather you know that now than three weeks in. What works well with me: a written brief, an issue tracker, async updates, and recorded walkthroughs of what I built. Spanish is my native language, so calls in Spanish are no problem at all.