React and Next.js developer. I specialize in clean UI, responsive dashboards, and API-driven full-stack apps — the kind of work hiring teams can clone, run, and judge for themselves.
Hiring manager fit -> your role, my work
Every role shows a different lens - same candidate, right context for your team.
Active hiring context
I translate Figma into structured, reviewable React - reusable components, responsive screens, and code that doesn't need to be rewritten after the first review.
What to evaluate
Look at component structure, how I name things, and whether the UI holds up at every breakpoint. That's where the real signal is.
Relevant for this role
What I bring
What I've built
What I use
What I actually build
Three capability areas. Each one shows the skill, what it produces, and evidence you can inspect - not just a list of technologies I've touched.
Every component is structured for someone else to read, extend, or review - not just for it to work once. Responsive by default, not as an afterthought.
"Can you take this Figma and build it?" - yes, and the output will match.
Auth, CRUD, REST APIs, and MongoDB connected to real UI. Both sides of the stack working together - not two halves duct-taped together.
Clone any project, run it, and the data is real.
Git branches, pull requests, Vercel deploys, Postman API testing. The workflow matches what engineering teams expect on day one.
Every project has a live link - not a localhost screenshot.
Featured projects
Each project targets a specific capability. Live demo and GitHub repo on every card - no screenshots-only work.
Preview
Project 01
Built to demonstrate a complete SaaS product flow - login through dashboard through data display - using the stack most product teams are hiring for. Deployed on Vercel.
Evaluate: Component structure and how state flows to the UI
Evaluate: Responsive behavior at every breakpoint
Evaluate: Auth state handling and protected routes
Preview
Project 02
End-to-end user auth with registration, login, protected routes, and a full CRUD interface backed by MongoDB. Frontend and backend connected - no placeholder data.
Evaluate: How auth state persists across page refreshes
Evaluate: API structure and how routes are organized
Evaluate: MongoDB schema decisions and data structure
Preview
Project 03
A purpose-built REST API with full CRUD endpoints, tested in Postman, consumed by a React frontend. Shows both sides: how the API is structured and how the UI handles real responses.
Evaluate: Endpoint naming, response shape, and error handling
Evaluate: How loading and error states are shown in the UI
Evaluate: Postman collection - all routes documented and tested
Live GitHub dashboard
This section reads my public GitHub profile, repositories, languages, stars, forks, and recent events so hiring teams can inspect current activity instead of a static screenshot.
What I'm building next
Three projects in active development. Each one is a real tool I'd actually use - not a tutorial clone.
A reusable dashboard starter - drop it into any project and get auth, billing layout, charts, and role-based nav ready to go. Built to be forked, not just admired.
Will demonstrate: reusable architecture, component design systems, and role-based access patterns.
Saves prompts, generates drafts, and organizes content projects - one workspace for the full AI writing workflow. Next.js frontend consuming a Node REST API with Firebase storage.
Will demonstrate: AI API integration, real-time data handling, and multi-view dashboard layout.
A CRM built for job searching - track applications, log notes, set reminders, and link GitHub proof directly to each role. The tool I wish existed when I started applying.
Will demonstrate: CRUD workflows, relational data modeling, and a UI built around a real user need.
These aren't for the portfolio. They're tools I'm building because I needed them - and shipping them is how I learn fastest.
Contact
Role fit, project walkthrough, or just a quick intro - any of those works.