Software Development Engineer II (Frontend)
- Compensation
- Not disclosed
- Location
- Gurugram, HR, India
- Work setup
- Not specified
- Seniority
- Middle
- Employment
- Full time
- Experience
- 4+ years
- Category
- Frontend
- Posted
Skills
Must have
- 4–6 years building production React applications in TypeScript, including ownership of a large or long-lived codebase.
- Deep React knowledge: rendering and reconciliation, memoisation trade-offs, concurrent features, and diagnosing re-renders with the profiler.
- Strong server-state design with TanStack Query or equivalent: cache keys, invalidation, optimistic updates and consistency after mutations.
- Hands-on with schema-driven forms (react-hook-form + Zod or equivalent) and a utility-CSS / headless-component stack (Tailwind, shadcn/ui, Radix or similar).
- Proven frontend performance work at scale: code-splitting, virtualisation, bundle analysis and interaction latency.
- Has implemented RBAC or permission-gated UI, and understands why the backend must remain the source of truth.
- Understands multi-tenant data discipline: every view, request and cache key must be scoped to the right merchant.
- Enough backend to own an endpoint: Node.js, REST design, validation, SQL and indexes.
- Uses AI coding tools daily and productively, with the judgement to catch generated code that is incorrect, insecure or untested.
- Testing discipline across unit, integration and end-to-end tests, focused on behaviour rather than implementation.
- Designs the empty, loading, error and permission-denied states, not only the happy path, and thinks about what a screen does when the API is slow or returns half the data.
- Improves older code incrementally, argues for rewrites with data, and raises the bar for others through reviews and conventions.
Full description
About GoKwik
GoKwik is a growth operating system for D2C and eCommerce brands, enabling checkout optimization, RTO reduction, payments, retention, and post-purchase engagement. Today, GoKwik powers 15,000+ merchants globally, processes ~$2 billion in GMV, and continues to strengthen its AI-powered infrastructure across India, the UK, Europe, and the US.
Why This Role Matters
As a Senior Frontend Engineer on the Internal Admin Platform, you will own the console that GoKwik's operations, support and partner-management teams use every day to manage merchant accounts, applications, permissions and configuration. Our platform is multi-tenant: one system serves thousands of merchants, each with its own catalogue, orders, inventory, pricing and customers, and it handles millions of API calls every week. A developer ecosystem sits on top, where third parties build and publish apps that extend what merchants can do.
This is production engineering, not greenfield prototyping. The services you join already carry live traffic, real merchant data and third-party integrations that cannot break. The role owns architecture, not only screens: frontend conventions, performance budgets, role-based access across UI and API, and the backend endpoints the console depends on. Getting access control or merchant data scoping wrong is a security issue, not a UI bug.
The console is a React + TypeScript single-page app on Vite, built on a shared component library, with server state in TanStack Query and every form validated through Zod. An older shell still runs on a micro-frontend host with Redux and a different component library, and you will lead the move from one to the other. Where AI genuinely helps operators, such as search, summarisation or assisted triage, you will bring it into the console and design it so a human stays in control of its output.
What You'll Own
- Frontend Architecture - Own module boundaries, shared component and hook patterns, state ownership, and the conventions other engineers build on.
- Complex Admin Workflows - Build large data tables, server-side filtering, multi-step forms, bulk actions and audit-friendly detail views in React + TypeScript.
- Server State - Own server state end to end with TanStack Query: cache-key design, invalidation after writes, optimistic updates with rollback, and correct loading, empty, error and permission-denied states.
- Role-Based Access (RBAC) - Design and enforce access across UI and API, so permission rules are defined once, verified on the backend and tested in both places.
- Merchant Data Scoping - Ensure every screen, query and cache key is scoped to the right merchant, so one merchant's data never appears in another's view.
- Legacy Migration - Lead the incremental move from the legacy micro-frontend shell (Redux, older component library) to the modern Vite stack without breaking live users.