Software Engineer(.NET) - Tech Lead

Do you like staying close to the code while also deciding how a team builds its systems? As Tech Lead for our Customer Care team, you set the technical direction for the AI tools that hundreds of thousands of energy and internet customers actually talk to. If that sounds like the right mix for you, keep reading. What you'll do As Tech Lead for Customer Care, you own the technical direction of the team building our customer-facing AI stack: an LLM-powered chatbot with voice as a core capability, the Knowledge Base/RAG pipeline that feeds it, and the tooling and feedback loop the team uses to keep improving both. Real customers with real questions about their energy bill or internet contract get answers your team builds. That's the weight of it, and the fun of it. Day to day, this looks like: - Translating product and domain challenges into clear technical approaches that balance speed, quality, and long-term stability. - Being in the code and in the room: reviewing designs, pairing with engineers, and coaching them through harder decisions instead of making those decisions for them. - Keeping services observable, secure, resilient, and genuinely production-ready on Kubernetes. - Working closely with our architect on where this team's systems end and the rest of the domain begins. - Making the team's day-to-day better through tooling, CI/CD, and testing practices that pay off over months, not just this sprint. - Building a culture where people want to keep learning and take ownership of what they ship. About the team The team builds the suite of AI tools that supports our customers: a chatbot with voice as a core capability, the Knowledge Base/RAG pipeline behind it, and the feedback loop that keeps improving both. It's a small team in the in customer care domain, working alongside an internal architect, a QA engineer, and an external delivery partner. You report to the Engineering Manager, who owns people and direction, while you run delivery day to day, coach engineers who own their own solutions, and work out with the architect how domain-wide direction gets built inside the team. The team is early enough that you'll shape real decisions instead of inheriting them.