Staff software engineer, Toronto

I make platforms faster, cheaper and quieter at 3 a.m.

I graduated in engineering from McMaster in 2016 and now work as a staff engineer on a platform that hundreds of developers deploy to. I like work I can measure: a latency, a bill, an uptime figure, a page that did not go off.

Placeholder artwork for a portrait: a simple head-and-shoulders figure in warm greys on a pale circle, with a small rust-red dot

Where I focus

  • Reliability

    Service level objectives, on-call that people can sustain, and incident reviews that change the system rather than blame a person.

  • Performance and cost

    Profiling first, then fixing the one thing that matters. I report savings in Canadian dollars and milliseconds, not in effort.

  • Platform and developer tools

    Deploy pipelines, service templates and internal docs that make the safe way the easy way for teams I do not manage.

  • Technical direction

    Writing design documents, reviewing other teams' designs and deciding with them what not to build.

Four projects with the number each one moved. The figures are illustrative: this is a sample résumé for a fictional person, and none of it describes real work at any company named here.

Career, by level

  1. Staff engineer

    ShopifyToronto, remote-first

    – Present

    Technical lead for the deploy platform and its three teams. Promoted after two years as a senior engineer, on a case I wrote myself and that my manager and two other staff engineers reviewed.

    • Cut the median deploy from 22 minutes to 6 across about 140 services.
    • Led the move of 90 services to one service template; pager volume fell by a third.
    • Run the yearly design review program and mentor three senior engineers towards staff.
  2. Senior engineer

    ShopifyToronto, remote-first

    –

    Joined sideways at the same level I held before, for a larger platform and a clear path to staff.

    • Redesigned the event pipeline from 4,000 to 120,000 events a second without a rewrite.
    • Cut the cloud bill for the shared clusters by 41% in twelve months.
  3. Senior developer

    WealthsimpleToronto

    –

    Promoted after two and a half years at the company, in a fintech team that cared about correctness.

    • Took the search API's p99 latency from 840 ms to 210 ms by fixing one query plan and adding a cache with a proper expiry.
    • Introduced service level objectives; customer-visible downtime fell from twelve bad days a year to two.
  4. Intermediate developer

    FreshBooksToronto

    –

    Hired one level up from my old title, as a feature developer on a billing service. Intermediate is the common Canadian step between junior and senior.

    • Owned the service's database and moved it to a managed one with no downtime.
    • Ran the team's first on-call rota, with a written handover guide.
  5. Software developer

    WattpadToronto

    –

    First job after university, with a title that said junior in all but name.

    • Wrote most of the first public API and its test suite.
    • Learned to run production the hard way.

Tech stack

Languages

  • Go
  • Python
  • TypeScript
  • SQL

Platform

  • Kubernetes
  • Terraform
  • AWS

Data and observability

  • PostgreSQL
  • Kafka
  • OpenTelemetry

Talks, open source and education

  1. Talk: Paying for reliability you can measure

    A Toronto DevOps meetup

    Thirty minutes on setting service level objectives with a product team.

  2. Organizer, a Toronto platform engineering meetup

    Community

    – Present

    Monthly evening talks and a lightning-talk round. Co-organized with two other engineers.

  3. Maintainer, tracepipe

    Open source

    – Present

    A small Go library for tracing pipelines. Two co-maintainers, a release every six weeks.

  4. Certified Kubernetes Administrator

    Cloud Native Computing Foundation

    Passed first time; renewed in 2024.

  5. BEng Software Engineering

    McMaster UniversityHamilton, ON

    –

    Final-year project on scheduling jobs across unreliable machines.

Get in touch

I am happy to talk about platform work, reliability and how to grow as an engineer. Email is best; I reply within three working days.

Email
hello@mira-castellan.example
Based in
Toronto, ON; open to remote work in Canada and the US
Talks
Reliability, platform teams and career growth