Remote within Canada A product that matters, a modernization effort underway, and meaningful problems to solve. One45 is one of Acuity Insights’ core products, used by medical schools across North America to manage some of the most operationally complex parts of health professions education. From clinical placements and rotation scheduling to evaluations, curriculum management, learner records, and accreditation reporting, One45 sits at the center of workflows that institutions rely on every day. Many of our clients have been with us for more than a decade. The product supports tens of thousands of learners, educators, administrators, and clinical faculty members each year. It’s the kind of system that becomes deeply woven into how organizations operate, where reliability, context, and thoughtful decision-making matter as much as technical execution. We’re hiring a Senior Software Developer to join the One45 team. You’ll join a product with more than twenty years of production history: stable, widely adopted, and entering a significant period of evolution. This is not a greenfield role. It’s also not a maintenance-only role. Some parts of the product have remained largely unchanged for years. Others are actively being modernized. The team is evolving APIs, improving data access and integrations, rethinking major workflows, and improving how software is developed with AI-assisted tooling throughout the lifecycle. You’ll help maintain and improve a product that institutions already depend on while contributing to a modernization effort that’s beginning to move from planning into execution. If you’re joining One45 today, you’re joining at a moment when many of the most important decisions are still being made. You’ll have the opportunity to help shape how the product evolves, how the team works, and what comes next. What you’ll work on There’s no clean separation between “maintenance” and “new work” on this team. Both matter, and both are shared. In your first few months, you’ll likely spend most of your time learning how the system behaves in production by working on customer-facing enhancements, bug fixes, and workflow improvements. The kinds of requests that seem straightforward on the surface, but often require understanding years of product decisions, customer expectations, and interconnected workflows underneath. It’s also a way to learn Right away, you might be working on things like: Improving evaluation workflows. Giving administrators more control over how evaluations are delivered, managed, and communicated. Making assessment information clearer. Improving how grades, scores, and other learner information are presented so they’re easier for programs to interpret and use. Refining permissions and access controls. Helping institutions manage increasingly complex roles, responsibilities, and workflows across their programs. Addressing day-to-day friction. Fixing bugs, improving workflows, and solving the kinds of problems that matter because people encounter them every day. This work isn’t separate from modernization. It’s how the team builds the context needed to modernize the product responsibly. Over time, that balance shifts, and you’ll move into larger initiatives that help shape where One45 goes next. That includes things like: API modernization. Building out the next generation of APIs that make the platform easier to integrate with, extend, and evolve. Evolving core modules. Reworking foundational areas of the product such as scheduling, placements, and lottery management to better support how institutions operate today. Improving access to data. Helping schools make better use of the information already inside One45 through improved reporting, integrations, and analytics capabilities. AI-assisted software development. Contributing to how the team incorporates AI throughout the development lifecycle, from implementation and testing to review and documentation. Some of this work is well-defined. Some of it is still taking shape. If you enjoy contributing ideas, challenging assumptions, and helping shape where work goes next, you’ll have opportunities to do that here. How the team works One45 operates on a shared ownership model. There isn’t a dedicated scheduling developer, evaluation developer, or API developer. The team works across the platform, contributing wherever the work is most important. That means a typical week might involve reviewing someone else’s code, investigating a production issue, refining requirements with Product, working on a customer-facing enhancement, and helping test a feature before it ships. Everyone contributes across the stack. Everyone participates in code reviews. Everyone helps improve the system. Product is deeply embedded in how the team operates. One45 has a dedicated Product Manager who participates in planning, backlog refinement, release discussions, and day-to-day decision-making. Engineers and Product work closely together to shape solutions, prioritize work, and navigate trade-offs as the platform evolves. The team is currently three developers, a Development Manager, and a rotating group of co-op students. As a result, ownership tends to be broad rather than narrow. One of the realities of working in a mature system is that context matters. Understanding how decisions connect across the platform is often just as important as the implementation itself. As the team grows, we’re investing in additional technical depth and leadership capacity so that ownership can be distributed more broadly, decisions can move more quickly, and more people can confidently drive important work forward. You’ll be joining a group that’s actively improving how work moves, how knowledge is shared, and how decisions get made. The team is small enough that everyone’s voice matters. The people who have the biggest impact aren’t necessarily the loudest or the most senior. They’re the ones who ask thoughtful questions, challenge assumptions, share context, and h