*Job Title* *Adobe Experience Manager (AEM) Technical Lead/Architect*
*Relevant Experience& Experience Required* *(in Yrs)* *9-10 years* *Key words to search in resume* * leading development and maintenance of CMS capabilities & lead the support and maintenance of Marketing IT Portals with Integrations with backend systems* *Technical/Functional Skills** -MUST HAVE SKILLS* *Knowledge on following products/systems: * - Total 9-10 years of experience leading development, gathering and writing authoring requirements in CMS capabilities - 5+ years business consulting & development experience with AEM/CQ5 - 5+ years of experience with Agile SCRUM development - Experience with production support of content and content management systems - Experience with content entry - Experience with a complex software release process and environment - Communicating CMS and content entry process to business units and content teams - OpenTextTeamSite experience a nice to have *Roles & Responsibilities* *Position Description: * *9-10 years of experience in leading development and maintenance of CMS capabilities. The scope is to lead the support and maintenance of Marketing IT Portals with Integrations with backend systems (specifically for Global Enterprise Support Portal for external users - developed using AEM 6.1 and API Integrations with Services systems) * *Essential Skills - Mandatory:* - Solid experience with CQ5 building blocks including templates, components, dialogs, widgets and bundles. - Experience on Java Content Repository (API) suite, Sling web framework and Apache Felix OSGi framework, DAM, Workflows is required. - Migration into AEM from other CMS (OpenText aka Vignette) - Provide technical mentorship to the offshore team. - Work with project managers to ensure that all project deliverables are on time and high quality - Work collaboratively with other teams; QA, UX, etc - Assist in deploying applications to Dev, QA, Production environments - Create standards for authoring including: authoring dialogues, component names, component groups and template names for developers and agile product owners to use during development - Create authoring requirements during the design process. Add authoring requirements to UX designs comps and component designs - Evaluate existing component library and recommend improvements to authoring experience - Create detailed documentation on technical architecture, completed components and develop training materials/documentation for continued support — - Collaborate with Agile developers to arrange knowledge transfer sessions for completed components - Perform acceptance testing on components and authoring experience Collaborate with enterprise (especially marketing IT departments) on AEM capabilities, principles and best practices in digital publishing *Startdate** (dd-mmm-yy)* *30-Sep-2016* *Duration of assignment **(in Months)* *6 months* *Work Location**(State, City )* *Lincolnshire, IL* -- *vinod.ku...@nityo.com <vinod.ku...@nityo.com>* *Regards!!* *Vinod Kumar*Phone: 609-853-0818 Ext- *2168*Email:vinod.ku...@nityo.com www.nityo.com *Nityo Infotech Corp. * -- You received this message because you are subscribed to the Google Groups "Open Source Erp & Crm" group. To unsubscribe from this group and stop receiving emails from it, send an email to open-source-erp-crm+unsubscr...@googlegroups.com. To post to this group, send email to open-source-erp-crm@googlegroups.com. Visit this group at https://groups.google.com/group/open-source-erp-crm. For more options, visit https://groups.google.com/d/optout.
