Hi,
Position: UI AEM Developer
Hope you are doing well,
Please go through the detailed job description, And let me know your interest.
Position: UI AEM Developer
Location: 100% remote
Duration: Long Term
Client/ Vendor: Apex
MUST HAVE technologies
1. Front End Focused AEM Development
2. Experience working in a dynamic environment
3. 2-3 years of AEM Development experience
NICE TO HAVES
1. C# background
2. REST API experience
3. Enterprise Level experience
4. JavaScript
5. HTML/CSS
* Working through transformation - consolidating front-end using AEM
(started over a year ago but didn't have the expertise for AEM - just
HTML/JavaScript) - wanting to use it for CMS not just for storing data and
need someone with more expertise to utilize full functionality on the dev
side
* Goal for AEM is to use no java though may have to introduce limited
Java-How to go about limiting use of Java?
* Position will work closely with the architect and management to
implement and code the design of the project (hands-on project)
* Note: Unlike many AEM teams they don't use JAVA (back-end is in
.NET) but looking for someone who has worked with AEM and this would be most
purely an AEM role (okay with whatever back-end they have familiarity with
if any - really won't need to touch and will be all front-end focused)
Day to Day Responsibilities/typical day look like:
* Will be all front-end focused (won't need to do any work with
back-end/DB)
* Mix of hands-on work and mentorship (code reviews, guidance to other
developers, etc.)
* Primary role is creating AEM components for teams/end-users (ask for
properties for bio etc.)
* Standard content pages (JCR)
* Static pages (authoring done by a different team but needs to
provide some of those tools - they want to create "templates")
* Data-driven pages
* Data-driven pages (small adapter that calls to REST API service
since they don't use JAVA/Sling)
* Eventually will be adding in analytics to the application
(experience with doing that in the past would be helpful)
* Using version AEM 6.5 (Siteleaf - not using the JSP version)
* Not as concerned with what version they have worked with but that
would be best
* Primarily using AEM as a CMS (content management system) not for the
DAM (digital asset management) side of things - most of that is provided by
a 3rd party
1. Front End Focused AEM Development
2. Experience working in a dynamic environment
3. 2-3 years of AEM Development experience
NICE TO HAVES
1. C# background
2. REST API experience
3. Enterprise Level experience
4. JavaScript
5. HTML/CSS
* Working through transformation - consolidating front-end using AEM
(started over a year ago but didn't have the expertise for AEM - just
HTML/JavaScript) - wanting to use it for CMS not just for storing data and
need someone with more expertise to utilize full functionality on the dev
side
* Goal for AEM is to use no java though may have to introduce limited
Java-How to go about limiting use of Java?
* Position will work closely with the architect and management to
implement and code the design of the project (hands-on project)
* Note: Unlike many AEM teams they don't use JAVA (back-end is in
.NET) but looking for someone who has worked with AEM and this would be most
purely an AEM role (okay with whatever back-end they have familiarity with
if any - really won't need to touch and will be all front-end focused)
Day to Day Responsibilities/typical day look like:
* Will be all front-end focused (won't need to do any work with
back-end/DB)
* Mix of hands-on work and mentorship (code reviews, guidance to other
developers, etc.)
* Primary role is creating AEM components for teams/end-users (ask for
properties for bio etc.)
* Standard content pages (JCR)
* Static pages (authoring done by a different team but needs to
provide some of those tools - they want to create "templates")
* Data-driven pages
* Data-driven pages (small adapter that calls to REST API service
since they don't use JAVA/Sling)
* Eventually will be adding in analytics to the application
(experience with doing that in the past would be helpful)
* Using version AEM 6.5 (Siteleaf - not using the JSP version)
* Not as concerned with what version they have worked with but that
would be best
* Primarily using AEM as a CMS (content management system) not for the
DAM (digital asset management) side of things - most of that is provided by
a 3rd party
Disclaimer
This electronic mail (including any attachments) may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic mail or its contents (including any attachments) by persons other than the intended recipient(s) is strictly prohibited. If you have received this message in error, please notify us immediately by reply e-mail or e-mail unsubscribe@imcsgroup.net so that we may correct our internal records. Please then delete the original message (including any attachments) in its entirety. Thank you
No comments:
Post a Comment
Thanks
Gigagiglet
gigagiglet.blogspot.com