Customer Success Engineer

Customer Success Engineer

Edia is a Series A technology startup revolutionizing K-12 education with AI-driven solutions. We develop software to improve math education, tackle chronic absenteeism, and improve intervention processes for school districts. Today, Edia supports 200+ districts across the country.

Edia serves 200+ school districts—including New York City, Denver, Fulton County, and San Francisco—with AI-powered solutions for chronic absenteeism, math coaching, and MTSS workflows. We're in the middle of launching our District Intelligence Platform (DIP), which unifies data from SIS, LMS, attendance, and behavior systems into a single system of action for student success.

Every new district means a complex, high-stakes integration. We're connecting to Power School, Infinite Campus, Synergy, and a long tail of legacy SIS platforms. We're configuring Clever and Class Link rostering, standing up SFTP data feeds, importing benchmark and end-of-course exam scores, and aligning to district-specific data models—all on a school-year timeline that doesn't slip. A missed go-live date means a semester of lost student outcomes.

We need a technical owner who can architect and execute that end-to-end: someone who thinks in data models and APIs, and can drive every integration workstream from contract signature to successful launch.

You'll be our first dedicated Customer Success Engineer—a foundational hire on the Customer Solutions & Implementations team, reporting to our SVP of Customer Success. You'll function as the technical lead and project quarterback across CS, Product Engineering, and district IT stakeholders, balancing technical execution with strong project management and change-management instincts.

This is not a standard onboarding role. You're implementing a multi-product platform with multiple integration points, in districts with complex IT environments, competing priorities, and tight timelines. You bring an engineering mindset to every integration challenge — comfortable diving into API specs, data mapping, and system architecture — while maintaining the project rigor and customer judgment to deliver on school-year timelines.

Technical Integration Leadership

• Architect and execute SIS integrations across Power School, Infinite Campus, Synergy, and other legacy platforms—defining data mapping specs, transformation logic, and validation requirements.
• Own SFTP pipeline setup, Clever/Class Link rostering configuration, SSO provisioning, and platform-level data ingestion workflows.
• Write and review data transformation scripts, API integration specs, and configuration documentation. Hands-on coding ability is a strong plus; deep fluency in data models, REST APIs, and ETL patterns is required.
• Serve as the primary technical interface between Edia's engineering team and district IT—translating complex technical environments into clear implementation architectures.
• Identify integration risks early: schema mismatches, API rate limits, authentication edge cases, and data quality issues—and drive engineering solutions before they block go-lives.

End-to-End Implementation Ownership

• Lead full-lifecycle implementation projects from contract signature through go-live: project plans, technical milestones, dependency mapping, risk registers, and stakeholder coordination.
• Receive structured handoffs from Sales (SOW, technical requirements, champion intro) and manage clean transitions to CSM at go-live with full configuration documentation and adoption metrics.
• Own the internal status cadence across Product, Engineering, Support, and CS—removing blockers and driving accountability across all work streams.

Customer & Change Management

• Navigate district procurement timelines, IT governance processes, and organizational dynamics to keep implementations on track.
• Guide district stakeholders—from IT directors to curriculum leads—through technical onboarding and rollout best practices.
• Proactively surface adoption risks and drive mitigation plans before they become blockers.

Scale the Function

• We're scaling from a handful of concurrent implementations to 3–4x that volume in 2026. You'll design the playbooks, tooling,…