CRM Architect

Posted 4 days 19 hours ago by eTeam

Permanent
Not Specified
Other
Utrecht, Netherlands
Job Description

Description:


- Senior level CRM architect/lead consultant 8+ years of project-based experience (with focus on technical knowledge. Functional knowledge is also very relevant in connection with research, correct solution direction and support CRM team);

- Knowledge and having applied Azure Pipelines (being able to set up/adjust Azure Pipelines) in combination with Azure Pipelines. Bicep scripts;

- Knowledge of (CRM) solution management, and experience with the use of minimal solutions;

- Knowledge of LogicApps, Azure functions, Plug-ins and Contrainer app. microservice architecture to be able to make the right technical considerations;

• Reviewing various code changes (peer reviews);

• Knowledge of the Azure platform.

- Writing technical designs (SaaS as well as PaaS components);

• Experience with ArchiMate modeling (would be useful but not a must).

- Knowledge of PowerAutomate flows that have a high degree of complexity (to be able to implement optimizations and/or solve problems);

- Knowledge and have applied of setting up Dynamics 365 environments including associated components (integrations, addons, security groups and azure servicebus);

- Knowledge of Dynamics 365 data migrations to support the data migration team;

- Ensuring that the Dynamics 365 environments are equipped with the correct software (versions) across the entire OTAP street;

- High degree of problem-solving skills, various critical (functional and technical) bugs come to the tech-lead to be resolved;

- Identify continuous improvements and tech debt, which will be worked on together with the CRM developers;

- The right degree of flexibility. The release of Dynamics 365 and related components happens 1-2 weekly outside office hours (where the tech lead takes the lead);

- Participate in a number of periodic meetings such as release management (where the tech lead estimates which CRM components will be released and which will not be released without getting in each other's way) and participation in architecture meetings where new initiatives (patterns/processes/techniques) are discussed.