Role summary by JobGrid
Software Engineer, Integrations at SchooLinks: Remote, United States; Full time; Senior; IT; Back End Engineer. This listing is part of JobGrid's Remote software engineer jobs from public company career pages. JobGrid adds normalized role facts, source context, and a path to the employer application page so candidates can compare the listing before applying.
- Location and workplace: Remote, United States
- Role classification: IT, Back End Engineer, Full time, Senior
- Source freshness: checked by JobGrid on 2026-05-28.
- Application path: candidates continue to the employer application page with non-personal referral tags.
We’re looking for a Software Engineer to own our data migration and integration infrastructure — end to end. This is a greenfield, individual contributor role: you’ll be the sole engineer driving this work, which means you’ll move from blank page to production on your own. You’ll own everything from architecture and design through implementation, testing, documentation, and long-term maintenance. Our first major integration is with Slate (by Technolutions), a leading CRM used by college admissions offices — but this role will grow into a full integration platform as SchooLinks expands its partner ecosystem. If you thrive with real ownership, love solving hard data problems, and want your work to have a direct impact on students’ futures, this role is for you.
As the product area you support grows, you’ll be well-positioned to move into management and leadership rules in the future.
What You'll Build
• Independently architect and implement bi-directional data integrations between SchooLinks and external platforms — starting with Slate (Technolutions)
• Design, build, test, and document RESTful API connections, webhooks, and OAuth/SSO flows to support secure, real-time data exchange — taking full ownership of each integration from technical spec through production deploy. You’ll build using Python code running in our Django service and Lambdas on AWS.
• Design ETL pipelines to map and transform student data across different schemas, handling edge cases, conflict resolution, and idempotency.
• Set up monitoring, alerting, and observability for every integration in production — then own ongoing maintenance, incident response, and iterative improvements as partner systems evolve
• Write the foundational documentation for this function — technical specs, API references, runbooks, and integration guides establishing the standard that future engineers will build on