Bajaj Finserv
Website:
bajajfinserv.in
Job details:
Location Name: NR Trident Tech Park
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) - AEM leads a single POD of 5-7 developers responsible for building and running the Adobe Experience Manager estate that powers this platform. Reporting to the Technical Architect - AEM, the role converts approved solution architecture into working, production-grade AEM implementations - components, templates, content fragments, workflows, DAM and Dispatcher - and is accountable for the POD's delivery predictability, code quality, platform hygiene 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
- 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 AEM applications in scope.
- Translate the solution design provided by the Technical Architect into implementable low-level designs, component specifications, API contracts and task breakdowns for the POD.
- Remain hands-on for a meaningful share of the role (target 30-40%) on AEM development using HTL, Sling Models, OSGi services, JCR queries, servlets, schedulers and custom workflows.
- Own the authoring experience delivered by the POD - editable templates, core and custom components, content fragments, experience fragments, tagging, taxonomy, metadata schemas and multi-site management.
- Implement and enforce the frameworks for caching, logging, exception handling and configuration management so that delivered code carries all the flavours of the core architecture defined earlier in the project lifecycle.
- Own integration of AEM with Content APIs, GraphQL and REST services, Adobe Dynamic Media and DAM, Adobe Target, Adobe Analytics / Launch, and the notification and personalisation frameworks in scope for the POD.
- Own Dispatcher and CDN behaviour for the POD's pages - cache rules, TTLs, invalidation and Akamai Fast Purge - and ensure cache correctness on every release.
- Maintain author and publish instance hygiene for the POD's applications: replication agents, package management, Oak index design and tuning, workflow and version purge, and repository growth control.
- Drive release readiness through build checklists, deployment runbooks, rollback plans and production hypercare for every deployment.
- Ensure the POD's digital assets continue to perform through peak sales season by planning for scale, graceful degradation and correct data flow across AEM, Dispatcher, CDN and origin.
- Engineering Quality and Code Governance
- Define and enforce coding standards, branching strategy, peer review, merge and promotion discipline across the POD using Git, Maven, Cloud Manager, Jenkins and GitHub Actions.
- Own quality gates - SonarQube, code coverage, static analysis and automated security scanning - and hold the line on defect density, escaped defects and rework metrics for the POD.
- Ensure unit test coverage using JUnit and AEM Mocks, and functional and regression automation coverage in partnership with QA, before any release is certified.
- Maintain a visible technical debt register for the POD's codebase with an agreed remediation plan, balancing delivery speed against long-term system health.
- Enforce performance, SEO and accessibility budgets on pages delivered by the POD, including Core Web Vitals thresholds, structured data correctness and WCAG 2.2 AA conformance.
- Enforce engineering hygiene in both process and code, and codify recurring learnings into SOPs and reusable patterns for the wider engineering group.|5. Innovation and Engineering Productivity
- Execute POCs to validate technology choices, upgrade paths and migration approaches 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 content operations automation - with measurable impact on velocity and quality and with clear guardrails on data, IP and security.
- Identify and automate repetitive build, content operations and release activities to reduce manual effort and cycle time.
- Leverage and sponsor innovation work through internal incubators and the external start-up network to introduce novel technical capabilities into the platform.|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 new 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.
- 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.
- Content Governance: Ensure author access control, approval workflows and maker-checker gates are correctly implemented for regulated and disclosure-sensitive content journeys.
- 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.
Key Decisions / Dimensions
Following Decisions Are Taken By The Role
- Low-level design and component design decisions within the boundaries of the architecture approved by the Technical Architect.
- Implementation approach for AEM components, templates, workflows, content models and integration 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 quality gates that block a release.
- Dispatcher, cache and invalidation configuration for the POD's applications, in partnership with infrastructure and CDN teams.
- Release go / no-go recommendation for the POD, along with the build checklist for every deployment to maintain hygiene on production servers.
- Technical debt prioritisation within the POD's backlog and the sequencing of remediation.
- 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
- Balancing new feature delivery against upgrade, migration and platform hygiene work on a large legacy AEM estate serving 30,000+ pages.
- Maintaining cache correctness, publish performance and repository health as content volume and authoring concurrency continue to grow.
- 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
- Qualifications
- Tech / B.E. - Computer Science or equivalent Engineering discipline
Post-graduation preferably from a Tier 1 college is an added advantage
- Work Experience
- Core Requirement: 5-7 years of web development experience with a minimum of 3 years hands-on on AEM 6.5+ or AEM as a Cloud Service, including at least 2 years leading a team of 5 or more developers.
- AEM Expertise: Strong hands-on experience with components, editable templates, HTL, Sling Models, OSGi services, JCR, taxonomy and metadata management, tagging, forward and reverse replication, workflows, content publishing and unpublishing, Oak indexing, and content migration and planning.
- Java and Backend: Strong Core Java / JEE, REST and SOAP web services development, and working knowledge of XML, XSL and server-side programming models used in Java-centric CMS platforms.
- Frontend Integration: Working knowledge of HTML5, CSS3, JavaScript ES6+ and integration with modern frameworks such as React JS, Next.js and Solid JS; ability to review frontend code delivered within the POD.
- Adobe Ecosystem: Hands-on with Adobe Dynamic Media / Scene 7, DAM, Adobe Target, Adobe Analytics and Launch / DTM; knowledge of Adobe I/O Runtime and Adobe I/O Events is an added advantage.
- Infrastructure and Delivery: Dispatcher configuration, Apache, load balancers, CDN (Akamai preferred), publish and author capacity planning, S3 / blob based data stores, and disaster recovery concepts.
- Cloud and DevOps: Experience with AWS or Azure, containerisation, and CI/CD using Maven, Git, Cloud Manager, Jenkins or GitHub Actions, including release systems, code merging and promotion.
- Quality Assurance: Continuous integration quality processes, SonarQube, manual and automated code review, JUnit and AEM Mocks, and automation testing strategy.
- System Properties: Delivering solutions that account for SEO and GEO, accessibility (A, AA, AAA), monitoring and RUM (New Relic, Datadog, Lighthouse CI), scalability, security, performance and responsive behaviour.
- Performance and Security Testing: Exposure to performance and security testing for web and app platforms, including load model creation and the OWASP Top 10.
- AI Engineering Depth (mandatory): Must have built with AI rather than only consumed AI tools - for example LLM-based automation, agentic coding harnesses, evaluation pipelines or AI-assisted content and code workflows - and must be able to explain design choices, guardrails and measured outcomes.
- Ways of Working: Agile and Scaled Agile delivery, DevSecOps practices, and a continuous improvement mindset; experience with JIRA or Azure DevOps.
- Domain: BFSI, Fintech or Ecommerce experience is strongly preferred, with an understanding of security, risk and compliance management in a regulated delivery environment.
- Certification: Adobe Certified Expert / Master in AEM Sites is preferred.
- Leadership: Proven ability to mentor developers, run performance conversations, manage partner resources and drive delivery predictability within a POD.
Skill Keywords
Adobe Experience Manager (AEM 6.5+, AEMaaCS), HTL, Sling Models, OSGi, JCR, Oak Indexing, Dispatcher, Java, JEE, REST, GraphQL, Content Fragments, Experience Fragments, Editable Templates, Multi Site Manager, DAM, Adobe Dynamic Media, Adobe Target, Adobe Analytics, Adobe Launch, Adobe I/O Runtime, Maven, Git, Cloud Manager, Jenkins, GitHub Actions, CI/CD, SonarQube, JUnit, AEM Mocks, Akamai, CDN and Caching, AWS, Azure, Core Web Vitals, SEO, GEO, Accessibility (WCAG), New Relic, Datadog, OWASP Top 10, Secure SDLC, Agile / Scrum, Team Leadership, Code Review, Technical Debt Management, AI-Assisted Engineering, GitHub Copilot, Agentic Coding.
Click on Apply to know more.