Senior Software Engineer

Our Story:
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.

As a member of the team, you can expect to:

• 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 Role:
The Senior Software Engineer is a hands-on member 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 full-stack role with a strong backend emphasis: the majority of the work is in C#/.NET microservices built on CQRS and event-driven patterns in Azure, with regular contribution to the React front end that delivers the learner and instructor experience. Working in a small squad alongside a product owner, designer, and fellow engineers, the Senior Software Engineer owns features end to end: shaping the problem with the product owner, designing the solution, building and testing it, shipping it to production, and measuring whether it moved the customer or business outcome it was meant to move. This role is expected to raise the bar for the squad through code quality, technical judgment, and mentorship, and to actively contribute to a culture of curiosity, ownership, experimentation, and continuous improvement.

Product Delivery:

• Design, build, test, deploy, and support features across the ITL stack: C#/.NET microservices, CQRS command and query handlers, Azure Service Bus event consumers and publishers, Azure SQL data models, and React front-end components.
• Partner with the product owner and designer to understand the customer problem behind each request, challenge assumptions, and propose the simplest solution that delivers the outcome.
• Break epics into small, independently shippable increments; ship to production frequently behind feature flags and validate with real usage data.
• Write automated unit, integration, and contract tests as part of every change; treat test coverage and observability (logging, metrics, tracing) as part of the definition of done.
• Demonstrate completed work to business stakeholders and articulate the customer and business benefit, not just the technical change.

Platform Ownership & Operational Excellence:

• Own the health of the services your squad is responsible for: monitor dashboards and alerts, participate in the on-call rotation, and respond to and resolve production issues.
• Participate in blameless incident reviews; drive follow-up actions that prevent recurrence (tests, alerts, runbooks, architectural fixes).
• Continuously improve the codebase you work in: reduce technical debt incrementally, improve build and deployment times, and simplify where complexity is not earning its keep.
• Contribute to the incremental decoupling of ITL domain data from upstream enterprise systems by ensuring each feature you build moves the data ITL needs into ITL-owned services.
• Apply secure coding practices and accessibility standards (WCAG 2.1 AA) as a default part of engineering work.

AI-First Engineering:

• Use AI-assisted development tools (e.g., GitHub Copilot, Claude, Cursor) as a core part of the daily workflow for design exploration, code generation, test writing, refactoring, and debugging, while owning the quality, security, and correctness of everything shipped.
• Experiment with new AI tools and techniques, measure their impact on speed and quality, and share what works (and what does not) with the squad.
• Identify opportunities where AI capabilities could improve the ITL product or internal tooling and bring them to the squad with a proposed proof of concept.

Culture, Learning & Collaboration:

• Bring curiosity to the work: investigate unfamiliar parts of the system, ask why, and share what you learn in code reviews, documentation, and team discussions.
• Run small, time-boxed technical experiments and spikes to de-risk decisions; present findings and recommendations to the squad with evidence.
• Give and receive thoughtful, direct code review feedback; mentor less experienced engineers and help them grow.
• Contribute to retrospectives with candor, own your part in what went wrong, and follow through on improvement actions.
• Perform other position-related duties as assigned.