• Strong REST/API fundamentals: reading docs, testing endpoints, debugging, handling errors, pagination, rate limits
• Comfortable with auth patterns (OAuth2, API keys, tokens) and common failure modes
• Experience with SFTP/CSV/batch integration workflows and rigorous mapping/validation practices
• Working familiarity with higher-ed SIS/ERP concepts and terminology; experience with systems like Banner, Colleague, PeopleSoft, Workday Student, Jenzabar, etc. is a plus
• Strong written communication — clear for campus IT and precise for internal teams
• HOW WE MEASURE SUCCESS
• Integration go-live success: integrations launch on schedule without blocking go-live
• Integration health: fewer silent failures, stale syncs, and recurring data quality issues
• Time-to-resolution: faster recovery when issues occur
• Engineering escalation rate: high % resolved without Engineering involvement
• Documentation coverage: mapping docs and runbooks are complete, current, and actually used
• Scalability impact: reusable patterns reduce time-to-go-live over time
• WHAT THIS ROLE IS NOT
• Not a software engineering role (you won't build production features)
• Not a generalist implementation role (integrations are the core responsibility)
• Not passive ticket triage — you prevent repeats and improve reliability
• Not documentation-optional — if it isn't documented, it doesn't scale