Integration Engineer (Peoplesoft/Workday/Banner)

FUSTIS LLC is seeking an Integration Engineer specializing in Peoplesoft, Workday, and Banner integrations. The role involves owning integrations from discovery through production, working with cloud infrastructure, and ensuring compliance with data handling requirements.

Responsibilities:

• Proven experience owning integrations from discovery through production
• Work with cloud infrastructure (AWS)
• Strong experience with: Enterprise APIs and OAuth, Batch and file-based integrations, 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: Workday (Student or HCM), Slate, 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: Configure ingestion pipelines, Manage storage and compute, 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: REST API clients (authentication, pagination, retries), Batch ingestion pipelines (CSV, JSON, flat files), 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: Data flow diagrams, Security and trust boundaries, Error handling and retry strategies, 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: API-based, Batch/export-based, SFTP push/pull, hybrid approaches
• Clearly articulate trade-offs between: real-time vs batch, automation vs operational overhead, depth of integration vs delivery risk
• Define integration scope that is realistic and supportable
• Set expectations with internal stakeholders on feasibility and timeline

Requirements:

• 7+ 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
• Strong experience with Enterprise APIs and OAuth
• Batch and file-based integrations
• 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: Workday (Student or HCM), Slate, 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: Configure ingestion pipelines, Manage storage and compute, 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: REST API clients (authentication, pagination, retries), Batch ingestion pipelines (CSV, JSON, flat files), 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: Data flow diagrams, Security and trust boundaries, Error handling and retry strategies, 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: API-based, Batch/export-based, SFTP push/pull, hybrid approaches
• Clearly articulate trade-offs between: real-time vs batch, automation vs operational overhead, depth of integration vs delivery risk
• Define integration scope that is realistic and supportable
• Set expectations with internal stakeholders on feasibility and timeline