Back End Developer (Adobe Experience Manager)

Nivel cariera

Middle (2-5 ani), Senior (5-10 ani)

Limbi vorbite

engleză

Adresa/ adresele jobului


IBM is looking for Back-end developers to work in Agile projects based on Adobe Experience Manager.

Our client is major Oil and Energy provider with operations all over the world that started a digital transformation program. IBM Interactive Experience (iX) will work with the client on this journey, to shape new demands, to create and develop an environment that enables innovation and the rapid testing of ideas (fail fast, learn fast), to set up the tools, methods and approaches for the client to create a sustainable and cost effective digital capability and deliver against an initial set of Minimum Viable Products (MVPs).

Responsibilities:

&bullData migration from legacy systems

&bullData modeling in the JCR

&bullEnsure integration with other backend systems if needed (.: Create nodes in JCR based on the financial stock data retrieved from a web-service, etc.)

&bullCreate and execute Junit tests

&bullUse Sling scheduling to schedule jobs periodically

&bullCreate config nodes to store OSGI data

&bullCreate and/or adapt AEM workflows based on the functional requirements received from the PO

&bullWriting Sling Servlets / Events

&bullUse JCR observation to listen for an event

&bullImplement business logic in Java classes that can be called from Sightly

&bullModify users and groups, modify permissions using code

 

Remark: This is just a high-level list with possible activities which can be encountered during an AEM developer role. A more accurate activities list can be specified only after requirements analysis. The same observation is valid also for the Front-end profile activities section.

 

Required:

&bullAEM basic Developer training

&bullJava SE, Java EE (Servlet), Sling (AEM training also covers an introduction to Sling), Junit

&bullJCR

&bullDatabases / SQL (can be needed for integrating with legacy database systems or for data migra-tion)

&bullJunit

&bullNice to have: OSGI, Sling, Web services (possible to be needed during integration with other services), EasyMock (to create JCR objects for testing purposes)