Software Developer (Casper Team)

*Intermediate or Senior level Remote within Canada*

A high-scale product, end-to-end ownership, and real problems to solve.

Casper is one of Acuity Insights’ core products, used by hundreds of programs globally to make high-stakes admissions decisions with greater confidence. It helps programs look beyond academic metrics by evaluating how applicants think, reason, and respond in complex situations, consistently and at scale.

Casper supports approximately 160,000 applicants each year, with individual test sessions ranging from 3,000 to 5,000 applicants at a time. It’s a system where reliability, performance, and judgment matter in real-world conditions.

We’re hiring two Software Developers to join the Casper team: one Intermediate and one Senior. You’ll work on a product with over a decade of production history: stable, widely used, revenue-critical, and actively evolving.

As George (Development Manager) puts it, “This isn’t a product you work on from the edges. You’re working on the system itself.”

This is not a greenfield role. It’s also not maintenance-only. Some parts of the system are well-established; others need modernization, clearer patterns, stronger testing, and thoughtful technical stewardship. You’ll help keep an important product healthy while building the next capabilities that make Casper more valuable, resilient, and ready for what comes next.

As AI reshapes how applicants prepare and respond, Casper is adapting too. The engineering work behind it is becoming more complex, more consequential, and more interesting, from how the team builds software day to day to how the product protects trust and test integrity.

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, your focus will be on upgrade, stability, and reliability work, helping move Casper onto supported versions of key technologies and building a strong understanding of how the system behaves in production.

Over time, that balance shifts. You’ll move into more product-oriented work, contributing to how Casper evolves in response to changing market needs.

Right away, you’ll likely be working on core upgrade and stability work, helping move Casper onto supported versions of Meteor and MongoDB, improving reliability, and getting familiar with how the system behaves in production. This work is how the team builds the context needed to safely evolve a system at this scale.

From there, you’ll move into work that shapes where Casper goes next.

That includes things like:

Score evolution
Rethinking how Casper scores are calculated, processed, and presented, a system that spans multiple services and connects everything from test delivery to program-facing insights.

Test integrity in an AI world
Designing how Casper detects, deters, and responds to policy violations in an environment where applicants have access to increasingly capable AI tools.

Making the product more understandable and defensible
Improving how programs interpret results, from analytics to score presentation, so decisions are clearer, more consistent, and easier to stand behind.

Supporting more complex program structures
Like institutions operating across multiple campuses and geographies, where the product needs to reflect more nuanced real-world use.

Some of this work is well-defined. Some of it is still taking shape. You’ll be part of figuring that out.

How the team works

Casper operates on a shared ownership model. There isn’t a strict separation between parts of the system, everyone contributes across the stack and across domains.

That includes core areas like authentication, payments, test delivery, scoring, alerts, and production support.

You’ll be part of a team that is collectively responsible for keeping the system running, improving it over time, and responding when things go wrong.

The kind of engineering environment you’ll join

Casper is built primarily with JavaScript, Meteor, MongoDB, React, and AWS.

The system reflects over a decade of evolution, with contributions from many developers over time. You’ll need to be comfortable navigating different patterns and approaches, understanding why things were built the way they were, and improving them thoughtfully.

You’ll need to be comfortable reading before rewriting, understanding context before changing direction, and making improvements that m…