IBM WCS Engineer - London

IBM WCS Engineer

Department/Practice: Digital and Data

Job Purpose and primary objectives:

Hands on experience in IBM WCS and in depth understanding

2. Highly skilled with Java, J2EE and frameworks

3. Experience and knowledge of tools like Eclipse , RAD,GIT and other monitoring tools like Jira,Jenkins etc

4. Experience in databases like oracle & sql

5. Experience in Retail and ecommerce is a plus

Key responsibilities (please specify if the position is an individual one or part of a team):

The purpose of this role is to be a hands-on engineer mentor and coach lesser experienced engineers, helping to deliver the product vision that aligns to an overall technology strategy and supporting the engineering department as a whole in activities such as improving ways of working, community building and recruitment.

Our product is deployed to millions of users and so an understanding of how to build high-quality, reliable, thoroughly tested and performant software, in compliance with best practice coding standards and technical design, is a key part to the role. We want someone with an innovation mindset with excellent awareness of new technologies and a solid grasp on the full engineering stack that thrives in a collaborative product development and engineering environment

Key Skills/Knowledge:

hands-on experience in Salesforce Marketing Cloud development, implementing CRM solutions with good command on triggers, batch processes, APIs and web services

Experienced in using AMPscript within email templates and landing pages for personalisation and automation purposes.

Exposure developing Front end and Back end

Experienced in using Automation Studio and Journey Builder

Experience using Jira/agile tools, GIT

Experience in delivering projects in agile methodology

Additional remarks (if any):

You will serve as a platform specialist, focusing on all aspects of Salesforce Marketing Cloud, supporting the team to create emails and helping implement marketing campaigns using Salesforce Marketing Cloud.

Agile methodology follows on this project, therefore regular daily scrum, investment & retrospective meeting happen every week.

Low, medium & high priority tickets will be assigned to the resource, assigned tickets expected to close by the end of the sprint week. Sprint open & close every week.

Impact assessment will be required each time before the deployment or changes go live.

Organize UAT with business stakeholder.

Whenever it is needed meeting should schedule internal, external & third-party team members

Posted on : last year, #72, 2 views

It is ok to contact this poster with commercial interests.

Report as inappropriate