Senior software engineer, four years at Kraken

I’m Victor, from Québec, Canada. I’m looking for a permanent senior role in backend, full-stack, or AI and automation, remote from Québec. I work mostly in TypeScript and Node.js, Rust and Python.

Portrait of Victor Cheeney.

At Kraken

I joined RaritySniper, an NFT analytics startup, in 2022, and Kraken acquired it that year. I grew from associate to senior engineer and left in May 2026. That code is private, so the projects below are what I can show.

  • Built Kraken Verify

    An onchain identity verification product, end to end: Rust backend, Next.js frontend, Kubernetes deployment, dashboards and migrations. I also designed a backend monorepo shared by two Kraken products, and led zero-downtime production migrations.

  • Led an incident fix

    When a production incident made Inky, Kraken’s mobile app for onchain trading, unusable, I took the technical lead, coordinated three engineers, helped find two bugs and shipped an over-the-air fix for each, and had Inky back within three hours. Then I wrote the postmortem.

  • Added a second exchange to Inky

    Put Inky’s derivatives trading behind one exchange-neutral interface, with each exchange as an adapter, then added Nado, a second exchange, through it.

  • Made Inky easier to run

    Added tracing from the app through its GraphQL API to its workers, moved Inky into Kraken’s mobile monorepo so Kraken could drop a paid build service, and wrote and taught the release process the team adopted.

  • Made RaritySniper faster

    Cut database CPU usage by 65% with indexes and continuous aggregates, and cut CI pipeline time by 50%.

All projects

How I work

I build with AI agents every day. These are the rules I keep, on my own projects and on a team.

  1. Start with the smallest fix

    I decide the smallest version that solves the problem before any code. Calendar Checkoff does one thing: Option-click an event to check it off.

  2. AI drafts, I decide and test

    I choose the design and review every change; agents draft the code. When a model is part of the product, I write the rules for trusting its output: in Citius Chrono, a bib read counted only after four checks, and I settled the last 20 or so myself.

  3. Test and check each release

    One command tests, releases and checks the site is live. At Kraken, I wrote the release process my team adopted.

Victor smiling on his time-trial bike at IRONMAN Ottawa.

Off the keyboard

Four IRONMAN finishes

Each race faster than the last. I also coach at my running club, Club Citius.

  1. IRONMAN Mont-Tremblant 202211:17
  2. IRONMAN Mont-Tremblant 202310:49
  3. IRONMAN Ottawa 202510:16
  4. IRONMAN Ottawa 20269:38

Say hello

If you’re hiring, or have a question about something I’ve built, send me a note.

hello@victorc.dev