Principal Engineer

** This is an opportunity to work for a remote-first company. Only applicants living in British Columbia will be considered for the role. Must be legally eligible to work in Canada.**

Driven by PLAYER OBSESSION, we earn our players’ trust by understanding their needs and creating experiences that put them first.

OWNERSHIP means we take responsibility for our work and outcomes; we follow through, learn from mistakes, and never say “that’s not my job.”

With RESOURCEFULNESS, we do more with less, finding creative ways to overcome challenges and deliver impactful results.

Grounded in CONTINUOUS IMPROVEMENT, we are relentless in our pursuit of better; for ourselves, our games, and our players.

At Kano, we build communities through gaming experiences that connect millions of players worldwide. We are looking for a hands‑on Principal Engineer (P4 Software Developer) to take ownership of Technical Excellence, Security and Privacy, and Platform Operations across all products. You will manage the Operations team, work closely with Product Tech Leads through a dotted line, and report directly to the President.

You will set technical vision, make high‑impact architectural decisions, and raise the bar on performance, reliability, and quality. You will mentor engineering leaders and individual contributors. You will jump into the details when it matters, lead incident response with calm command, and turn risk into clear roadmaps that ship.

Location: Remote within British Columbia, Canada

• Drive Technical Excellence:
  Define and drive a studio‑wide program for quality, performance, and continuous improvement. Establish performance budgets, prevent regressions with automated checks, and improve DORA delivery metrics.
• Lead Security and Privacy:
  Be the accountable owner for Security and Privacy. Keep us up to date and ahead of Platform Security requirements.
• Manage Operations and Reliability:
  Lead the Operations team. Set Service Level Objectives with error budgets, design graceful degradation and failover, define on‑call and runbooks, and drive post‑incident reviews that deliver durable fixes.
• Build Observability and Error Monitoring:
  Standardize logs, metrics, traces, and real‑time error and crash reporting across backend and clients. Create actionable, SLO‑based alerting and executive health dashboards.
• Improve Developer Productivity and the Software Development Lifecycle:
  Level up CI/CD, branching strategy, and change control. Add quality gates, static analysis, secret scanning, SBOM and dependency management, and supply chain controls.
• Drive Fin Ops:
  Own cloud budgets and forecasts. Improve commitment coverage, right‑size compute and storage. Report monthly on cost versus performance.
• Lead Incidents and Risk:
  Act as incident commander for high‑severity issues. Run table‑tops, keep risks tracked with owners and dates, and prevent recurrences.
• Mentor and Develop Leaders:
  Coach Tech Leads and senior ICs. Set expectations for design docs, code reviews, and outcomes. Build a culture of clear ownership and a bias toward delivering.
• Partner Cross‑Functionally:
  Work with Product, Legal, Finance, and Player Success to align technical plans with business goals and regulatory needs.
• Leverage AI as a force multiplier:
  Use AI to accelerate development and operations (code assist, test generation, incident triage, analytics).
• Own SRED:
  Create an auditable process with eligibility gates in Jira, contemporaneous notes, and artifact capture. Partner with Finance for accurate, on‑time claims.

• 10+ years in software engineering with 3+ years as a principal‑level platform/architecture leader
• Strong AWS background (IAM, VPC, EC2/ECS/Fargate, S3, KMS, Guard Duty, Security Hub, Cloud Trail, Config)
• Infrastructure‑as‑code proficiency (Terraform or CDK) and CI/CD tooling (Git Hub Actions or equivalent)
• Security and privacy ownership in platform‑reviewed environments
• SRE and performance engineering expertise (SLOs, incident management, load/perf testing, graceful degradation)
• Data architecture across relational and non‑relational systems
• Observability stack experience (Graylog, Open Telemetry,…