• You will lead the Payments team • Be accountable for payments working correctly, reliably, every single time • Shape the roadmap and argue for product direction • Lead a team of senior engineers • Own the full payments product — front end and money mechanics • Multiple integrated payment facilitators kept correct and uninterrupted • Handle bugs, issues, and production support — end to end • Engage in product planning and estimation

• Design, develop, and maintain scalable backend applications and services using C# and .NET/.NET Core. • Architect and build enterprise-grade RESTful APIs and backend services. • Evaluate and improve application architecture, scalability, and maintainability. • Promote engineering standards, coding best practices, and clean software architecture. • Design and support cloud-native applications within Microsoft Azure. • Collaborate on deployment strategies, cloud optimization, and infrastructure improvements. • Troubleshoot and resolve complex production issues. • Mentor junior and mid-level software engineers.

• Develop and maintain backend services using C# and .NET/.NET Core. • Build and support RESTful APIs for internal and customer-facing applications. • Develop new features, enhancements, and bug fixes across multiple software products. • Write clean, scalable, maintainable, and well-documented code following engineering best practices. • Support applications hosted within Microsoft Azure environments. • Collaborate closely with product, frontend, and DevOps teams to deliver scalable cloud-based solutions.

• Overhaul how Close syncs email and calendars. Our sync engine has run for a decade; we're making a serious, ground-up investment in its performance and reliability. • Take voice agents further into the call. We own the live conversation layer for Chloe's calls, and there's a lot of work ahead expanding our voice agent capabilities and infrastructure. • Solve inbound. So far Chloe makes calls; next she answers them. An inbound conversation can go anywhere — which raises real questions about specialized agents, a receptionist layer, and seamless call routing between them. • Build native scheduling. Core calendar scheduling capabilities inside Close, plus more powerful scheduling for our agents. • Design human orchestration of an agentic workforce. Agents create work for humans too — things to review, approve, respond to. • Push connect rates and answer rates. Phone number pooling, local presence, branded calling, reputation monitoring. • Move our streaming and event substrate forward. Kafka, Redis, pub/sub.