Element451 is the AI-first CRM and student engagement platform for higher education. Our platform helps colleges and universities manage the full student lifecycle, from first inquiry through enrollment and student success. Institutions run their admissions, marketing, engagement, and retention operations on Element451, which means our platform has to connect reliably with the systems campuses already depend on - starting with their Student Information System.

The Role

Integrations are the connective tissue between Element451 and the systems campuses run on - student information systems first, and learning management and other API-based systems over time. Today we sell a managed integration package: rather than handing customers an API and a manual, Element451 scopes, builds, and maintains each institution's integration for them. That model is a competitive advantage, and it needs a single owner on the delivery side.

We're hiring a Senior Director, Integrations to own the entire post-sales integration lifecycle. Your organization takes the baton once a deal is signed and owns everything downstream: validating the signed SOW, architecting the integration, building it, and keeping it healthy for the life of the account. You'll lead an existing team of integration architects, integration engineers, and live support specialists.

This is a hands-on leadership role, not a slide-deck one. You are the senior subject-matter expert on SIS integrations - you don't need to write the code, but you must understand deeply how these integrations are built so you can scope them, direct your architects and engineers, and pressure-test an approach yourself. This isn't a Product role, but you'll be one of Product's closest partners - helping shape what we build natively so integrations become progressively less custom over time.

What You'll Own

SOW validation. Own the technical handoff from Sales into Delivery. Once a deal is signed, validate that the integration as scoped and sold is technically feasible and correctly sized before your team commits to the build — and surface gaps, risks, or missing requirements early, before they become escalations.

Integration architecture and scoping. Be the senior SME who, working with your integration architects, defines how each integration is designed — data models, sync patterns, authentication (OAuth, SAML, API keys), error handling, and how we ride frameworks like Ellucian Ethos. Set the reference patterns and standards that make every new build faster and more repeatable, and grow the IA team's depth in this space.

Integration build. Own the integration engineering team and the delivery of every integration through build, UAT, and go-live — after which bidirectional syncs between Element451 and the SIS run as Dagster jobs (cron schedules plus event-driven sensors) over the Ethos API. Own build quality, timelines, and the tooling and runbooks that let the team deliver consistently.

Flat-file and one-off integrations. Own integrations beyond the managed SIS set: flat-file exchanges (SFTP-delivered CSV and fixed-width files) for student information systems we don't cover with a managed connector, application-source feeds such as Common App, and bespoke one-offs — for example, syncing application data into another CRM. These are lower-volume and more custom, and your team scopes, builds, and maintains them to the same standard as everything else.

Care and maintenance. Own the operational lifecycle after go-live: sync health and monitoring, versioning as vendor APIs change, and enhancements to live integrations. You are the senior escalation point when an integration breaks the week before decisions go out.

Live support. Own the chat-based Live Support experience that helps customers with integration issues — staffing, quality, response standards, and the feedback loop from support back into build and architecture.

Delivery execution: people, process, and tools. You own how the integrations function runs. Set the operating model, hire and develop the team, define the process from handoff through maintenance, and choose the tooling that makes delivery reliable and scalable. Accountable for delivery outcomes — quality, reliability, throughput — not commercial margin.