AI is changing how we build software.
It is also changing how people learn.
For developers, however, building an AI-powered learning product is not simply a matter of connecting an LLM to a chat interface and adding a "Tutor" button.
Education introduces a different set of engineering problems.
A system can produce a technically impressive answer and still be a poor learning system.
It can answer a student's question correctly but fail to explain why. It can generate a personalized exercise that is actually inappropriate for the student's level. It can provide a confident answer when it should say, "I'm not sure."
And unlike many consumer applications, the consequences can accumulate over time.
That raises a more interesting question for developers:
What does it actually take to build an AI system that helps people learn?
I don't think there is one universal answer, but there are a few principles worth considering.
1. An AI tutor is not just a chatbot
A chatbot primarily responds to a user's current message.
A learning system needs to understand something larger.
It may need to know:
What the learner is studying
What they already understand
Where they are making mistakes
What level they are working at
Which explanations have already been given
What they are trying to achieve
Whether they are improving over time
That changes the architecture.
Instead of thinking:
User → Prompt → LLM → Response
a learning-oriented system starts looking more like:
Learner
↓
Learning Context
↓
Relevant Content + History
↓
Reasoning / Generation
↓
Safety + Quality Checks
↓
Learner Response
↓
Assessment + Feedback
↓
Updated Learning Context
The model is only one part of the system.
The surrounding context can be just as important.
2. Context can matter more than model size
There is a natural tendency to ask:
"Which model should we use?"
That's an important question, but it isn't always the first question I would ask.
A more useful question is:
"What information does the model actually have when it makes a decision?"
Imagine two systems.
The first has access to a very powerful model but only receives:
Explain photosynthesis.
The second uses a smaller model but knows:
Student level: GCSE
Topic: Photosynthesis
Previous attempt: Incorrect
Known weakness: Confuses chlorophyll with chloroplasts
Current objective: Explain the role of chlorophyll
Preferred explanation style: Short examples
The second system has substantially more useful information.
This is why educational AI should not be designed purely around model selection.
Retrieval, learner state, structured data, assessment history and carefully selected context can have a huge influence on the quality of the experience.
3. Personalization is more than recommending content
Personalization is often reduced to:
"Student A likes mathematics, so show Student A more mathematics."
That's recommendation.
Useful personalization goes deeper.
A learning system might recognize that two students studying the same topic have different problems.
For example:
Student A
Understands the concept but struggles with exam questions.
Student B
Can solve the exam questions but doesn't understand the underlying concept.
Giving both students the same explanation isn't necessarily personalization.
A better system could change:
The difficulty of questions
The type of examples
The amount of explanation
The order of topics
The frequency of revision
The type of feedback
The next recommended activity
This makes personalization a system-design problem rather than simply an AI feature.
4. The difficult part is knowing whether the AI helped
This is probably one of the most interesting problems in AI-powered education.
For a normal chatbot, we might evaluate:
Response quality
Latency
Accuracy
Cost
User satisfaction
Those metrics still matter.
But education adds another question:
Did the learner actually learn something?
Suppose an AI explains algebra beautifully.
The student responds:
"That makes sense."
That's useful feedback, but it doesn't prove learning occurred.
A stronger evaluation loop might look like:
Explanation
↓
Practice
↓
Attempt
↓
Assessment
↓
Feedback
↓
New Attempt
↓
Measure Improvement
The goal isn't simply to generate better explanations.
The goal is to produce better learning outcomes.
That distinction is easy to miss when building AI products.
5. Assessment should be part of the loop
One of the mistakes we can make with AI learning systems is treating assessment as something that happens at the end.
In reality, assessment can provide valuable context throughout the learning process.
For example, an incorrect answer can reveal:
A missing prerequisite
A misconception
A calculation error
A vocabulary problem
A misunderstanding of the question
A gap in conceptual knowledge
The important part isn't just marking the answer wrong.
The interesting engineering problem is determining what the mistake tells us about the learner.
That information can then influence what happens next.
Question
↓
Student Answer
↓
Error Classification
↓
Learning State Update
↓
Targeted Feedback
↓
Next Activity
This creates a feedback loop rather than a collection of disconnected features.
6. AI needs boundaries in education
A learning system should not treat every generated answer as automatically trustworthy.
This is particularly important when students are relying on the system for academic information.
Depending on the use case, developers may need:
Retrieval from trusted sources
Content boundaries
Citation or source references
Output validation
Moderation
Confidence handling
Human review
Clear escalation paths
Sometimes the best response from an educational AI system isn't:
"Here's the answer."
It may be:
"I'm not confident enough to answer that reliably. Here's what I can verify."
That behavior can feel less impressive in a demo.
It can be much more responsible in a real learning environment.
7. Human oversight doesn't make an AI system less intelligent
There is sometimes an assumption that adding teachers or administrators into an AI workflow defeats the purpose of automation.
I don't think that's necessarily true.
Teachers have context that software often doesn't.
They can notice:
A student losing motivation
A repeated misconception
A change in behavior
A learning difficulty
A question that requires emotional or social context
AI can help surface patterns.
Humans can interpret those patterns.
A useful architecture therefore doesn't necessarily replace the human:
AI → Teacher → Student
Instead, it can become:
Student
↓
Learning Activity
↓
AI Analysis
↓
Useful Signals
↓
Teacher Insight
↓
Human Decision
The objective isn't to automate every decision.
It's to make better decisions possible.
8. Privacy becomes part of the architecture
Educational software can deal with sensitive information.
Learning history, assessment results, behavioral patterns and personal information should not be treated as ordinary application data.
Privacy therefore isn't simply a policy-page issue.
It affects architecture.
Developers should think carefully about:
What data is collected
Why it is collected
How long it is retained
Who can access it
What is sent to third-party AI providers
Whether data is used for model improvement
How users can control their information
The less data a system needs to achieve a particular function, the easier it can be to reason about the privacy implications.
9. Don't build the AI feature before understanding the learning problem
This might be the most practical lesson.
It is tempting to start with:
"Let's add an AI tutor."
But a better starting point is:
"Where exactly are learners struggling?"
Maybe the problem is not explanation.
Maybe students struggle with revision.
Maybe teachers spend too much time creating assessments.
Maybe students receive feedback too late.
Maybe school leaders don't have enough visibility into learning progress.
The AI capability should follow the problem.
Not the other way around.
10. The future is probably hybrid
I don't think the future of educational technology is going to be:
AI replaces teachers.
I also don't think it will be:
AI is simply another chatbot students occasionally use.
A more realistic direction is a hybrid learning environment where software handles repetitive and data-heavy tasks while educators remain responsible for judgment, relationships and important decisions.
AI can help with:
Generating practice material
Adapting explanations
Identifying learning gaps
Summarizing progress
Providing immediate feedback
Finding useful learning resources
Teachers can focus more of their time on:
Mentoring
Motivation
Deeper instruction
Classroom relationships
Complex learning decisions
That's a much more interesting future than simply putting a chatbot inside an LMS.
A simple mental model for developers
If you're building AI for education, it may help to think about the system as five layers:
┌─────────────────────────────┐
│ Experience │
│ Student / Teacher / Admin │
├─────────────────────────────┤
│ Intelligence │
│ AI / Reasoning │
├─────────────────────────────┤
│ Context │
│ History / Content / State │
├─────────────────────────────┤
│ Measurement │
│ Assessment / Progress / QA │
├─────────────────────────────┤
│ Trust & Safety │
│ Privacy / Access / Review │
└─────────────────────────────┘
The LLM sits in the middle.
It isn't the entire product.
That distinction becomes increasingly important as AI moves from experiments into real educational systems.
Final thought
We're entering an interesting period for EdTech.
The technical barrier to generating explanations, questions and summaries is becoming lower.
That means the competitive advantage may gradually move away from simply generating content.
The harder problems are becoming more interesting:
How do we understand a learner?
How do we measure whether learning actually happened?
How do we personalize without over-automating?
How do we keep students safe and their data private?
And how do we design AI that works with educators instead of simply trying to replace them?
For developers, that's where AI-powered education becomes much more than an LLM integration problem.
It's a systems problem.
And, ultimately, it's a human problem.
What do you think is the hardest engineering problem in AI-powered education right now: personalization, assessment, reliability, privacy, or something else?
Top comments (0)