Vancouver, British Columbia, Canada
Aplos
Full-time
About Velora:
📍check out our company website: joinvelora.com
Our product websites:
Together, our combined expertise spans fundraising, donor management, financial tracking, and communications—offering a powerful suite of tools designed to reduce complexity so nonprofits can focus on what matters most: making a difference.
We’re one company with 3 products all servicing customers in the impact space. Working at Velora means that you have the opportunity to build one or across all our products.
We have a combination of merged teams and also teams dedicated to one specific product and you can find details about the work through our job descriptions under the “about the role” section.
About the role:
Location: Remote — Canada (Ontario, Manitoba, Alberta, British Columbia only); Vancouver area preferred
Velora is looking for a Senior DevOps / Platform Engineer to help run and scale the infrastructure behind Aplos, Raisely, and Keela. This role centers on Raisely (GCP) as our top business priority today, with exposure across all three brands as we unify the platform.
This is a DevOps role with a platform engineering focus: building the internal developer platform and paved roads that power how Velora engineering teams build, ship, and operate software (not the product platform itself).
We move fast — we're an established, financially solid company, not an early-stage gamble — and we need people who enjoy wearing many hats, adding value, and working shoulder-to-shoulder with the wider engineering org. We hold one of the closest DevOps↔Engineering relationships you'll find anywhere, and that's on purpose.
At Velora, DevOps provides the tooling, infrastructure, and processes that let engineers self-serve — safely and at speed. Many engineers have permission to deploy services to production and own everything around them (configuration included) because we’ve built the platform and guardrails that make that safe.
We treat our internal developer platform as a product: we partner closely with engineers to understand pain points, requirements, and SDLC needs, then we go build the solutions and operate them. That means DevOps owns core platform evolution work (like upgrades and foundational improvements) so product engineering can keep attention on customer and business problems — while still enabling teams to own services end-to-end.
So while the title is DevOps, the person we're looking for is a full-spectrum engineer: someone who understands cloud deeply, provisions and upgrades infrastructure, reasons about networking, memory, CPU, and virtualization — and who can genuinely code, reason about distributed systems, and think through complex workflows. An engineer who chooses to solve DevOps problems.
What will you be doing (your role)?
Platform & Infrastructure Ownership
📍check out our company website: joinvelora.com
Our product websites:
- keela.co
- raisely.com
- aplos.com
Together, our combined expertise spans fundraising, donor management, financial tracking, and communications—offering a powerful suite of tools designed to reduce complexity so nonprofits can focus on what matters most: making a difference.
We’re one company with 3 products all servicing customers in the impact space. Working at Velora means that you have the opportunity to build one or across all our products.
We have a combination of merged teams and also teams dedicated to one specific product and you can find details about the work through our job descriptions under the “about the role” section.
About the role:
Location: Remote — Canada (Ontario, Manitoba, Alberta, British Columbia only); Vancouver area preferred
Velora is looking for a Senior DevOps / Platform Engineer to help run and scale the infrastructure behind Aplos, Raisely, and Keela. This role centers on Raisely (GCP) as our top business priority today, with exposure across all three brands as we unify the platform.
This is a DevOps role with a platform engineering focus: building the internal developer platform and paved roads that power how Velora engineering teams build, ship, and operate software (not the product platform itself).
We move fast — we're an established, financially solid company, not an early-stage gamble — and we need people who enjoy wearing many hats, adding value, and working shoulder-to-shoulder with the wider engineering org. We hold one of the closest DevOps↔Engineering relationships you'll find anywhere, and that's on purpose.
At Velora, DevOps provides the tooling, infrastructure, and processes that let engineers self-serve — safely and at speed. Many engineers have permission to deploy services to production and own everything around them (configuration included) because we’ve built the platform and guardrails that make that safe.
We treat our internal developer platform as a product: we partner closely with engineers to understand pain points, requirements, and SDLC needs, then we go build the solutions and operate them. That means DevOps owns core platform evolution work (like upgrades and foundational improvements) so product engineering can keep attention on customer and business problems — while still enabling teams to own services end-to-end.
So while the title is DevOps, the person we're looking for is a full-spectrum engineer: someone who understands cloud deeply, provisions and upgrades infrastructure, reasons about networking, memory, CPU, and virtualization — and who can genuinely code, reason about distributed systems, and think through complex workflows. An engineer who chooses to solve DevOps problems.
What will you be doing (your role)?
Platform & Infrastructure Ownership
- Take end-to-end ownership of our internal orchestration platform — a real SaaS product that DevOps builds and operates, whose customers are Velora's engineering teams.
- This is a full software stack: a frontend, a backend, a document database, and complex distributed orchestration logic built on an event-driven architecture with Redpanda. Owning it means owning the code, the architecture, and the roadmap — not just running it.
- Evolve the platform as a product: understand what engineering needs, design the workflows, and ship the software that delivers them.
- Own and evolve our infrastructure-as-code with Terraform (we use Terraform Cloud) — provisioning, upgrading, and managing environments. GCP (Raisely) is the focus initially, with expected exposure to AWS and Azure over time as the person ramps and begins contributing to Terraform for the other brands.
- Operate and scale Kubernetes-based workloads with Helm — owning reliability, capacity, networking, and performance for the services you support.
- Provide the tooling, infrastructure, and processes that let engineers own their services end-to-end — from deployment through c