Frontend Engineer

Experience - 3–5 years

Location - Vikhroli, Mumbai

 CTC - 15-18 LPA

About the Role

We're looking for a Frontend Engineer to build and own product surfaces in NymbleUp's web app — the workforce-scheduling, LMS and video-analytics platform used daily by store managers and HR teams at large enterprise clients. You'll work in a Next.js 16 / React 19 / TypeScript codebase (App Router, MUI 7, Zustand, SCSS Modules) of roughly 250k lines, shipping features like the Workforce Scheduler: a virtualized week/day planner that stays interactive with 2,000+ employee rosters, drag-and-drop shift editing, bulk actions and approval flows. This is a hands-on role for someone who cares about performance, state design and correctness in data-heavy UIs, not just pixel-pushing.

What You'll Do

• Build and maintain features end-to-end in Next.js (App Router) and React 19 with TypeScript — route, view, store, service layer.
• Design client state with Zustand stores and selectors so that single edits don't re-render whole grids; keep server data flows clean through our Axios service layer and typed endpoint modules.
• Ship performance-sensitive UI: row virtualization, memoized cells, debounced filters, Web Workers for heavy rollups, and measured frame budgets on large rosters.
• Implement complex interactions — drag/resize/copy of shifts, keyboard editing, bulk apply, approval and publish flows — with correct date/time and timezone handling.
• Work with the Django backend team on API contracts: read responses critically, log blockers with concrete recommendations, never invent endpoints.
• Build with the shared component library and design tokens (MUI theme + SCSS tokens); extend it rather than re-rolling components.
• Debug production issues across multi-tenant deployments (auth/token refresh, tenant base-URL resolution, CSP, caching) and trace root causes.
• Take part in code reviews, keep typecheck/lint/build green, write clear PR descriptions, and help raise test coverage in a codebase that currently has none.

Must-Have Qualifications

• B.E./B.Tech in Computer Science (or equivalent CS engineering degree) — required.
• 3–5 years of professional frontend development, with at least 2 years in React + TypeScript on a production product.
• Strong React fundamentals: rendering model, memoization, hooks discipline, Server vs Client Components, and why a component re-renders.
• Hands-on Next.js App Router experience (layouts, route groups, server components, API/route handlers, middleware).
• Solid TypeScript — strict mode, generics, typed API layers, no `any` by habit.
• State management at scale (Zustand, Redux or similar) and data-fetching patterns with Axios/fetch, interceptors and token refresh.
• Comfort with CSS architecture: SCSS Modules, design tokens, responsive layouts, and a component library such as MUI.
• Strong debugging skills — browser DevTools, React Profiler, network traces; able to isolate and fix issues in a large codebase you didn't write.
• Strong analytical and logical reasoning — handles date/time, timezone and scheduling edge cases correctly and can defend design decisions.

Good to Have

• Performance work on large lists/grids: @tanstack/react-virtual, Web Workers, canvas or similar.
• Drag-and-drop UIs (@hello-pangea/dnd, react-dnd), rich-text editors (TipTap), charts (Recharts), or data grids (AG Grid).
• Experience with multi-tenant SaaS, auth flows (JWT refresh rotation, OTP), CSP/security headers, and frontend VAPT fixes.
• Exposure to BFF/route-handler work in Next.js: third-party integrations (Zoho Desk, Google Maps/Sheets), rate limiting, streaming AI chat with the Vercel AI SDK.
• Testing: React Testing Library, Playwright or Vitest; helping set up a test culture from scratch.
• Node.js deployment basics (pm2, Cloudflare/OpenNext, CDN cache invalidation) and Git-based review workflows with conventional commits.

What We're Looking For (Mindset)

• A problem-solver who treats a flaky drag interaction or a 5-hour timezone drift as a puzzle, not a chore.
• Someone who reads existing patterns before inventing new ones, and asks why before how.
• Strong ownership — sees features through from design proposal to verified production behaviour.
• A clear communicator who can explain technical trade-offs to backend, product and design peers.

To apply, share your resume along with a brief note on a performance or state-management problem you solved in a React app and how you approached it.