Surbhit A.

I’m comfortable stepping into those situations.

I normally begin by reviewing the repository, architecture, database, deployment setup, integrations, and current issues. From there, I separate what should be fixed immediately from what can stay as it is.

I don’t believe in rewriting an application simply because I would have built it differently. If the existing code is usable, I work with it. If something genuinely creates a reliability, security, or scalability problem, I’ll explain why before changing it.

Recent work

One project involved more than 748 hours of development on a logistics software package, where the application had multiple workflows and business rules that needed to work together reliably.

I’ve also built a custom quote builder using Replit, taking the initial application and turning it into a more structured product workflow.

Another recent project involved implementing a complete full-stack SaaS application over five months, covering both frontend and backend functionality.

I’ve also worked on Twilio Voice integration for a VoIP product, connecting calling functionality with the wider application and backend systems.

My typical stack

React, Next.js, TypeScript, JavaScript, Tailwind CSS, Node.js, NestJS, Supabase, PostgreSQL, MongoDB, Stripe, Twilio, REST APIs, Vercel, AWS, Git, and GitHub.

How I approach development

I like to understand the product before writing code.

Who will use it? What is the main workflow? What needs to happen in version one, and what can wait? Which integrations are critical? Where does the data live? What could cause problems once real users start using the system?

Once those questions are clear, I can recommend an architecture that fits the actual product rather than overengineering an MVP.

During development, I focus on keeping the frontend, backend, database, APIs, authentication, payments, and deployment working as one system.

I also pay attention to the less visible parts of development: error handling, database design, permissions, API failures, webhooks, validation, logging, performance, and maintainability.

These are usually the things that determine whether an application keeps working after launch.

For larger projects, I’m backed by the HestaBit team, including UI/UX designers, QA engineers, DevOps specialists, mobile developers, and additional frontend or backend developers.

That means I can work directly as your full-stack developer for a focused build, while still having the ability to scale into a small product team when the project requires it.

If you already have designs and specifications, I can start from there. If you only have the product idea, I can help turn it into a practical technical plan before development begins.