Lead Software Engineer - Hybrid

Crisis Prevention Institute Inc. (CPI) is the worldwide leader in evidence-based de-escalation and crisis prevention training and dementia care services. Our programs teach professionals the skills to recognize, prevent, and respond to crises in the workplace. Since 1980, we’ve helped train more than 17 million people within service-oriented industries including education, health care, behavioral health, long-term care, human services, security, corporate, and retail.

At CPI, we are dedicated to changing behaviors and reducing conflict for the Care, Welfare, Safety, and Security of everyone. We believe the power of empathy, meaningful connections, personal safety, and security are the antidotes to fear and anxiety. It’s a philosophy that is central to everything we do, and traces back to our beginning.

• Make a difference through your work – You’ll be proud to tell your family and friends about what you do.
• Gain significant career experience only obtained within a fast-growing organization – Entry-level roles through executive leadership.
• Feel fulfilled and have fun – We work hard but make the time to build meaningful relationships and celebrate the wins.

The Lead Software Engineer is the technical lead of a Product Engineering squad on CPI's Integrated Training and Learning (ITL) platform, the cloud-native learning platform used by CPI's learners, Certified Instructors, and customer administrators worldwide. This is a hands‑on, backend-focused role: the Lead spends the majority of their time designing and writing code in C#/.NET microservices built on CQRS and event‑driven patterns in Azure, and is comfortable working across the full stack, including the React front end, when the squad's work requires it.

As technical lead, the Lead Software Engineer owns the technical direction and delivery health of the squad: translating product outcomes into a sound technical approach, breaking work into small shippable increments, setting engineering standards, and ensuring the services the squad owns are reliable, observable, and easy to change. The Lead is a player‑coach, not a manager: they raise the squad's technical bar through design reviews, code reviews, pairing, and mentorship, and they model the culture CPI is building in Product Engineering: curiosity, ownership, drive, experimentation, learning from failure, and relentless improvement.

• Own the technical approach for the squad's roadmap: partner with the product owner to shape problems, evaluate options, and choose the simplest design that achieves the customer and business outcome.
• Lead technical design for new features and services in the ITL platform: C#/.NET microservices, CQRS command/query handlers, event contracts on Azure Service Bus, Azure SQL data models, and React front‑end integration.
• Break epics into small, independently deployable increments; drive the squad toward frequent, low‑risk production deployments using feature flags, trunk‑based development, and automated testing.
• Remain hands‑on: write production code daily, take on the hardest or most ambiguous technical problems, and unblock the squad when it gets stuck.
• Provide task breakdowns, identify dependencies and critical path, and give realistic effort estimates and risk assessments to the product owner and engineering manager.
• Demonstrate the squad's work to business stakeholders and clearly connect technical work to customer and business impact.

• Own the health of the services the squad is responsible for: define SLOs, ensure meaningful alerting and dashboards exist, participate in and help run the on‑call rotation, and lead the response…