AEM Developer

Title: AEM Developer

Location: Boston, MA (Local Preferred )

Onsite Requirements: 3 days onsite (Hybrid)

Start: ASAP

Duration:  6-10 months

MOI : Video

Job Description

·       5+ years of experience at minimum with AEM Development.

·       While this is primarily a backend role, the candidate must have some front-end experience for when needed.

·       Local to Boston and has strong interpersonal, communication (written and oral), and analytical skills.

·       This individual must be team-oriented and deadline driven

·       Financial services experience is a plus but not required

This is a mid-senior level role that will serve as an expert in AEM development. The ideal candidate would be local to Boston and has strong interpersonal, communication (written and oral), and analytical skills. This individual must be team-oriented and deadline driven. 5+ years of experience at minimum. While this is primarily a backend role, the candidate must have some front end experience for when needed. Financial services experience is a plus but not required.

1. Core Technical Skills

•        Java and J2EE: Proficiency in Java and Java-based frameworks (e.g., Spring, Hibernate) is essential.

•        Sling Framework: Understanding Apache Sling, which is the web application framework used by AEM to map request URLs to content resources.

•        OSGi Framework: Knowledge of OSGi (Open Services Gateway Initiative) for modular development and managing AEM bundles.

•        JCR (Java Content Repository): Familiarity with JCR, especially Apache Jackrabbit Oak, which is the repository used by AEM.

•        RESTful APIs: Experience in developing and consuming REST APIs for integrations with third-party systems.

•        HTL (HTML Template Language): Understanding of HTL (formerly Sightly), the templating language used in AEM.

2. AEM-Specific Knowledge

•        AEM Components Development: Ability to create and customize AEM components, templates, and dialogs.

•        Workflows: Experience in designing and implementing AEM workflows for automating content processes.

•        Dispatcher Configuration: Knowledge of configuring AEM Dispatcher for caching and load balancing.

•        Content Management: Familiarity with AEM content authoring, versioning, and publishing processes.

•        AEM Upgrades and Maintenance: Experience in upgrading AEM versions and maintaining the platform.

3. Frontend Integration

•        While primarily a backend role, some understanding of frontend technologies like HTML, CSS, and JavaScript is helpful for integrating backend services with the frontend.

Deep Chand