Senior Migrations Engineer

Core responsibilities

• Migrations Platform Development: Design, build, and evolve the Migrations Platform — a mission-critical PHP application — ensuring it is reliable, performant, and scalable as we onboard increasing volumes of schools.
• SLA Ownership: Take ownership of the platform's defined SLAs, including migration success rates, throughput, and turnaround times. Identify and deliver improvements that raise the bar on reliability and quality.
• Reliability and Performance: Take services from design through to production with end-to-end ownership. Ensure they are observable, with the logs, dashboards, and alerts needed to detect and respond to issues fast.
• Automation: Reduce operational toil for the Migration Operations team by automating repetitive tasks, validations, and data integrity checks.
• Customer-Critical Delivery: Support migration windows during weekends and school holidays. Be flexible with working hours during peak onboarding cycles to ensure customers go live successfully.
• Technical Standards: Apply and uphold coding standards, write well-tested and reusable code, and engage with the architecture community to share best practices. Ensure services meet production readiness standards.
• Planning and Delivery: Provide accurate estimates and feasibility input on technical work. Deliver iteratively, contribute to release planning, and participate in post-release reviews.
• Incident Response: Lead investigations of failed or delayed migrations, perform root cause analysis, and drive follow-up improvements that prevent recurrence.
• Mentorship: Support and mentor fellow engineers, including Migration Operations Engineers, through code review, pairing, and constructive feedback. Share knowledge generously across the team.
• Collaboration: Work closely with Onboarding, Support, Product Managers, and other engineering teams to coordinate timelines, manage customer expectations, and align technical delivery with the wider onboarding strategy. Communicate risks, blockers, and status clearly to both technical and non-technical stakeholders.