EdTech Developers Who Build for the Learner and Teacher

What makes EdTech development different from a standard web app?

EdTech development differs from a standard web app in its data: one product serves several roles, keeps progress that must stay accurate, and carries content that changes every term. These skills matter beyond the stack:

1. Roles and permissions. Learner, teacher, admin, parent and company manager each see a different slice of the same records. A plan change or a new branch must not leak one slice into another.
2. Progress and grading data. Attempts, scores and completions have to survive course edits, so fixing a typo in question 4 does not wipe last month's results.
3. Content pipelines. Courses, quizzes and video arrive from authors, imports and AI tools, and each source needs a review step before learners see it.
4. Payments that match access. Subscriptions, company seats and instalment plans decide who may open which lesson, and a failed renewal has to change access on time.
5. Mobile apps. Mobile engineers are the largest group among EdTech engineers in Cortance's network, 11 of 32 as of October 2026, working in Kotlin Multiplatform, Flutter, React Native and Swift.

Which rules reach your code: COPPA, FERPA, accessibility and GDPR?

Children's privacy, student records and accessibility rules all reach EdTech code, and two of them changed recently. The FTC's amended COPPA Rule took effect on June 23, 2025, and operators of services for children under 13 had to comply by April 22, 2026 (Federal Register, 2025). It adds biometric identifiers such as voiceprints and facial templates to personal information and tightens the rules on information security, data retention and parental consent. The FTC kept its proposed school-specific rules for ed tech on hold until the US Department of Education updates FERPA, the law on student education records. Until then, it enforces COPPA in schools under its existing guidance.

Accessibility has a date too. The US Department of Justice's 2024 ADA Title II rule requires WCAG 2.1 Level AA for the websites and mobile apps of state and local governments. Public schools and universities are included. An interim final rule of April 20, 2026 moved the deadline to April 26, 2027 for public entities serving 50,000 people or more (Federal Register, 2026). Smaller ones have until April 26, 2028. Content a university provides through a vendor's platform counts, so a product sold to public universities is measured against the same standard. Learners in the EU add GDPR on top.

None of this is a certificate an engineer can show. It shows up as decisions in past projects. Think of an age check before any data is collected, recordings deleted on a schedule, and screens that work with a keyboard and a screen reader. Yusif O. added accessibility support to Steplab Record, a companion app for the Steplab education platform, and that is the kind of line we look for when a client sells to schools. Your legal counsel decides which rules apply; the engineer has to build to them.

LTI, SCORM and xAPI: when does your product need them?

LTI, SCORM and xAPI matter when your product has to live inside someone else's learning system. LTI lets a tool open inside an LMS such as Canvas or Moodle with the user's identity and role passed along. SCORM packages a course so an LMS can play and track it, and xAPI records learning activity, including activity outside a course, in a learning record store. Schools and universities that run an LMS ask for LTI; corporate L&D teams with existing course libraries ask for SCORM or xAPI.

As of October 2026, none of the project descriptions in Cortance's network name SCORM, xAPI or LTI. If your product depends on them, tell us at the start, and we will look for the closest experience: single sign-on into another organisation's systems, as David M. built with Identity Server for the NCC Education portal, or progress and certification tracking inside a learning platform.

What to check in an EdTech developer's past projects

1. More than the learner screen. Did they build the teacher, admin, parent or billing side, or only the course player?
2. A change on their watch. A plan migration, a new branch or a move to new infrastructure shows how they protect data that already exists.
3. Scale and peaks. How many learners, branches or live sessions, and what happened at enrolment or exam time?
4. Children in the audience. If the product served users under 13, what did consent and data deletion look like?
5. Where content came from. Was it written by authors, imported from PDFs and other systems, or generated, and who checked it?

A red flag is a portfolio of course websites with no roles, no progress model and no payments. That is web design work, and an education product needs the rest soon after launch.

Why are EdTech companies hiring developers now?

EdTech companies are hiring for two changes that arrived together. Rules have caught up: the amended COPPA Rule is in force, and public universities have a fixed date for accessible web and mobile content. That date also reaches the vendors whose platforms they use. AI tools now draft course material, so the engineering work shifts to the pipeline that checks generated content before learners see it. Both changes land on products that already run, so the useful hire is often an engineer who can change a live platform without breaking what learners and payers rely on.