studio · system online
I'm Arthi — a Frontend / Angular Developer in Chidambaram, Tamil Nadu. I build the front of the product: dashboards, role-based platforms and the screens people use every day.
02 — Developer profile
Not a bio paragraph — the parts that actually tell you how I'd fit on a team.
Front-end for real applications — admin panels, role-based dashboards, listing and management screens. The kind of UI that has state, permissions and a backend behind it, not just a landing page.
03 — Featured work
Each one is a real application or interface — problem, build, stack and the engineering calls behind it. Open a case study to go deeper.
04 — Project universe
Filter by a technology to see where I've actually used it.
Angular SPA plus an Express/MongoDB API. JWT auth and route guards drive separate admin, teacher and student dashboards over shared course and user data.
React and Tailwind help-centre UI. A small set of reusable primitives — Card, Modal, Sidebar, Form — renders a data-driven article catalogue with search and sidebar navigation.
React + TypeScript client with an Express/MongoDB API. JWT register and login, protected task CRUD, bcrypt-hashed passwords and small gamification touches to keep the list moving.
React 19 dashboard with Recharts and Framer Motion. A single finance context feeds every chart and card, and transitions are motion-designed rather than default.
Angular 18 standalone components recreating a Figma admin dashboard — sidebar, breadcrumb header, stat cards, line and donut charts, data table and an activity panel, matched on colour, spacing and type.
Express 5 REST API with Mongoose models, JWT sessions, bcrypt password hashing, CORS and Nodemailer email. The backend half of the Student Management System.
Express/Mongoose API with a route–controller–middleware split, JWT auth middleware and full task CRUD. Ships with the Minimal Efficient ToDo frontend.
Frontend Developer (Web Application Developer) · BornWizh Technologies · Nov 2024 — Present
The day job: building and maintaining modules of an education platform in Angular — dashboards, listing screens and management panels used by different types of users.
05 — Toolkit
No percentages — they don't mean anything. Tap a technology to see the projects it actually shows up in.
The everyday tools — the ones every project here is built with.
How I structure single-page applications that grow past a few screens.
Making the frontend talk to a backend and behave under real data.
Layout, responsiveness and the visual layer.
Enough Node to build the API my frontend needs and work with backend devs.
Version control and getting things onto the internet.
06 — What I can help build
The kinds of work I'm set up to do well — each with a real example from what's above.
Build
A full single-page application — routing, guards, lazy-loaded features, typed services and forms.
Typical use
An internal tool or product that has outgrown a few static pages and needs real structure.
example →Student Management System
Build
Layouts that hold up from a 360px phone to a wide monitor, built on Flexbox and Grid without a heavy framework.
Typical use
A marketing site or app UI that has to feel right on every screen, not just the design mockup.
example →KnowledgeNexus
Build
Analytics and admin screens — stat cards, charts, tables and filters over a clean state layer.
Typical use
You have data and need people to actually read it and act on it.
example →Finance Dashboard UI
Build
Wiring a frontend to a backend — HttpClient, interceptors, auth tokens, loading and error states done properly.
Typical use
The API exists (or is being built) and the frontend needs to talk to it reliably.
example →Student Management System
Build
Internal tools where what you can see and do depends on who you are — enforced at the router, not just hidden in the template.
Typical use
Multiple user types — admin, staff, customer — sharing one application.
example →Student Management System
Build
A design file turned into pixel-accurate, responsive, componentised UI — matched on colour, spacing and type.
Typical use
You have a design and need it built faithfully, in a structure that survives real content.
example →Figma Dashboard
Build
Refreshing an existing frontend — untangling CSS, fixing responsive breakage, tightening interactions and accessibility.
Typical use
The app works but the UI feels dated, brittle or inconsistent.
example →Ongoing work at BornWizh Technologies
07 — Journey
Follow the path. Each checkpoint opens up.
Aries Arts & Science College for Women, Chidambaram
Bachelor of Computer Applications. Where the programming actually clicked.
Quaid-E-Millath Government College for Women (Autonomous), Chennai
Master of Computer Applications — deeper into software engineering and the web stack.
BornWizh Technologies, Chidambaram
Web Application Developer on an education platform, working across Angular modules with backend and QA.
Rebuilt a Figma admin design in Angular 18 standalone components — pixel-accurate, with Chart.js and a structure ready for real data.
Student Management System (full-stack Angular + Express/Mongo), KnowledgeNexus help centre, Finance Dashboard UI and a full-stack todo — auth, dashboards, data viz.
Looking for frontend, Angular or UI developer work where the frontend is treated as product, not decoration.
year building for the web professionally
projects with a live demo you can open
builds documented as case studies
of them full-stack, front to database
08 — UI lab
Interactions pulled out of the projects and made pokeable. Go on.
hover the line
click to cycle · animates in place
try it
env: midnight · click to cycle
09 — Contact
Roles, freelance frontend work, or a second opinion on an interface — all good. I reply to real messages.