Next.js and frontend architecture
New product builds, App Router work, design-system implementation, and the frontend decisions that keep a codebase maintainable after launch.
New builds · architecture · design systems
Limited availability this week
Hire a Next.js and full-stack engineer for work that has to ship.
I take on frontend-heavy and full-stack product work where implementation quality, maintainability, and delivery discipline matter. That includes new builds, rescue passes, SEO and performance upgrades, admin tooling, and AI-enabled product surfaces.
- Years building
- 8+
- Published projects
- 5
- Skills catalogued
- 613
- Credentials & badges
- 93
What I can take on
Four areas where I do implementation-heavy work. Most projects draw on more than one.
Performance and SEO hardening
Core Web Vitals, metadata, structured data, sitemaps, canonical strategy, and crawl-surface fixes that hold up in production.
Speed · search · technical SEO
Admin tools and content operations
Dashboards, CMS workflows, review queues, and the internal surfaces that keep content moving without turning every change into an engineering ticket.
Dashboards · CMS · workflows
AI assistant experiences
Public-safe assistant UX, retrieval-aware flows, telemetry, and the admin controls needed to ship AI features without surprises.
Assistants · retrieval · guardrails
How an engagement runs
Clear scope first, then a short loop from proposal to working software. No black-box retainers.
Three ways to work together
- Fixed-scope build
- A clearly defined product increment with a fixed scope, timeline, and deliverable.
- Sprint contract
- I join your team for a defined period and work through the priority queue with you.
- Fractional role
- Ongoing frontend, SEO, and AI surface work across several workstreams.
Remote-first. Async updates by default. Weekly checkpoints so decisions do not wait for a meeting.
From first message to handover
- 1
Scoping call
Thirty minutes to confirm the goal, stack, constraints, decision-maker, and timeline. No commitment yet.
- 2
Written proposal
You get the scope, deliverables, timeline, and rate in one document. We adjust once before starting.
- 3
Weekly delivery
Working software every week, a short written update, and four to six hours of overlap with your time zone.
- 4
Handover
Code, deploy notes, and the context your team needs to keep moving without me.
Selected work
A few production builds that show the kind of problems I take on.
Award2024Case study
Space Otaku
Developed a Progressive Web App (PWA) for space education, listed in the published portfolio as receiving 1st Prize. Engineered a custom, performance-optimized game engine within React for the 'Space Shooter' module. Integrated a conversational AI agent powered by Dialogflow for interactive learning and implemented a rigorous reliability suite using Checkly to monitor API health and uptime.
Next.jsSCSSDialogflowPWA
2026Case study
MyRigCheck
Personal Product
Built a production game-compatibility platform that checks 367,825 titles against a detected PC rig and returns FPS estimates, bottleneck analysis, and a Rig Power Score. Designed a deterministic IGDB + Steam read-layer pipeline with phase-based builds, blue-green swaps, and post-swap canaries, then served the catalog through a read-only database gateway with a graceful degraded mode for the self-hosted origin.
Next.js 16React 19TypeScriptMongoDB
2025Case study
Lake Como Style
Freelance Project
Architected a high-performance, cinematic event booking platform using the bleeding-edge Next.js 16 and React 19 stack. Engineered a scalable content management system with Sanity to handle 11+ custom schema types, ensuring seamless client updates. Implemented complex UI animations using Framer Motion and Lenis for smooth scrolling, while building a robust transactional email service with Nodemailer for automated booking confirmations.
Next.js 16React 19Sanity CMSTailwind CSS 4
Availability and fit
This is the working schedule for the current week. If the timing matters, the scoping call is the fastest way to confirm a start date.
- Mon
- Busy
- Tue
- Busy
- Wed
- Busy
- ThuToday
- Busy
- Fri
- Busy
- Sat
- Busy
- Sun
- Available
1 available day this week. Replies within 48 hours on working days, from Kolkata, West Bengal (IST).
Good fit
- Next.js, React, and TypeScript product work that needs an owner.
- Performance, SEO, metadata, and structured-data upgrades.
- Admin tools, CMS workflows, and content operations.
- AI assistant surfaces that need safe public behavior and guardrails.
- Rescue passes on a codebase that has outgrown its original structure.
Probably not a fit
- Design-only work with no engineering scope.
- Projects with no clear owner or decision-maker.
- Work that needs a fixed rate before the scope is defined.
Not sure which side you are on? Send the context anyway and I will tell you honestly.
Questions before you write
The things people usually ask before sending a brief.
Do you take freelance or contract web development work?
Yes. I take select freelance, contract, and project-based web work when the scope, timeline, and expectations are clear.
What types of projects are the best fit?
The strongest fit is frontend-heavy or full-stack product work involving Next.js, React, TypeScript, design systems, performance, dashboards, CMS workflows, or AI-assisted web experiences.
Can you work with teams outside India?
Yes. I can collaborate remotely with product teams, founders, and agencies across time zones, with communication and delivery expectations agreed upfront.
How is pricing decided?
Every engagement starts with a scoping call and a written proposal. The proposal lists the deliverables, timeline, and rate for that scope, so the number is tied to the work rather than a generic rate card.
What happens after I send the form?
You get an email confirmation immediately, and your message goes straight to my inbox. I reply within 24 hours on available days, or 48 hours otherwise, usually with a few questions or a proposed scoping call.
Tell me what you're building
A short message is enough to start. The more context you give, the faster we can decide whether a scoping call makes sense.
What to include
- The outcome you need, in one or two sentences.
- Your current stack and where the work lives.
- Timeline or deadline, and what happens if it slips.
- What is blocking you today.
- Budget range, if you have one.
Replies within 48 hours
On working days. Your message goes straight to my inbox, not a queue.
Send a message
Replies typically in <48hLaneHire me