The Backend Developer – Adobe Experience Manager (AEM) will design, develop, test, and maintain backend solutions for AEM-based applications. The role requires strong hands-on experience in Java, Apache Sling, OSGi, JCR, AEM APIs, integrations, and AEM as a Cloud Service. The position holder will contribute to reliable, scalable, secure, and maintainable backend services while working closely with project teams and stakeholders to deliver high-quality digital solutions.

Responsibilities:

Core/Primary:

• Design, develop, and maintain backend services and custom AEM functionality using Java, OSGi, Sling Models, Sling Servlets, and Sling Schedulers
• Develop secure and efficient content and repository operations using JCR, ResourceResolver, and AEM APIs
• Build and support integrations between AEM and third-party platforms, services, and data sources
• Create automated unit tests using JUnit, Mockito, and AEM/Sling Mocks to ensure code quality and maintainability
• Troubleshoot backend issues and optimize AEM code for performance, reliability, security, and scalability
• Manage builds, dependencies, source control, and code reviews using Maven and Git
• Support deployments, quality gates, and environment operations through AEM Cloud Manager for AEM as a Cloud Service

Marginal/Secondary:

• Participate in code reviews and provide feedback to improve code quality, maintainability, and adherence to development standards
• Collaborate with frontend developers, QA team members, and project stakeholders to clarify technical requirements and resolve implementation issues
• Support documentation of technical design, backend implementation details, and deployment-related changes

Other:

• Stay updated on AEM, Java, cloud development, security, and integration best practices to support continuous improvement
• Contribute to internal knowledge sharing, process improvements, and team learning activities when required

Technical Qualifications:

• Hands-on experience working with Adobe Experience Manager (AEM), Java, OSGi, Sling Models, Sling Servlets, Sling Schedulers, JCR, ResourceResolver, and AEM APIs
• Experience building and supporting integrations between AEM and third-party platforms, services, and data sources
• Experience writing automated unit tests using JUnit, Mockito, and AEM/Sling Mocks
• Experience with AEM as a Cloud Service and Adobe Cloud Manager, including build pipelines and deployments
• Proficient: Proficient in backend development using Java, OSGi services, Sling Models, Sling Servlets, and repository operations
• Proficient with Maven for build and dependency management and Git for version control
• Proficient in troubleshooting backend issues and optimizing AEM code for performance, reliability, security, and scalability
• Knowledge/Understanding: Knowledge of Agile development practices and collaborative delivery environments
• Understanding of development standards, secure coding practices, cloud-based deployment processes, and maintainable backend architecture

Personal Skills:

• Ability to work independently, manage assigned tasks, and deliver results with minimal supervision
• Ability to analyze and troubleshoot complex backend development and AEM integration challenges
• Ability to communicate technical solutions clearly and collaborate effectively with technical and non-technical stakeholders
• Ability to maintain attention to detail and ensure accuracy, quality, and consistency in development work
• Ability to adapt to changing priorities and work effectively in a fast-paced project environment
• Ability to work effectively within a team, share knowledge with peers, and support collaborative problem-solving

Education and Work Experience:

• Bachelor’s degree in Computer Science, Information Technology, Engineering, or a related scientific discipline is preferred, or an equivalent combination of education and experience
• Minimum of 3 years of relevant backend development experience, including hands-on experience with AEM backend development, Java, OSGi, Sling, JCR, AEM APIs, integrations, and cloud-based AEM deployments