Make other engineering teams more effective

• Treat internal engineering teams as important customers of Core Systems.
• Build APIs, services, tools, and platform capabilities that make it easier for product teams to move quickly and safely.
• Partner closely with product engineering teams to understand recurring pain points and identify opportunities for shared solutions.
• Establish clear boundaries and ownership between shared platform capabilities and product specific functionality.

Operate critical systems well

• Build a strong operational culture around the systems the team owns.
• Use observability, incidents, capacity planning, and production data to continuously improve reliability.
• Lead thoughtful incident reviews and ensure the team addresses systemic issues rather than simply fixing symptoms.
• Help the team make pragmatic decisions about reliability and resilience based on customer and business impact.

What We're Looking For

• Experience managing software engineering teams responsible for complex production systems.
• A strong software engineering background and the technical depth to participate meaningfully in architecture and system-design discussions.
• Experience designing, operating, or leading teams responsible for distributed systems, backend services, shared platforms, or similarly foundational technology.
• A track record of delivering significant technical initiatives involving multiple systems or engineering teams.
• Strong judgment about when to invest in architecture and when a simpler solution is the right answer.
• Experience building systems where reliability, scalability, security, and operational quality matter.
• Ability to communicate complex technical topics clearly to both engineers and non-technical stakeholders.
• Strong people-management skills, including coaching experienced engineers and creating clear accountability without micromanagement.
• Comfort operating in environments where the path is not always obvious and technical decisions involve meaningful tradeoffs.

Nice to Have

• Experience operating large-scale cloud systems, particularly in AWS.
• Experience with distributed data systems, service-oriented architectures, or high-scale backend platforms.
• Experience evolving mature systems while maintaining high availability for customers.
• Experience with multi-region, multi-tenant, or data-residency architectures.
• Experience building internal platforms or shared capabilities used by multiple product engineering teams.
• Experience working in SaaS, education technology, or another environment with significant security and privacy requirements.

How We Think About Success

In your first year, success in this role will look like:

• The team has clear ownership, priorities, and technical direction.
• Engineers on the team are growing and operating with increasing autonomy.
• Core systems are becoming more reliable, understandable, and easier to evolve.
• Major architectural investments are progressing through pragmatic, incremental delivery rather than large open-ended rewrites.
• Product engineering teams can move faster because foundational capabilities are easier to use and better supported.
• Engineering leadership has clear visibility into the health, risks, and long-term direction of the systems the team owns.

Our company participates in E-Verify.