Moodle Developer in Spain
EU-based senior Moodle developer working remotely with universities, corporate L&D teams and EdTech vendors across Europe. CET working hours, English-fluent communication, EUR invoicing.
Five years of Moodle, two of them at Moodle HQ. I know the core internals: APIs, release cycles, plugin policy, security model and compatibility.
Typical engagements: technical audits, custom plugins, version upgrades (3.x → 4.x → 5.x), CRM/ERP integrations, WCAG accessibility work, performance tuning and ongoing support.
I publish plugins to moodle.org when the client authorises and the scope is generic. Otherwise it stays on private repos under your ownership.
Need a senior Moodle developer in Europe? Book a 30-min discovery call or send a brief.
Frequently asked questions
How much does a custom Moodle plugin cost? ＋
Custom plugins start at €500. The final price depends on scope: number of screens, external API integrations, automated test requirements and the maintenance policy you want. You get a fixed-fee proposal within 24 hours of a brief or discovery call.
Do you work with Moodle 4 and Moodle 5? ＋
Yes. I keep plugins compatible with both branches and plan migrations from 3.x to 4.x and from 4.x to 5.x. Audit-only migration reports are available if you just need the report.
Can you audit my Moodle and only deliver the report? ＋
Yes. Audit-only engagements cover performance, security, plugins, accessibility, GDPR and a clear improvement plan, with no obligation to hire the implementation.
Do you work with clients outside Spain? ＋
Yes. I invoice in EUR and USD, sign international contracts and work CET / GMT hours. I have shipped projects with clients in Colombia, Mexico, the United States and across the EU.
Will you sign an NDA? ＋
By default yes. I can sign your standard NDA or supply a GDPR / LOPDGDD-compliant template.
Do you publish my plugin on moodle.org? ＋
Only if you authorise it and the scope is generic (not specific to your organisation). When we do, it is explicit in the contract and you keep all brand and configuration rights.
How do you handle WCAG accessibility? ＋
Every new plugin ships with a WCAG 2.1 level AA checklist covered: contrast, keyboard navigation, visible focus, alt text, HTML semantics, screen-reader compatibility and prefers-reduced-motion support.