Job Title: Senior Workday Integration Consultant
Location: Remote
Duration: 6-18 month
Interview: Video
Must have:
· 9+ years of experience in integration, backend, or platform engineering
· Proven experience owning integrations from discovery through production
· Work with cloud infrastructure (AWS)
· Workday (Student or HCM)
· Banner / PeopleSoft
· Enterprise APIs and OAuth
· API-based
• 9+ years of experience in integration, backend, or platform engineering
• Proven experience owning integrations from discovery through production
• Strong experience with:
o Enterprise APIs and OAuth
o Batch and file-based integrations
o SFTP-based data exchange
• Strong data modeling and schema-mapping skills
• Experience working in cloud environments (AWS preferred)
• Strong documentation and communication skills
• Prior experience integrating higher-education systems:
o Workday (Student or HCM)
o Slate
o Banner / PeopleSoft
• Experience operating in governance-heavy or regulated environments
• Experience serving as a sole integration owner or consultant
• Work with cloud infrastructure (AWS) to:
o Configure ingestion pipelines
o Manage storage and compute
o Ensure secure data handling
• Apply least-privilege access and secure credential management
• Implement logging, monitoring, and alerting
• Ensure compliance with data handling requirements
• Implement approved integration designs end to end, including:
o REST API clients (authentication, pagination, retries)
o Batch ingestion pipelines (CSV, JSON, flat files)
o SFTP-based data exchange (push and pull)
• Build ingestion workflows that converge into a unified backend API layer
• Implement data validation, normalization, and reconciliation
• Handle institution-specific schema variance and edge cases
• Design end-to-end integration architectures including:
o Data flow diagrams
o Security and trust boundaries
o Error handling and retry strategies o auditability and reconciliation flows
• Define data contracts and canonical mappings
• Identify infrastructure and tooling requirements
• Ensure architectures are implementable, secure, and maintainable
• Recommend the most appropriate integration approach per client and per system:
o API-based
o Batch/export-based
o SFTP push/pull
o hybrid approaches
• Clearly articulate trade-offs between:
o real-time vs batch o automation vs operational overhead o depth of integration vs delivery risk
• Define integration scope that is realistic and supportable
Set expectations with internal stakeholders on feasibility and timeline