Aryan Saxena

Toronto, Canada

9 AM — 5 PM — 9 PM

Software engineer.
Up for an adventure.

At Air Canada, on the Aeroplan loyalty platform.

9 AM–5 PMThe work 5 PM–9 PMOff the clock

Delhi → Montreal → Toronto

Take a look
9 AM–5 PM

The work

Aeroplan

Inside Aeroplan.

Partner integrations, identity and consent at Air Canada.

A core member-context service in production
2 million+requests a day
Tooling and repo standards rolled out across
50+repositories · around 65 developers

Integrations I’ve worked on

Built from the Air Canada side.

  • Hyatt
  • Avolta
  • Uber
  • Chexy

An investigation / iFly

Where were all these requests coming from?

A traffic spike. No source in the logs. One trace back to the caller.

Request traceiFly / 250 TPS
01 / 05Over the limit.

Illustrative request flow from another team’s Lambda through our service to iFly. All investigation findings are listed beside this diagram.

Illustrative trace

  1. 01

    Over the limit.

    Requests to iFly exceeded our 250 TPS contract.

  2. 02

    No source in sight.

    AWS logs couldn’t identify the team. Request IDs had no source prefix.

  3. 03

    Follow the caller.

    I used Dynatrace to trace the requests to another team’s Lambda.

  4. 04

    A deployment backfill.

    Historical data had been prefilled during a deployment.

  5. 05

    Make the source visible.

    We shared the findings with the integration team and pushed for company-wide source prefixes in request IDs.

01

Partner linking

Linking Aeroplan accounts with hotel, retail and mobility partners.

I worked through API contract mismatches, corrected specifications and traced failures back to their source.

02

Consent migration

Two platforms running in parallel through the cutover.

I led a parallel ingestion path so marketing operations could continue without a gap in consent state.

03

Developer tooling

Shared conventions for 50+ repositories and around 65 developers.

I worked with DevOps on the move to GitHub and Serverless v4, with repo conventions and CI/CD guardrails.

Along the way

  1. Air Canada

    Software engineer

    Toronto · 2024–present

  2. Intact Financial

    Software developer intern

    Montreal · 2023

  3. Insight Enterprises

    Cloud engineer

    New Delhi · 2021–2022

Concordia University

MSc Applied Computer Science

Montreal · 2022–2024

3 AWS · 3 Azure

  • AWS Developer – Associate
  • AWS AI Practitioner
  • AWS Cloud Practitioner
  • Azure Developer Associate
  • Azure Data Fundamentals
  • Azure Cloud Fundamentals

AWS · TypeScript · Node.js · Python · Java · Kafka · Dynatrace

5 PM–9 PM

Off the clock

Better with company.

Trips with friends, football, a board game — I’m happy to join.

A few things I make time for.

  • Standby

    A standby board: three seats, five names, and you waiting in the middle.

  • Next stop

    Depends on the standby list.

  • Board games

    A single die, waiting to land.

  • Swimming

    A swimmer between pool lane ropes, counting lengths.

  • Football

    A football lined up with a target. Time the shot to hit the centre.

  • Reading

    A shelf of books. The pink spine pulls out and opens to a bookmarked chapter.

  • Music

    Five equalizer bars respond to a tapped rhythm. Entirely silent.

  • Coding

    Three lines of code. The bug is on line 2: use === to compare, not = to assign.

9 PM

Got a plan?

A project, a trip, or just a hello.

Made with curiosity, and a little help from AI.