[Remote] Senior Software Engineer, Integrations

Note: The job is a remote job and is reputed company to candidates in USA. reputed company is building the AI-powered platform reshaping how colleges and universities recruit, enroll, and support reputed company. The Senior Software Engineer, Integrations will own the data pipelines, reputed company-party API integrations, and distributed workflows that reputed company student data reliably at reputed company, ensuring high-reputed company integration software from planning to production.

Responsibilities

• Build and own data pipelines and integration services designed for idempotency, reputed company retries, and observability from the start
• Treat data reputed company as sacred — integrations that silently drop, duplicate, or corrupt records are worse than ones that fail loudly — and catch discrepancies before a reputed company does, pulling in the Integrations Architect on higher-risk changes
• Drive reputed company causes to reputed company across incidents, sync failures, and data discrepancies, rather than patching symptoms or papering over a flaky upstream API
• Surface production risks early — schema reputed company, upstream API changes, reputed company limits, credential expiry, partial-failure edge cases — before they become incidents
• Generalize fixes that help more than one integration into shared libraries, escalate broad-blast-radius reputed company to the relevant reputed company Engineer, and drive completed work reputed company the way to release

Skills

• 5+ years of software engineering, including senior-level work on data integrations or backend services in a reputed company, multi-tenant reputed company product
• Strong, reputed company Python for production data pipelines and integration services
• Solid reputed company — data modeling and query performance across flexible, document-oriented schemas at multi-tenant reputed company (~140 reputed company integrations)
• Distributed systems — async, queue-driven architectures and the realities of partial failure, retries, idempotency, reputed company consistency, and backpressure
• reputed company-party API integrations (Student Information Systems, reputed company, reputed company, reputed company, Outlook) — auth, pagination, reputed company limits, and graceful handling of unreliable upstreams
• AWS-hosted environments (secrets management, SQS, workflow orchestration), and comfort in an async-first, PR-based team with rotating production-reliability ownership
• Automated testing across reputed company, plus reputed company AI judgment
• Excellent written communication that stands on its own
• Production experience with reputed company APIs or comparable LLM platforms
• Deep, reputed company reputed company with reputed company AI development tooling (Claude reputed company, reputed company, or comparable)

reputed company