| AEM Developer. at Remote, Remote, USA |
| Email: [email protected] |
| From: Benjamin Thomas, Concord it systems .INC [email protected] Reply to: [email protected] AEM Developer. Austin, TX Day 1 onsite USC/H4-EAD/L2EAD Only Please inform candidate there will be a coding test while the L1 interview. Job description: At least 3-5+ years with Core AEM projects only Overall Total Experience should be 6+ Strong Java programming foundation Extensive hands on workflows, Sling servlet, REST, JSON, Lucene indexing is must. Exposure to Coral / Granite UI, Adobe UI customization is a must Deep understanding of AEM's security along with its Access Controls Expertise around extending AEM's core functionalities such as Launches Must have worked on AEM 6.4 or newer versions. Working Experience with Sightly / Sling models . Strong understand of core AEM components such as oak, sling and dispatcher Experience with Continuous Integration and Automated test execution and building tools such as Jenkins, Hudson, Selenium or Maven Work with project managers to ensure that all project deliverables are on time and high quality Work collaboratively with other teams; QA, UX, etc Exceptionally good at document and explaining core technical processes. Other CMS experiences and a good understanding of the DXP area Prior experience is a strong plus Detailed points that will be covered as part of this JD 1. Front-end technologies - Touch UI - Sightly - Component, Content and experience fragment, editable templates, Client libs 2. AEM Technology stack (Backend ) - OSGI, JCR, Sling, WCM Api's, Sling Model - Workflow, workflow launcher, Event handler, Event listener, Scheduler, Sling Job - API integration - Multi-Site Manager setup - Query builder, Searching, Indexing, Session handling - Junit 3. Security - Access Control Lists (ACL), Single Sign On (SSO), Security layers 4. Performance Tuning - Page performance, Dispatcher caching - Query optimization - Debugging level 5. Infrastructure - Cronjob setup - Dispatcher setup - Apache setup 6. AEM Persistence setup 1. TarMK 2. MongoMK 3. S3 7. Build and deployment - Maven/Ant build, Jenkins, CI/CD pipeline - Production deployment 8. Language Java - Exception handling - Collection framework - Design pattern - Multi-threading 9. AEM upgrade - Service pack upgrade and Hot fix installation - AEM version upgrade - Pre-upgrade Analysis - Upgrade planning (In place/Content migration) - Post-upgrade process 10. Use case - Migration from Non-CMS - Headless CMS Approach - Integration with Other technology - Coding best practice Keywords: continuous integration continuous deployment quality analyst user interface user experience sthree information technology Texas AEM Developer. [email protected] |
| [email protected] View all |
| Thu Aug 08 20:53:00 UTC 2024 |