Work / Selected systems
Products are shown here as systems under pressure: the constraint, the engineering response, and the measurable evidence that the response worked.
Portfolio capability map
Follow each project through the capabilities it exercises. Bright cells mark substantial, documented responsibility—not a technology checklist.
| Project | Architecture | Reliability | Product UX | Performance | Data | Knowledge |
|---|---|---|---|---|---|---|
| 01Tinkoff fintech | ||||||
| 02Kanban | ||||||
| 03Engineering Wiki | ||||||
| 04Polaris | ||||||
| 05WikiMasters | ||||||
Documented responsibility Adjacent capability | ||||||
01 / Production evidence
Four and a half years of product evolution, expressed through the architectural decisions that kept delivery moving.
Built and evolved partner and internal operations frontends for a fintech platform serving 300,000+ users, spanning onboarding, analytics, approvals, documents, and real-time workflows.
02 / Built in public
Public products used as engineering laboratories—not decorative side projects.
A full-stack Kanban system built to make drag-and-drop feel immediate while protecting task state when requests fail, sessions overlap, or clients fall behind.
A growing map of frontend engineering connecting first-principles explanations, interview reasoning, quick references, and deliberate practice.
A Next.js and TypeScript browser IDE connecting a file tree, code editor, terminal, live preview, GitHub import/export, and AI assistance.
A collaborative wiki MVP for creating, editing, and reading articles. Authored knowledge stays central, supported by media, cached reads, and AI summaries.