Engineering Team Lead

Remote | Reports to CTO

As our engineering organization grows, we’re hiring an Engineering Team Lead to support a team delivering high-quality, reliable software.

This role carries real accountability across delivery, technical quality, and team health. It is intentionally designed so that, over time, the team becomes less dependent on you for day-to-day decisions.

You’ll remain technically engaged — participating in design discussions, reviewing PRs, and occasionally contributing code — but this is not a “hero” or “fixer” role. Your primary responsibility is to strengthen the team’s ability to make sound technical decisions independently.

Own Outcomes

• Ensure clear standards exist for architecture, quality, reliability, and maintainability
• Maintain alignment between engineering work and business objectives
• Take responsibility for delivery outcomes without becoming a bottleneck

Guide Technical Direction

• Facilitate design reviews and RFCs
• Help the team document trade-offs and converge on shared decisions
• Step in when decisions stall or risk becomes material

Delivery & Execution

• Improve flow and predictability
• Support the team in handling incidents and unexpected complexity
• Create clarity without centralizing control

AI-Assisted Engineering

• Actively leverage AI and agentic tooling to improve engineering quality and reduce cycle time
• Encourage experimentation while maintaining standards

Team & Performance

• Run 1:1s and support professional growth
• Own performance decisions through transparent processes
• Support hiring and team formation
• Foster a culture of shared responsibility rather than centralized authority

You retain final decision authority, but use it sparingly.

You step in decisively when:

• The team is deadlocked
• High-impact incidents require coordination
• Quality or reliability is at risk
• Time constraints make distributed decision-making impractical

When you intervene, you:

• Take responsibility for the outcome
• Explain your reasoning clearly
• Strengthen the system so the team can handle similar situations independently next time

Your goal is not to be indispensable, but to build a team that functions well without constant escalation.

• Experience leading engineers in a product environment
• Strong technical background with the ability to engage in architectural discussions
• Comfort with accountability for delivery and team performance
• High self-awareness around authority and decision-making bias
• Ability to balance autonomy with standards

You don’t need to dominate every technical decision. You need to create the conditions where good decisions happen consistently.

• Growing company with real customer traction
• Opportunity to shape how engineering scales
• Direct partnership with the CTO
• Product built around applied AI in a traditional industry
• Culture that prioritizes sustainable systems over heroics