Score first, explain second.
Validate the assessment structure before explaining it in the learner’s language. Connect feedback to rewriting and reusable expressions.
PRODUCT / BUILD / SHIP2026.07
Tago
Write
From a writing score to the next revision.
INDEPENDENT PRODUCT / RELEASED
01 / CONTEXT & CONTRIBUTION
The problem.
My part in it.
Background
- A writing score did not tell learners how to revise.
- Casual writing and TOPIK tasks needed different criteria.
- Feedback had to match language and level, with draft comparison.
- AI requests also required recovery, deduplication and cost controls.
Objective
- Connect understandable assessment with the next writing attempt.
- Combine scoring, localized feedback, revision and saved expressions.
My role
- Independent product / planning, AI-assisted development and QA.
- Implemented server jobs and cost controls; shipped and updated the app.
02 / SYSTEM DESIGN
How it connects.
Processing / data flowIteration / feedbackService / environment boundary
Own the release.
Persist evaluation jobs, recover failures and control duplicate requests and model costs. Continue shipping updates alongside content and QA work.
03 / RESULTS & SCOPE
The outcome.
4Assessment dimensions
5Interface languages
2026.07Released
Product capabilities and release date, not measured learning outcomes. Product planning, AI-assisted development, QA and release owned directly.