Job Purpose
Bajaj Finserv Web is a critical component of the company's omnipresence strategy. You will be working with India's largest NBFC's web technology stack, encompassing over 40 business lines and 230+ features, with nearly 500 million traffic and managing over 30,000 webpages.
It is an integrated platform offering a portfolio of products covering payments, cards, wallets, loans, deposits, mutual funds, and loans on lifestyle products, ranging from consumer durables to home furnishings.
The Software Development Manager (SDM) - Full Stack leads a single POD of 5-7 developers building the experience and services layer of this platform on Next.js, React and Node JS. Reporting to the Technical Architect - Frontend, the role converts approved architecture and design system standards into production-grade full stack implementations - server rendered and statically generated pages, shared components, BFF and API integration layers - and is accountable for the POD's delivery predictability, Core Web Vitals, code quality and compliance posture. The role is expected to remain hands-on, conduct code reviews, enforce engineering standards and SOPs, and continuously raise the productivity of the POD through automation and AI-assisted engineering.
Duties and Responsibilities
1. Core Development and Delivery
• Own end-to-end delivery for the POD - sprint planning, estimation, build, code review, testing, release and post-release stabilisation - for all web and in-app surfaces in scope.
• Translate the solution design provided by the Technical Architect into implementable low-level designs, component specifications, API and data contracts, and task breakdowns for the POD.
• Remain hands-on for a meaningful share of the role (target 30-40%) on Next.js and React development with TypeScript, including App Router, React Server Components, SSR, SSG, ISR and streaming.
• Own the POD's Node JS services and BFF layer - route handlers, API aggregation, GraphQL and REST consumption, caching, resilience patterns, timeouts and error handling.
• Consume and contribute to the enterprise design system and shared component library, ensuring token, theming, versioning and Storybook discipline rather than local forks and one-off components.
• Implement integration with headless content sources (AEM headless or other CMS/DXP), commerce and backend services through the contract layer defined by the Architect.
• Own state management, data fetching and form and validation architecture within the POD's applications, keeping patterns consistent with the platform standard.
• Own edge and caching behaviour for the POD's routes in partnership with CDN teams - cache key design, revalidation, purge strategy and origin protection across Akamai and Cloudflare.
• Drive release readiness through build checklists, feature flag and progressive rollout plans, deployment runbooks, rollback plans and production hypercare for every deployment.
• Ensure the POD's digital assets continue to perform through peak sales season by designing for auto-scale, graceful degradation and resilient rendering across the Node / SSR tier, CDN and origin.
2. Engineering Quality and Performance Governance
• Define and enforce coding standards, branching strategy, peer review, merge and promotion discipline across the POD using Git, GitHub Actions or Jenkins, and monorepo and package governance conventions.
• Own quality gates - SonarQube, static analysis, code coverage, bundle size checks, Lighthouse CI budgets and automated security scanning - and hold the line on defect density and escaped defects.
• Own the POD's Core Web Vitals outcomes (LCP, INP, CLS) including bundle analysis and code splitting, image and font strategy, hydration cost, streaming and partial prerendering, with explicit optimisation for low-end Android devices, low bandwidth networks and in-app webviews.
• Ensure testing coverage across unit, component, contract and end-to-end layers using Jest, Testing Library, Playwright or Cypress, along with visual regression, before any release is certified.
• Own SEO, GEO, structured data, render parity and accessibility (WCAG 2.2 AA)



as build-time concerns for the POD rather than post-release corrections.|• Maintain a visible technical debt and dependency upgrade register for the POD's codebase with an agreed remediation plan, including supply chain risk across the dependency tree.
• Establish frontend observability for the POD - real user monitoring, synthetic checks and error tracking through New Relic, Datadog and Lighthouse CI - and act on the telemetry.
3. POD and Team Management
• Technical Mentorship: Provide day to day technical guidance to 5-7 developers, run design and code walkthroughs, and build depth in the POD through structured learning paths and pair programming.
• Performance Management: Set clear, measurable goals for every team member, conduct regular one-on-ones and reviews, give constructive feedback, and close the appraisal cycle within timelines.
• Capacity and Resource Planning: Allocate work across the POD based on story complexity, skill fit and individual development needs, maintain sprint velocity and utilisation, and flag capacity risks to the Technical Architect early.
• Talent Acquisition and Retention: Participate in hiring panels, own the technical evaluation of candidates for the POD, and run structured onboarding and ramp-up plans for recent joiners, byte hires and partner resources.
• Partner Management: Manage in-POD vendor and partner developers to the same standard of quality, hygiene and delivery discipline as internal engineers.
• Team Collaboration: Build a cohesive POD with strong communication into Product, Design, Content, QA and infrastructure teams, and maintain high engagement and morale.|4. Compliance and Security
• Data Privacy and Security: Ensure all development within the POD complies with applicable data privacy regulation, RBI and internal information security policy, including data localisation requirements for any cloud or AI service used.
• Secure SDLC: Enforce secure coding practices covering the OWASP Top 10, dependency and supply chain scanning, secrets management, and timely closure of VAPT and application security findings.
• Browser and Client Security: Ensure correct implementation of CSP, XSS and CSRF protection, secure token and session handling in the browser, and governance of third-party scripts and tags on the POD's surfaces.
• Audit Readiness: Maintain traceability from requirement to code to release - approvals, change records, test evidence and deployment records - so that internal audit and regulatory reviews can be served without rework.
• Incident Management: Own the POD's participation in production incident response, root cause analysis and preventive action tracking, ensuring minimal customer impact.
5. Innovation and Engineering Productivity
• Execute POCs to validate frameworks, rendering approaches and migration paths with clear benchmarking on performance, cost and scalability before adoption.
• Drive adoption of AI-assisted and agentic engineering within the POD - code generation, review assistance, test generation and design-to-code workflows - with measurable impact on velocity and quality and with clear guardrails on data, IP and security.
• Support the migration of the existing CMS rendered estate to a composable Next.js frontend for the POD's scope, ensuring zero regression on organic traffic, analytics and compliance sensitive journeys.
• Leverage and sponsor innovation work through internal incubators and the external start-up network to introduce novel technical capabilities into the platform.
Key Decisions / Dimensions
Following decisions are taken by the role:
• Low-level design and component design decisions within the boundaries of the architecture and design system standards approved by the Technical Architect.
• Rendering mode selection per route - SSR,



SSG, ISR or client rendering - within the strategy defined by the Architect.
• Implementation approach for BFF and API integration, state management, error handling and resilience patterns for the POD's scope.
• Sprint scope, story sequencing, estimation and allocation of work across the 5-7 developers in the POD.
• Code acceptance - approval or rejection of pull requests, and the performance and quality gates that block a release.
• Cache key, revalidation and purge configuration for the POD's routes, in partnership with infrastructure and CDN teams.
• Release go / no-go recommendation for the POD, including feature flag and progressive rollout decisions, and the build checklist for every deployment.
• Technical debt and dependency upgrade prioritisation within the POD's backlog.
• Onboarding and offloading of partner and internal resources based on POD delivery requirements.
• Escalation of architectural exceptions, cross-POD dependencies and risks to the Technical Architect.
Major Challenges
• Holding Core Web Vitals and conversion outcomes while delivering rich personalisation and marketing-driven change at a high release cadence.
• Delivering consistent experience across low-end Android devices, low bandwidth networks, in-app webviews and desktop.
• Sustaining design system adoption and architectural consistency within the POD when timelines push teams toward local shortcuts.
• Delivering a continuous release cadence across 40+ business lines while holding quality, performance and compliance standards with a POD of 5-7 developers.
• Working across cross-functional teams - Product, Design, Content, Data, Marketing and infrastructure - where dependencies frequently sit outside the POD's direct control.
• Gaining and maintaining a deep understanding of new financial products and regulatory obligations in order to build business-driven, compliant solutions.
• Continuously evolving systems and technologies within minimum time to manage growing business volumes and peak season traffic.
• Constant upskilling of the POD, including byte hires and new joiners, without losing sprint velocity.
Required Qualifications and Experience
a) Qualifications
B. Tech / B.E. - Computer Science or equivalent Engineering discipline
Post-graduation preferably from a Tier 1 college is an added advantage

b) Work Experience
• Core Requirement: 5-7 years of software development experience with a minimum of 3 years hands-on on React JS and Next.js with TypeScript, plus Node JS backend or BFF development, including at least 2 years leading a team of 5 or more developers.
• Primary Technical Expertise: Strong command of React (hooks, context, concurrent rendering, performance profiling) and Next.js (App Router, React Server Components, SSR / SSG / ISR, middleware, route handlers, caching and revalidation).
• Backend and Integration: Node JS service development, BFF patterns, REST and GraphQL API design and consumption, authentication and session handling, and integration with headless CMS or DXP platforms such as AEM headless, Sanity or Contentful.
• Core Frontend Skills: HTML5, CSS3 and modern CSS architecture (Tailwind, CSS Modules, CSS-in-JS), semantic markup, responsive and adaptive design, cross-browser and in-app webview behaviour.
• Engineering Foundations: State management and data fetching patterns (TanStack Query, Zustand, Redux, SWR), form and validation architecture, and monorepo and package management discipline.
• Design System: Experience building or contributing to a shared component library with design tokens, theming, Storybook, versioning and semantic release across multiple teams.
• Performance: Demonstrable track record on Core Web Vitals (LCP, INP, CLS), bundle analysis and code splitting, image and font optimisation, hydration cost reduction, streaming and partial prerendering, and performance budgets enforced in CI.
• Edge and Delivery: Hands-on with CDN and edge platforms (Akamai, Cloudflare), caching and purge strategy, edge functions and workers, and hosting models such as OpenNext, containerised Node or serverless.

📌 System Analyst (Bengaluru)
🏢 Bajaj Finance
📍 Bengaluru