Enterprise Architect, Workday

Foundation for California Community Colleges
US flag
Remote, US
Full-timeTechnical
Salary
$130k–160kper year
Seniority
Lead / Principal
Hands-on configuration
50%of the role is configuring in the tenant
Systems
Workday + Salesforce

Good to know. Candidates must reside in California.

Overview

Turbin's analysis on the role ·

Workday platform and integration architect role.Architecture and integration ownership beat module depth.

The posting centres on platform-wide target-state architecture for a Workday rebuild, enterprise data strategy, and the integration layer to Salesforce. Specific modules are not named in duties, and certifications like Prism or Security are listed only as examples of a plus.

Skills, by how much you'll use them

From Turbin's read of the posting
3 skills
Every day

The core of the job. Lead with these.

  • Workday architecture
  • Integrations
  • Data strategy
3 skills
Only mentioned

Named in the posting. Safe to skip.

  • Salesforce
  • Prism
  • Security

What you'll do

5 responsibilities
  • Serve as the architectural authority for the Workday platform and lead target-state architecture for the ongoing Workday rebuild
  • Govern how Workday solutions are designed and built across modules and enterprise systems
  • Own the integration and orchestration layer connecting Workday to Salesforce and other enterprise systems
  • Lead the enterprise data management strategy and establish patterns for data and AI movement across systems
  • Drive technical solution discussions with internal customers and provide architectural and technical direction

Do you fit?

Tick what you have. Only you see this.
0 of 3 must-havesTick what you have to see your match.
Must have · 3

Nice to have

  • Workday certifications such as Integrations, Prism, or Security
  • Salesforce exposure
  • Nonprofit experience

How to pitch yourself

Turbin's advice

Lead with your Workday platform architecture and integration landscape ownership, especially across a rebuild or multi-system environment. Mention Salesforce integration patterns and any Workday certifications briefly if you have them.

  1. Highlight end-to-end integration architecture ownership, noting scale and patterns such as "architected Workday to Salesforce integration layer during platform rebuild"
  2. Show how you governed solution design and enterprise data flows across Workday and downstream systems rather than working inside a single module
  3. Include Workday Integrations, Prism, or Security certifications and any Salesforce or nonprofit context only if you genuinely hold them