*Hi,* *This is Manohar from IndSoft, Inc*
*One of our client is looking for Front end AEM Developer. Please share your consultant resumes to [email protected] <[email protected]>* *Position: Front End AEM Developer* *Client:* Fortune 100 Client- Client name will be given upon submission *Length:* 6-month rolling contract with likely extensions for another 6 months *Interview Process*: 2 30 –minute Video Interviews *Location:* 100% remote for duration of contract *Any visa is fine but no Transfers* *Don’t submit only AEM Resumes need strong experience in Front End * *Please check with your consultant before submitting* *Max rate: $53/h on C2C* *What are the top 3 MUST HAVE technologies?* Front End Focused AEM Development Experience working in a dynamic environment 2-3 years of AEM Development experience *NICE TO HAVES (OR WHAT GETS THE WIN)?* C# background REST API experience Enterprise Level experience JavaScript 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 3 rd party -- You received this message because you are subscribed to "rtc-linux". Membership options at http://groups.google.com/group/rtc-linux . Please read http://groups.google.com/group/rtc-linux/web/checklist before submitting a driver. --- You received this message because you are subscribed to the Google Groups "rtc-linux" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rtc-linux/CAPY1naE-2-FL2YwgCdzQUS4%3DJ85gm_QOs9a_gdXb7QShJ-zJjg%40mail.gmail.com.
