Job Summary
Veeva Solution Architect
• 5-8 years of experience in solution design/architecture roles within enterprise platform delivery, with hands-on Veeva Vault background (configuration and/or integration) strongly preferred.
• Working knowledge across both configuration (objects, lifecycles, workflows) and integration (Vault-to-Vault Connections, MuleSoft/API-based integration) domains — enough breadth to translate architecture intent into both types of solution design.
• Experience producing solution design documentation (design specs, data flow/sequence diagrams) to a standard that hands-on delivery teams can build from without further clarification.
• Experience working in a regulated (GxP) environment and awareness of how architecture decisions affect validation scope.
• Comfortable operating as an intermediary — translating senior architecture direction to delivery teams and surfacing delivery-team questions back up, rather than working in isolation.
• Demonstrated experience holding delegated technical decision authority on behalf of a more senior architect - able to decide confidently inside a defined boundary, and disciplined about escalating outside it. Candidates who default to escalating every decision are not suitable for this role.
• Working knowledge of native Vault-to-Vault Connections and Spark messaging alongside MuleSoft, sufficient to reason about which route a given cross-vault requirement should take.
• Experience in Agile/Scrum delivery, providing design input at sprint/story level.
• Strong English communication skills, both written (design docs) and verbal (day-to-day delivery team support).
Key Responsibilities
Veeva Solution Architect
• 5-8 years of experience in solution design/architecture roles within enterprise platform delivery, with hands-on Veeva Vault background (configuration and/or integration) strongly preferred.
• Working knowledge across both configuration (objects, lifecycles, workflows) and integration (Vault-to-Vault Connections, MuleSoft/API-based integration) domains — enough breadth to translate architecture intent into both types of solution design.
• Experience producing solution design documentation (design specs, data flow/sequence diagrams) to a standard that hands-on delivery teams can build from without further clarification.
• Experience working in a regulated (GxP) environment and awareness of how architecture decisions affect validation scope.
• Comfortable operating as an intermediary — translating senior architecture direction to delivery teams and surfacing delivery-team questions back up, rather than working in isolation.
• Demonstrated experience holding delegated technical decision authority on behalf of a more senior architect - able to decide confidently inside a defined boundary, and disciplined about escalating outside it. Candidates who default to escalating every decision are not suitable for this role.
• Working knowledge of native Vault-to-Vault Connections and Spark messaging alongside MuleSoft, sufficient to reason about which route a given cross-vault requirement should take.
• Experience in Agile/Scrum delivery, providing design input at sprint/story level.
• Strong English communication skills, both written (design docs) and verbal (day-to-day delivery team support).