Hamza Nafasat

Tech Team Lead

Jun 2024 - Present • 2 yrs 1 mo

At Devno Sol I work as a tech team lead for a full stack development team. This current role covers two things. Leading and mentoring junior and mid level developers, and personally handling the complex technical work that needs senior level thinking, especially anything involving AI integration. In the last year most of my hands on work has been AI integration. This includes OpenAI API integration into existing apps, building RAG systems for knowledge base and document based chatbot features, and AI agent development for automation tasks, the exact services I now offer directly as RAG chatbot, AI voice agent, and OpenAI integration gigs. I also work with Convex database for real time data needs and Clerk authentication for projects that need solid auth handled correctly the first time. On the core stack side I build with Next.js as the main framework, handle Node.js on the backend, and manage Vercel and Railway deployments depending on what the project needs. I set up CI/CD pipelines so deployments stay clean and repeatable instead of manual and risky. As team lead I do code reviews, help the team with Next.js debugging and complex bug fixing, and set project architecture before development starts. I am the person the team comes to when something breaks in production and nobody can figure out why, which is the same root cause tracing I apply to every Next.js and Node.js bug fix and deployment rescue I take on for clients. This role sharpened my system design thinking, my ability to mentor other developers, and my comfort handling AI integration problems most developers still avoid because the retrieval and reliability side of AI is harder than it looks from the outside.

Backend Developer

Feb 2024 - Jul 2024 • 5 mos

At Tyzend I worked as a part time remote backend developer, handling the server side of their main product while working alongside their in-house frontend team. My main focus was Node.js development for their backend APIs and services. I built and maintained REST APIs, handled database design and query optimization, and took full ownership of their VPS deployment setup. This is where I went deep into server work, including Docker deployment, Linux environment setup, environment config management, and keeping production stable under real traffic, the exact deployment and rescue work I now offer as its own gig. A large part of this role was debugging server side issues. Production crashes, slow API responses, memory leaks, and broken database connections were normal weekly problems, not rare events. Because I worked remotely and part time, I had to read logs fast, find the real cause, and fix it without constant back and forth with the team. This made me sharper at Node.js debugging than most developers who only work from an office with someone next to them to ask. I also built Docker deployment workflows, set up basic server monitoring, and worked on improving API response times under load. The team was small, so I had to be self reliant and solve problems with very little handholding. Working at Tyzend taught me that backend development in a remote setup lives or dies on clear communication and fast problem solving. The VPS deployment, Docker, and Node.js debugging instincts I built here are exactly what I bring to every bug fix and deployment rescue order today.

Full Stack Developer

Jan 2024 - Apr 2024 • 3 mos

At Acme Digital Solutions I worked as a full stack developer across multiple client projects, building production web apps with Node.js and Next.js on the backend and React on the frontend. Day to day I built REST APIs, set up deployment pipelines, wrote clean component based React UIs, and fixed bugs across the whole stack when something broke. A big part of my role was taking client requirements and turning them into working, production ready apps from scratch instead of prototypes that needed a rebuild later. This is also where I built the bug fixing instincts I use today. Most projects had tight deadlines, so I got very good at tracing root causes fast instead of guessing, especially when an app worked locally but failed after deployment. I handled CI/CD setup using GitHub Actions, Docker based deployments, and backend architecture for new projects, the same Next.js and Node.js debugging and deployment work I now offer as a standalone service. I also worked on database design, auth flows, and third party API integrations, which is where I learned to write code other developers can actually read and maintain without confusion. Clean structure matters as much as the feature working on day one. Working here taught me how to handle the full product lifecycle, from the first client meeting all the way to deployment and post launch bug fixing. I did this across 5 plus projects in different industries, which gave me a broad understanding of how different businesses actually use Node.js and Next.js in production, not just in theory.