Frontend development
Interfaces built on semantic markup and a real type and spacing system, so hierarchy holds at every viewport.

I take a product from the first interface decision through the application logic, the database, the authentication and the deploy. One person, one continuous build.
That matters most where the seams usually are. A payment has to become a record a parent can read. A login has to survive a refresh. A layout has to hold at 375px and at 1920px. I work on both sides of those seams, so nothing gets handed off and lost.
Currently building school and business platforms with Next.js and React on the front, Python and Flask on the back, and PostgreSQL underneath.
Selected work / 01
Real products, shown through their own interfaces and the decisions behind them.
Project / 01
Maitrebuilder
A full-stack school platform connecting results, payments, admissions, attendance, CBT examinations, parent access, and administration.
View case studyCapabilities
Interfaces built on semantic markup and a real type and spacing system, so hierarchy holds at every viewport.
Application logic, role-aware workflows and APIs that stay predictable once real users depend on them.
Relational schemas, server-verified sessions and permission boundaries enforced away from the client.
Third-party services wired into journeys that produce traceable records rather than dead ends.
Production delivery measured against real numbers — payload, layout stability, and time to interactive.
Technical foundation
What I actually build with, grouped by the part of the product it holds up.
Next.jsReactTypeScriptJavaScriptHTMLCSS
PythonFlaskREST APIs
PostgreSQLSupabase
GSAPScrollTriggerLenis
VercelCloudflareGitHub
Experience
2026 — Present
Designing and shipping complete web products for clients — interface, application logic, data layer and deployment handled end to end rather than handed off.
2026
Built a single operational platform covering admissions, attendance, CBT examinations, results, fee payments and parent access, replacing processes that were split across paper and disconnected systems.
2025
Moved from interface work into backend systems — authentication, relational schema design and payment integration — and made the two halves a single discipline.