Senior React/Next.js Engineer

Senior React/Next.js Engineer

Mangaluru, Karnataka | Onsite | Full-time

About the role

Delivery is organised into small, senior pods who own a client outcome end to end: scope, architecture, delivery, quality, and production. AI coding agents are an integral part of the delivery workflow, and much of the implementation is agent-generated. The value of this role lies in the work that surrounds generation: decomposing ambiguous business problems into buildable specifications, making architectural decisions, directing agents against those decisions, and ensuring that everything shipped meets production standards.

This position owns the web client of a multi-product consumer platform shipped across several regions: rendering and caching strategy, Core Web Vitals, the component and design-system layer, SEO, localisation, and front-end security. The role is problem-driven rather than ticket-driven. Most engagements are delivered on fixed-timeline terms, so scoping and estimation quality has a direct bearing on project outcomes. The emphasis throughout is on engineering judgment.

AI-augmented delivery: expectations

•    AI coding agents are used daily as a core part of delivery. The critical skills are the specification that goes into generation and the review that follows it.

•    Full ownership is expected for all code shipped under this role, regardless of how it was produced. Accountability for correctness, security, and maintainability rests with the engineer, not the tool.

•    A key competency is identifying code that appears correct but is not: output that compiles, passes the happy path, and yet conflicts with framework fundamentals, introduces security exposure, or degrades at scale.

•    All AI-assisted work is expected to be fully explainable and debuggable by the engineer who ships it.

Key responsibilities

•    Outcome ownership: scoping, architecture, agent-directed implementation, review, testing, and release for web features, delivered end to end.

•    Rendering and caching strategy: per-route selection between static, incremental, server-rendered, and client-rendered approaches, with a clear understanding of the cost of each. Performance budgets (Core Web Vitals, bundle size, TTFB) are defined, defended, and verified through profiling.

•    Component architecture and design system: features are built from shared primitives rather than one-off markup, so that generated code lands within a coherent system.

•    SEO, metadata, and localisation: crawlability, structured data, canonical URLs, sitemaps, and multi-region routing maintained without forking the codebase.

•    Front-end security posture: CSP, XSS and CSRF defences, safe session and token handling, secrets kept server-side, and closure of VAPT findings. Generated code is treated as an additional review surface for security.

•    API boundary: shaping the contract with the back end, flagging API designs that would force poor rendering choices, and handling auth, real-time updates, error and empty states, and optimistic UI to a production standard.

•    Review, mentoring, and standards: pull requests and agent output reviewed with the same rigour; mentoring of junior engineers within the pod; conventions and reference patterns documented for wider team use.

•    Scoping and estimation: estimates prepared with care and stood behind, given the direct relationship between scope quality and commercial outcomes on fixed-price work.

Required skills and experience

•    Framework depth: deep production Next.js and React experience on applications shipped and maintained over time. App Router, server components, streaming and suspense, static and incremental generation, server actions, and route handlers.

•    Understanding beneath the API surface: hydration, the client-server boundary, unintended client-component conversion, and debugging stale pages across framework cache layers, CDN, and HTTP headers. Review quality at this level is what distinguishes the role.

•    Strong TypeScript: the type system used to prevent bugs rather than to satisfy the compiler.

•    Breadth of fundamentals: HTTP, state, data modelling, concurrency, and security fundamentals strong enough to review work at the API and data layer the client consumes. Pods are small, and review responsibility extends across adjacent layers.

•    Performance engineering: Core Web Vitals, code splitting, bundle analysis, image and font optimisation, and reduction of unnecessary JavaScript.

•    State and data management: deliberate separation of server and client state, caching and invalidation, and forms and validation, with clear reasoning behind each choice.

•    Accessibility and internationalisation: semantic markup, keyboard navigation, focus management, ARIA where genuinely needed, and internationalised layouts that hold up across languages.

•    Testing: component and end-to-end tests as part of normal delivery, with clear judgment on what is worth testing.

•    Independent execution: the ability to take an ambiguous requirement, clarify what is actually needed, document it clearly enough for others (or agents) to execute, and deliver without close supervision.

Good to have

•    Deploying and operating Next.js outside a managed host: containers, self-hosted builds, and an understanding of what the platform layer provides.

•    CI/CD for front end: preview deployments, automated checks, staged rollouts, and feature flags.

•    Front-end observability: real user monitoring, error tracking, and session replay.

•    Data privacy in practice: consent management that genuinely gates what it claims to, auditing of third-party scripts, PII kept out of URLs, analytics, and logs; familiarity with GDPR and India's DPDP Act.

•    Monorepo tooling and shared packages across web and other clients.

•    Design-system or component-library ownership, including documentation and versioning.

•    Analytics, experimentation, and A/B testing infrastructure.

What the role offers

Competitive salary based on experience, direct ownership of technical decisions on the web client, fast delivery cycles supported by AI-augmented workflows, and a small senior team environment where engineering judgment is the primary contribution.

How to apply

Please send a resume along with links to [Confidential Information] shipped work, live sites, GitHub, or both.