Pharma2 Sr Solution Architect

Job Description

Senior Salesforce Solution Architect

Position Summary

The Senior Salesforce Solution Architect will provide end-to-end solution architecture leadership for a complex Salesforce platform optimization and modernization initiative.

The architect will establish the target-state architecture and provide technical governance across five primary workstreams:

• Storage and archival
• Trigger framework modernization
• QA automation
• Environment refresh and data masking
• Flow modernization

The role will partner closely with Salesforce developers, technical leads, QA, data, DevOps, business analysts, and project leadership to ensure solutions are scalable, maintainable, secure, and aligned with established Salesforce architecture standards.

The architect will support the engagement from discovery and architecture validation through sprint execution, testing, release readiness, hypercare, and technical transition.

Core Responsibilities

1. Solution Architecture & Technical Strategy

• Own the overall Salesforce solution architecture and ensure consistency across all workstreams.
• Translate business and technical requirements into scalable solution designs and implementation patterns.
• Assess the current Salesforce landscape, identify architectural risks and technical debt, and define appropriate modernization approaches.
• Establish target-state architecture, design principles, technical standards, and implementation guardrails.
• Evaluate solution options and document key architecture decisions, trade-offs, dependencies, and constraints.
• Ensure new solutions favor maintainability, scalability, platform-native capabilities, and appropriate separation of concerns.

2. Salesforce Automation Modernization

• Establish architectural standards for Apex triggers, Flow, and other Salesforce automation.
• Define a consistent trigger architecture, including bypass controls, execution management, error handling, and appropriate functional isolation.
• Guide modernization of legacy automation into maintainable Salesforce patterns.
• Define standards for migration from legacy Process Builder and Workflow Rule automation to Salesforce Flow.
• Review automation for duplication, unnecessary complexity, governor-limit exposure, recursion risks, and conflicting execution paths.
• Establish reusable patterns and governance to limit future accumulation of technical debt.

3. Data Lifecycle, Storage & Archival

• Define the architecture for Salesforce data retention, archival, and long-term storage.
• Assess object relationships and downstream dependencies that could be affected by archival.
• Establish patterns that preserve required access and application functionality while reducing unnecessary platform storage consumption.
• Define appropriate approaches for sandbox validation and controlled production archival.
• Partner with data and business stakeholders to translate retention requirements into viable technical designs.
• Ensure archival solutions account for integrations, reporting, analytics, automation, and other dependent platform capabilities.

4. Environment Strategy & Data Masking

• Define Salesforce environment-management and refresh architecture.
• Establish technical patterns for identifying and protecting sensitive data within non-production environments.
• Guide the design of repeatable data-masking and selective-refresh processes.
• Ensure environment strategies support development, QA, regression testing, integration testing, and release activities.
• Define technical validation criteria for environment refresh and masking processes.
• Identify dependencies between environment readiness and downstream testing or modernization activities.

5. Quality Engineering & DevOps Architecture

• Partner with QA and engineering teams to define a sustainable Salesforce automated-testing strategy.
• Establish architectural expectations for regression coverage of critical business processes.
• Define how automated testing integrates with Salesforce CI/CD pipelines.
• Support reusable test-data patterns and broader automation of quality controls.
• Establish appropriate technical quality gates for deployment and release readiness.
• Ensure development and release practices support traceability, repeatability, and controlled production deployment.

6. Architecture Governance & Design Authority

• Serve as the central architecture authority across the Salesforce modernization workstreams.
• Lead solution-design reviews and provide architecture guidance to technical leads and development teams.
• Maintain architecture decision records and ensure major technical decisions are documented.
• Identify cross-workstream technical dependencies before they affect sprint or release execution.
• Escalate architecture risks, platform constraints, technical debt, and design decisions requiring broader stakeholder action.
• Ensure implementation remains aligned with approved architecture throughout delivery rather than allowing sprint-level decisions to fragment the solution.

7. Sprint & Delivery Support

• Provide architecture leadership across a seven-sprint delivery model.
• Ensure technical designs and architecture decisions are sufficiently defined before dependent development begins.
• Support backlog refinement and technical decomposition of complex requirements.
• Partner with project leadership to identify architectural dependencies that affect sprint sequencing.
• Review proposed scope changes for architectural impact and technical complexity.
• Support engineering teams during implementation without replacing the accountability of designated development and workstream leads.

8. Security, Compliance & Responsible AI

• Incorporate enterprise security, data protection, access control, and compliance requirements into solution designs.
• Ensure architectural decisions support established review and production-change controls.
• Evaluate the appropriate use of approved AI-assisted engineering capabilities within established governance boundaries.
• Ensure AI-assisted development remains subject to accountable human technical review, testing, and release controls.
• Identify architecture and data-governance concerns associated with AI-enabled Salesforce capabilities where applicable.

Technical Workstreams

Storage & Archival

Architect a scalable data-retention and archival solution covering object categorization, retention requirements, archival patterns, dependent functionality, validation, and controlled production execution.

Trigger Framework Modernization

Define and govern a standardized Salesforce trigger framework, including bypass capabilities, execution controls, reuse patterns, and modernization of prioritized Apex automation.

QA Automation

Establish the technical approach for automated regression testing, CI/CD integration, test-data management, quality gates, and expansion of reusable automation coverage.

Environment Refresh & Data Masking

Define environment-management architecture covering sandbox refresh, sensitive-data protection, masking, selective data provisioning, repeatability, and validation.

Flow Modernization

Define Flow architecture and standards, rationalize the existing automation landscape, guide retirement of inactive automation, and govern migration of prioritized legacy automation into maintainable Salesforce Flow patterns.

Expected Deliverables

• Current-state architecture assessment
• Target-state Salesforce architecture
• Architecture principles and technical standards
• Solution architecture diagrams
• Integration and dependency architecture
• Trigger framework standards and implementation patterns
• Flow development and governance standards
• Data-retention and archival architecture
• Environment and data-masking strategy
• Automated testing and CI/CD architecture
• Architecture Decision Records (ADRs)
• Technical risk and dependency register
• Architecture review and release-readiness criteria
• Technical governance and development playbook
• Technical transition and knowledge-transfer documentation

Accountability Boundaries

The Solution Architect owns overall solution architecture, technical standards, design integrity, and cross-workstream technical governance.

• The Solution Architect defines architectural direction and approves solutions against established technical standards.
• Technical leads and developers remain accountable for implementation within the approved architecture.
• Business and product stakeholders retain ownership of business requirements, priorities, and acceptance.
• Project leadership owns integrated schedule, commercial management, scope governance, and delivery reporting.
• QA and release teams retain responsibility for test execution and deployment activities, with the architect establishing relevant technical quality expectations.