The Opportunity
As a Forward Deployed Integrations Engineer at Coursedog, you'll embed directly with our most strategic customers to own their SIS integration from start to finish, working closely with Engineering, Technical Services, our new Integrations Center of Excellence, and each customer's IT and registrar teams. You'll be responsible for getting integrations live correctly and on plan, protecting the live data they depend on, and turning what you learn in the field into repeatable playbooks and product improvements. The work balances hands-on execution with long-term thinking, and customer-by-customer problem solving with building solutions that scale. This role is well-suited for someone who takes ownership of hard technical problems, enjoys being the trusted technical voice in high-stakes deployments, and is motivated by helping institutions get more from Coursedog while making the platform better for every customer that follows.
If you're excited by complex SIS integration challenges across Banner, Colleague/Ethos, Workday, PeopleSoft, Jenzabar, and Anthology, and want to help strengthen the integrated data foundation that powers every Coursedog product, this is a chance to do meaningful work at real scale.
This position offers a competitive base salary between $90,000 - $110,000 , based on experience and qualifications. The role also includes a performance-based variable compensation component, bringing total on-target earnings (OTE) to $110,000–$120,000 when performance objectives are achieved.
What You'll Do
- Embed with customer accounts as the hands-on technical owner and builder, working directly with client IT, registrars, and functional leads
- Own end-to-end environment provisioning for staging and production, ensuring infrastructure is optimized and ready for integration before data flows begin
- Coordinate SIS connectivity setup with the customer's technical team, managing the handshake process where the customer initiates their side and Coursedog establishes bidirectional data flow
- Configure, test, and validate SIS integrations across SIS variants: attribute mappings, field wiring (GET/POST), data transformation logic, effective dating, cross-listing, merge thresholds, and conflict handling
- Validate data accuracy throughout the integration setup using test harnesses and sample data, identifying and documenting any mapping issues before production load
- Migrate institutional data at scale, planning for volume, merge performance, and client-side data readiness
- Root-cause merge and integration failures from merge reports and resolve the underlying cause — not just the ticket
- Treat write-back with production-grade care: backups, controlled merges, staging/production parity, and rollback discipline (our writes can change live registration data)
- Build API-based solutions and automations (REST, JSON, scripting) that unblock adoption and eliminate recurring friction at the configuration layer before it becomes an engineering escalation
- Identify and build out custom or non-standard SIS fields that don't fit standard Coursedog mappings, solving customer-specific data architecture needs directly rather than routing to engineering
- Conduct technical sessions with customer IT and integration teams to understand their SIS data structures, data quality issues, and integration constraints, then design solutions that align with best practices
- Feed the CoE. Document runbooks and reusable playbooks; partner with Product and Engineering (INT / Integrations Pipeline) to turn recurring fixes into product — validation rules, self-serve health checks, merge explainers
- Create clear handoff documentation for the Implementation PM and broader team, including integration architecture, validation results, known constraints, and any custom configurations
- Drive adoption and referenceability. Forward-deployed accounts carry an explicit reference and product-feedback mandate
What Success Looks Like (first 12 months)
- Your accounts go live correctly and on plan, with fewer post-go-live merge failures
- Zero write-back incidents on your accounts
- Measurably fewer issues from your accounts reach the engineering escalation queue
- A growing library of runbooks and productized fixes contributed back to the CoE
- Your accounts become referenceable
