Resumen del rol

Senior DevOps Engineer/Platform Engineer

Requisitos y responsabilidades

Contenido del rol extraído en secciones para revisar más rápido.

Our product websites:

  • keela.co
  • raisely.com
  • aplos.com

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.

Enabling Engineering Self-Service

  • Provide the tooling, infrastructure, and processes that let engineers own their services end-to-end — from deployment through configuration — instead of routing work through DevOps as a ticket queue.
  • Hold a clear sense of ownership boundaries between Engineering and DevOps: what each component should own, and where one team's responsibility ends and the other's begins. Codify the contract between teams so nothing slips through the cracks.
  • Partner directly with engineers — reason about distributed systems, data flows, transactions, and webhooks; pinpoint where a problem manifests (in code, in a schema, in a wrong assumption) and hand back a clear diagnosis, without taking over engineering's work.

Reliability & Operations

  • Own reliability for the platform and services you steward: set sensible SLOs, plan capacity, run resilience drills, and keep systems within target.
  • Share in production on-call as part of the team — we own what we get paged for, fix what keeps breaking, and keep toil low through automation.
  • Take ownership during incidents: jump in quickly, drive toward remediation, and run blameless post-incident reviews that produce durable fixes and better runbooks.

Standards & Security

  • Set and drive adoption of modern SDLC patterns — module structure and dependencies, environment promotion, and safe, progressive delivery.
  • Apply least-privilege IAM, robust secrets management, and image and dependency scanning; bake security into how we provision and deploy.
  • Author clear design docs, diagrams, and RFCs, and raise the bar for technical writing across the team.

AI-Native Ways of Working

  • Treat AI as your default operating mode — use Cursor and Notion AI across troubleshooting, planning, implementation, and execution.
  • Take any problem as far as you can with AI before reaching for help, expanding the surface area you can own without depending on others.

Technical Depth

  • 5–9 years in platform engineering, DevOps, SRE, or software engineering, with strong production ownership and cross-team collaboration.
  • Proven, hands-on software development experience — you've designed, built, and owned production services (backend, and ideally full stack), not just the infrastructure and pipelines around them.
  • Bachelor's in Computer Science, Engineering, or a related field — or equivalent hands-on experience.
  • Genuinely strong coding ability. We're language-agnostic, but you can build and reason about real software — internal tools, automation, services — not just glue scripts.
  • Strong infrastructure-as-code skills with Terraform (we use Terraform Cloud) for provisioning, upgrades, and environment management. This is a strong preference rather than a hard gate.
  • Solid Kubernetes and Helm experience operating production workloads, with room to deepen on the job.
  • Cloud fluency with a GCP focus today and the appetite to build expertise across all three major clouds (GCP, AWS, Azure) as we unify the platform.
  • Comfortable reasoning about distributed systems, service-oriented architecture, networking, and the hardware and virtualization concepts underneath — CPU, memory, and how a running process actually consumes resources.
  • Working knowledge of databases and transactions — enough to reason about data integrity and trace where a data problem originates.
  • Architectural instinct for ownership and boundaries — what a component should own, and where the line between Engineering and DevOps sits.
  • A high bar for technical writing — clear design docs, diagrams, and RFCs.

AI-Native Mindset

  • AI-native by default: you use AI (Claude, Cursor, Notion AI) for everything — troubleshooting, planning, implementation, and execution — and treat "I don't know" as one prompt away from "now I do."
  • You take a question or task as far as you can yourself, using AI to move confidently into unfamiliar territory, rather than delegating it away — while respecting where another team's ownership begins.
  • You challenge AI output with rigor — you know when to trust it and when to dig deeper.

How you work

  • You enjoy wearing many hats and thrive in a fast-paced, high-ownership environment.
  • You own problems end-to-end — figure out the path and ship the outcome, even under ambiguity.
  • You're obsessed with impact, not activity, and you see DevOps as a force multiplier for engineering, not a gatekeeper.
  • You give and receive direct feedback — say the hard thing, commit, and move forward.
  • You think about the business and the team — you invest genuinely in making the people and systems around you better.

Why work with us?

  • 💵 Salary – The salary range for this role is $135,000 - $165,000 CAD. Your base salary compensation will be determined based on factors such as skills, education, experience, and geographic location.

Why work with us?

  • 🏝️ Paid Time Off – In Canada, everyone gets 4 weeks paid leave plus 11 days of public holidays, as well as an 'end of year shutdown' which is an extra 2 week company holiday. Plus, you are entitled to generous paid sick leave.
  • 🌴 Work remotely – We're a remote-first company — live and work wherever you're happiest in Canada (excluding Quebec).
  • 🤷 Training – We'll support you when you want to learn new skills or pay for conference or course tickets.
  • ❤️ Health Coverage & Retirement – We offer robust medical, dental, vision, disability and life insurance coverages and have a 4% match on Retirement.
Roles similares

Mantén una lista de respaldo.

Ver stack
FocoDevOps EngineeringÁrea del rol
Señal de senioritySeniorNivel del candidato
StackAWS, Azure, GCPSkills principales
Ubicación1 país aceptadoElegibilidad

Stack

Usa estas tags para comparar roles remotos similares.

Elegibilidad de ubicación

Candidatos deberían aplicar solo cuando el país del perfil aparece aquí.

Tu perfilPaís no definidoInicia sesión para comparar tu país con este rol.

Flujo de contratación

WithMira muestra el rol y luego envía candidatos a la aplicación de la empresa.

1Revisa fit del rol, stack y elegibilidad de ubicación en WithMira.
2Abre la página de aplicación de la empresa desde el link rastreado.
3Guarda el rol o suscríbete a oportunidades similares antes de salir.