1) Regional Architecture Ownership & Standardization

• Own the regional target architecture and multi-release roadmap for Automotive Cloud (Sales).

• Establish architecture principles/guardrails, reference patterns, and governance (e.g., declarative-first, reuse-first, integration standards, data quality rules).

• Lead cross-market fit-gap and standardization decisions; manage trade-offs between global consistency and local requirements and regulations.

2) Automotive Cloud (Sales) Solution Architecture — Year 1 Scope

• Lead Management: define capture channels, routing/assignment rules, lifecycle stages, deduplication approach, conversion governance, and auditability.

• Opportunity Management: define opportunity lifecycle/stages, pipeline governance, required data and controls, and handoffs across sales, dealer, and back-office processes.

• Price & Product Configuration:

• Define product catalog strategy (product hierarchy, options/variants as applicable), configuration governance, and lifecycle management.

• Define pricing architecture (price books, discounting/approvals, promotions as applicable) and controls.

• Align product and pricing integration with SAP (and dealer/DMS where relevant), including system-of-record, synchronization, and reconciliation approach.

• Account & Contact Management: define standard model (including dealer/customer structures), relationship patterns, stewardship responsibilities, and data quality controls.

• Vehicle & Asset Management: define entity strategy, lifecycle/state model, and relationships to accounts/contacts/leads/opportunities; align with MDM/SAP/DMS as system of record.

• Demand Forecast: define pipeline governance, forecast logic/inputs, operational cadence, and downstream integration/analytics needs.

• Workflow & Approvals: design scalable approval frameworks, exception handling, audit trails, and policy controls across markets.

• Reporting & Dashboards: define KPI governance (definitions, ownership, refresh cadence), role-based dashboard strategy, and “single source of truth” principles.

3) Agentforce Architecture (Responsible AI for Sales)

• Define AI use-case portfolio and guardrails for prioritized sales scenarios (e.g., lead/account/vehicle summarization, recommended next steps, guided selling prompts, forecast explanations).

• Define grounding strategy leveraging Data Cloud and approved enterprise sources; set requirements for accuracy, recency, and traceability.

• Define access controls and safety requirements (least privilege, sensitive data handling, auditability).

• Ensure Agentforce behaviors, retrieval sources, and actions respect Ford-standard consent constraints, including enforcement and auditability for consent-sensitive data.

• Establish evaluation and monitoring framework: quality, safety, latency, drift, and business impact; define go/no-go gates for production rollouts.

4) Enterprise Integration & Security Architecture

• Facilitate MuleSoft API-led standards: interface contracts, versioning, canonical mapping where appropriate, idempotency/retries, error handling, monitoring/alerting, SLAs, and support model.

• Define integration strategy and reconciliation approach; clarify system-of-record and data stewardship for shared domains.

• Define integration approach (security, connectivity, data quality, rollout scalability).

• Define integration approach (as needed) between Salesforce/Data Cloud and the Ford-standard consent component, including system-of-record, synchronization rules, and operational monitoring.

5) Delivery Governance & Stakeholder Leadership

• Run architecture and design reviews; manage cross-domain dependencies and risks (data, integration, security, release).

• Partner with Product Owner(s) on backlog readiness (acceptance criteria, NFRs, testability) and release scope decisions.

• Coach delivery teams/SI partners on standards and patterns; ensure solutions are supportable and aligned with enterprise architecture.

• Own documentation quality (solution designs, integration/data flows, security model, NFRs, operational readiness, release notes).

Internal Stakeholders

External Stakeholders

• SI, Suppliers

Key Measurements for this Position

• Adoption and measurable business outcomes across lead management, forecasting, vehicle/asset visibility, and reporting.
• Improved data quality, reduced duplicates, and trusted identity resolution/unified profiles in Data Cloud.
• Compliance (Ford standard component): correct capture and enforcement of consent/purpose across CRM, Data Cloud activation, and Agentforce use cases; audit readiness and reduction of consent-related defects/incidents.
• AI adoption with measurable productivity uplift and monitored quality/safety.
• Integration reliability measured through success rate, SLA compliance, incident reduction, and observability.

• Release quality and reduced recurring incidents through architectural remediation.

  #LI-SS

• Bachelor’s degree in relevant discipline.

• Salesforce Certified Administrator: Salesforce Certified Sales Cloud Consultant are required

• Automotive Cloud; Data Cloud; MuleSoft; Agentforce/Salesforce AI credential (as available) are preferred

• 6–9+ years Salesforce delivery experience with solution architecture ownership for complex programs (multi-market and/or multi-cloud).

• Strong experience across integration landscape: MuleSoft. Other integration landscape experience e.g. SAP, dealer/DMS ecosystems, AD/SSO, and enterprise data platforms (MDM/GCP) are preferred.

• Strong architecture competencies: Salesforce security, data modeling, automation patterns, SDLC, DevOps/release governance, and operability.

• Strong customer data architecture capability: identity resolution, consent/privacy, segmentation, activation, and data quality/lineage.

• Agile delivery fluency (Jira/Confluence) and strong stakeholder leadership.