Patel N.

Senior Front-End/Full-Stack Developer with 10+ years building enterprise web applications, specializing in React.js, TypeScript, and Node.js. I focus on scalable, maintainable UI architecture, performance optimization, and clean integration with REST APIs, and I work closely with PMs, designers, and backend teams to ship production-ready features in Agile environments. Recent work includes: Food Management SaaS Platform — An end-to-end admin panel for a food raw-material supply company, covering inventory, order processing, and role/permission-based access control. I translated evolving Agile requirements into production features, collaborating closely with the PO and QA team on quality. On the technical side, I solved a major complexity problem: large, interdependent forms with conditional validation were causing re-render issues in Formik, so I migrated the form layer to React Hook Form + Yup schema validation, which resolved the performance and maintainability issues. The platform is built on a modular monolithic architecture to support multiple teams working in parallel. Workforce Time-Tracking SaaS Tool — A centralized task management system that aggregates tasks from multiple third-party tools into one admin panel, with time logging via a desktop app (Electron), and reporting (user, project, financial). The core challenge was a complex multi-role permission system — I solved this by centralizing all permissions in a store and building a wrapper component that controls both UI visibility and route-level access based on role. Music Streaming Platform — Built custom playlist creation with time-scheduled streaming. Initially built in Node.js, but hit real scaling limits — sync issues, slow downloads, and poor concurrency under multiple simultaneous streams due to Node's single-threaded model. I researched alternatives, adapted a Go-based streaming package to fit the project's specific requirements, and rebuilt the streaming layer in Go for better concurrency and file I/O throughput — a case where I chose to bring in a new language specifically to solve a performance bottleneck rather than force-fit the existing stack. I'm also someone who actively explores new technology, though I've learned to validate feasibility early — after picking Flutter for a project under a tight deadline and having to pivot back to React Native mid-project, I now always vet technical feasibility against the deadline before committing to a new stack.