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.

How typical is this path?

Graduate to staff in eight years is possible, but at the quick end of what published numbers suggest, and staff roles are scarcer in Canada than in the United States. Figures are approximate; sources are in the notes file that ships with this template.

  • Senior at about four years

    Typical is roughly four to seven years of experience, so promotion after four and a half years, helped by one move, is at the fast end of normal.

  • Staff at eight years

    Typical is eight to twelve years or more, and many strong engineers never go. Eight is possible, not average.

  • Fewer staff roles here

    Toronto has plenty of senior roles but fewer staff and principal ones, and the best-paid are often at US companies with a Toronto office or on remote US teams.

  • Moving helped

    The jump to Intermediate and the sideways move to a bigger platform both came from changing company, which is common and often faster than waiting.

The honest caveats

Would this be faster at a big tech company?

Not necessarily. Large companies have clear levels and slow, committee-based promotions: staying at senior for years is normal and by design. Start-ups promote faster and give bigger titles for less proven scope.

Is a title the same everywhere?

No. Canadian titles run Junior, Intermediate, Senior, then Staff or Principal, but a senior developer at a start-up may match a mid-level engineer at a large company. Compare levels and scope, not titles.

What about moving to the United States?

It is a common route to higher pay and more staff-level roles. Some people move on a TN visa, some stay in Toronto and work for a US company remotely or from its Toronto office. I have stayed, and I weigh pay in Canadian dollars against the cost of living here.

Why not management?

I tried a six-month acting team lead stint in 2023 and went back to the technical track. Many engineers who want more scope go to management; the senior to staff step is often harder than the senior to manager one.

What mattered most?

Owning an outcome end to end, writing it up so others could use it, and changing companies when the next level was not on offer. Not hours, and not any one technology.

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