Education / Product engineering
- Apr 2025–Feb 2026
- PM / Frontend engineer
- Product engineering
- Private product
Overview
A connected learning system.
Graus connected the experience students used to practise mathematics with the tools administrators used to create and manage that content.
Built with
- Next.js
- React
- Tailwind CSS
- GSAP
- Lenis
- Express
- MongoDB
Why it mattered
A math platform should not feel like another textbook.
The most important change
- Before
- Course changes lived in backend JSON, so creating or updating content still depended on a developer.
- After
- The admin interface gave the team a visual way to create courses, organize topics, build activities, and set prerequisites.
Select a view to bring it forward. Select the focused image again to expand it; use the open stage or Escape to return.
Inside the product
One learning system, seen from both sides.
Students chose a course, completed an activity, reviewed the result, and earned a reward. Administrators created the content and set the prerequisites that guided each step.
Student view
Choose a course.
Students could browse available courses and topics from one clear starting point.
Administrator view
Set what comes first.
Administrators could add prerequisites when an activity depended on earlier work.
Student view
Complete an activity.
Short prompts, visual examples, answer choices, and lives kept attention on the task.
Student view
See the result.
The result brought the score, time, and earned experience together.
Student view
Build a streak.
A streak connected one completed activity to longer-term progress.
My role & contribution
From project manager into frontend and product engineering.
I started as project manager, helping define what the product needed and shaping its visual and UX direction. Moving into frontend engineering meant implementing those decisions myself while continuing to shape the experience.
- Project manager
- Frontend engineer
- Product engineer
As a product engineer, I carried that ownership across the product. I designed and built most of the front-facing screens shown here while connecting the public site, learner experience, administrator tools, authentication, and learning data into one system.
Design authorship. I designed and built most of the current product pages and UI shown here, drawing on parts of earlier product work. Most of the characters, icons, and illustrations came from earlier teamwork and were adapted for this version; my authorship is the interface, not those original assets.
Beyond the learning flow.
Profile customization and public pages extend the same visual language across the wider product.
