[Hiring] Senior Software Engineer @Crisis Prevention Institute

Role Description

The Senior Software Engineer is a hands-on member of a Product Engineering squad on CPI's Integrated Training and Learning (ITL) platform. This is a full-stack role with a strong backend emphasis:

• Work primarily in C#/.NET microservices built on CQRS and event-driven patterns in Azure.
• Contribute to the React front end that delivers the learner and instructor experience.
• Own features end to end: shaping the problem, designing the solution, building and testing it, shipping it to production, and measuring outcomes.
• Raise the bar for the squad through code quality, technical judgment, and mentorship.
• Contribute to a culture of curiosity, ownership, experimentation, and continuous improvement.

Qualifications

• Bachelor's degree in computer engineering, computer science, or a related field, or equivalent practical experience.
• Five years or more of professional software engineering experience building and operating production web applications and services.
• Three years or more of hands-on experience with C# and .NET (ASP.NET Core, .NET 6+) building APIs and backend services.
• Experience building and maintaining distributed, event-driven systems, including message brokers (Azure Service Bus or equivalent) and asynchronous processing patterns.
• Experience with CQRS, domain-driven design, or similar patterns that separate reads from writes and model business domains explicitly.
• Experience building front-end features in React (hooks, state management, component design) and modern JavaScript/TypeScript.
• Experience designing relational data models and writing performant SQL (SQL Server / Azure SQL).
• Experience deploying and operating services in Azure (App Service, Functions, Service Bus, Azure SQL, Azure Monitor / Application Insights) or an equivalent cloud platform.
• Experience with automated testing across the stack (unit, integration, contract, and end-to-end) and CI/CD pipelines (Azure DevOps or GitHub Actions).
• Experience working on an agile team with continuous delivery practices: small batches, trunk-based development or short-lived branches, feature flags, and frequent production deployments.
• Knowledge of RESTful API design, authentication/authorization patterns, and security-based design patterns.
• Knowledge of observability practices: structured logging, metrics, distributed tracing, and alerting.
• Experience using AI-assisted development tools (e.g., GitHub Copilot, Claude, Cursor) as part of a daily engineering workflow.
• Yearly personal development demonstrated by successfully completing an accredited software engineering course, acquiring a software engineering-related certification, or presenting a completed learning project to the team.
• Curiosity: asks why before how, digs into unfamiliar code and systems, and seeks to understand the learner, instructor, and customer problem behind every request.
• Ownership: treats the services and features they touch as theirs to keep healthy, from design through production support.
• Drive: a bias toward shipping working software in small, frequent increments.
• Experimentation: comfortable proposing and running small, time-boxed experiments (spikes, proofs of concept, A/B tests).
• Learning from failure: participates openly in blameless retrospectives and incident reviews.
• Continuous improvement: leaves every codebase, process, and document a little better than they found it.
• Ability to take an ambiguous product problem and drive it to a well-designed, well-tested, shipped solution with minimal supervision.
• Ability to communicate technical trade-offs clearly to both engineers and non-technical stakeholders.
• Ability to give and receive direct, respectful feedback and to disagree productively while committing to team decisions.
• Ability to manage multiple, competing priorities and attain the best possible outcomes for the organization.

Requirements

• Participate in blameless incident reviews; drive follow-up actions that prevent recurrence.
• Continuously improve the codebase: reduce technical debt, improve build and deployment times, and simplify complexity.
• Apply secure coding practices and accessibility standards (WCAG 2.1 AA).
• Use AI-assisted development tools as a core part of the daily workflow.
• Experiment with new AI tools and techniques, measure their impact, and share findings with the squad.
• Identify opportunities where AI capabilities could improve the ITL product or internal tooling.
• Run small, time-boxed technical experiments and spikes to de-risk decisions.
• Give and receive thoughtful, direct code review feedback; mentor less experienced engineers.
• Contribute to retrospectives with candor, own your part in what went wrong, and follow through on improvement actions.

Benefits

• Make a difference through your work.
• Gain significant career experience within a fast-growing organization.
• Feel fulfilled and have fun while building meaningful relationships.