Key Responsibilities
The client is looking for a senior Veeva CRM Architect, strong integration strategy & implementation experience required
· Deep, hands-on expertise in Veeva CRM and Veeva Vault CRM architecture.
· strong integration strategy & implementation experience required
· Direct experience with Veeva CRM migration, ideally from the Salesforce-based platform to Vault CRM.
· Strong understanding of Veeva deployment packages, environment promotion, release operations, and technical upkeep.
· Experience designing DevOps, release-management, development, deployment, and support processes for enterprise platforms.
· Lead the technical architecture for migration from Salesforce-based Veeva CRM to Vault CRM.
· Define the migration approach, deployment path, technical controls, and methods for moving configuration and changes through environments.
· Establish a more mature operating model for development, releases, DevOps, QA, validation, and production support.
· Design and improve release-management practices, including Veeva deployment packages and repeatable promotion procedures.
· Partner with QA to define appropriate controls, procedures, and validation practices.
· Coach and teach internal technical resources so the organization can operate and maintain the platform effectively.
· Provide hands-on technical leadership while working with business, technical, QA, and implementation stakeholders.
Technical Environment and Scope
· Approximately 500 CRM users.
· Primary users include territory managers, marketing teams, and medical communications stakeholders.
· U.S. operations represent approximately 60% of the business.
· Veeva CRM is relatively standard but includes company-specific augmentations.
· Five data pipelines support representative data flows to the enterprise data lake.
· Drupal is used for content management.
· Reltio MDM is in place.
· Veeva OpenData connects with SAP.
· The role will address the operational management of the end-to-end landscape, including release and QA practices.
Primary Challenges to Address
· Technical change management and organizational maturity in the Veeva space.
· Lack of consistent DevOps and release-management practices.
· Limited tooling and repeatable processes for promoting changes after QA.
· Need for clear development, deployment, support, and validation paths.
· Need to build a high-performing team and sustainable support model.
· Process risk caused by ad hoc and inconsistent controls and procedures.
· Resource and user-adoption risks associated with the broader migration program.