Engineering Manager, Support & Stability

What You’ll Do

• Own stewardship of the application's highest-risk, highest-impact domain areas. Keep them clean, tested, and maintainable so other teams can build on top of them with confidence.
• Build the measurement systems that tell you where risks live. Deployment frequency, days with commits, support ticket volume, and recurring failure patterns are your leading indicators. If you can't measure it, you can't protect it.
• Prioritize root cause over volume. When a class of problem keeps showing up, your job is to make it go away permanently, not to keep closing tickets against it.
• Lead your team's first-line triage of engineering support tickets. Own and resolve what you can, and route what you can't with the context already assembled so the receiving team isn't starting from zero.
• Push your team to make AI agents the default starting point for domain maintenance and support triage, not an afterthought. Review AI-generated work with the same rigor you'd apply to any code.
• Lead your team's AI adoption directly. Set the expectation clearly, give people support and time to build the skill, then hold them accountable.
• Build and champion the skills, prompts, and automation that turn a recurring problem into something AI catches or fixes before a human has to.
• Negotiate the boundaries of what your team owns versus what stays with the team that built it. Keep the scope tight and defensible.
• Represent your team's perspective on system health and support trends back to product and engineering leadership, and make the case for stability work with the same rigor others bring to feature work.
• Run the fundamentals of people management well. Clear expectations, regular high-quality 1:1s, direct feedback, and investment in your team's growth.
• Maintain enough hands-on technical involvement to stay credible on the work your team does and to unblock them when it matters.

Your Experience

• 3+ years of engineering management leadership experience, ideally including ownership of platform reliability, system health, or critical-domain code.
• You've built or run a proactive stability or support program, not just responded to incidents and tickets as they came in.
• You have experience distinguishing a one-off issue from a systemic one, and you've made the call to invest in a permanent fix instead of patching the symptom.
• You use AI agents as a default part of how you and your team work, and you can describe specifically how that changed your team's output, not just that you tried it.
• You're comfortable saying no. You can negotiate scope and ownership boundaries with other teams without damaging the relationship.
• You have enough technical depth to review complex work in high-risk domains and to stay hands-on when the team needs you to be.
• You've managed underperformance and recognized strong performers with clarity and consistency, and you know how to hold people accountable while building psychological safety.
• You operate with intensity and hold a high bar for your own work and for the people around you. You give direct feedback, ask for help early, and respond to setbacks with ownership rather than withdrawal.
• Strong experience with PHP/Laravel environments is a plus, but not required.

Nice-to-Haves

• Experience with PHP/Laravel
• Tech stack familiarity: Vue.js, MySQL, DynamoDB, Kubernetes, AWS, Jira, Claude, Cursor, Datadog, Snowflake