Dear Hiring Manager,
The first thing I did at Loomis Retail was open the product page on a three year old Android phone, because that is what most of our customers used. The page took eleven seconds to become interactive. I want to build interfaces for people on real devices, not just the ones we keep on our desks, and that instinct is what I would bring to your frontend team.
Good frontend work is invisible when it succeeds, so I judge myself on the moments users never notice. I care about accessible markup that works with a keyboard and a screen reader, component APIs that other engineers can reuse without friction, and a performance budget that is enforced in CI rather than admired in a slide deck. I am comfortable owning the line between design intent and shipped behaviour.
On the Loomis checkout rebuild I replaced a heavy client rendered flow with a streamed, progressively hydrated one and trimmed the JavaScript bundle from 540KB to 190KB. Largest Contentful Paint dropped from 4.2 seconds to 1.6 seconds on mid range mobiles, and mobile conversion rose by 7 percent in the following quarter. I drove the accessibility audit alongside it, taking the page to a clean WCAG AA pass.
I noticed your team is rebuilding the dashboard with a new design system, and the question of how to keep components consistent without slowing feature work is one I have lived through. I would love to compare notes on how you are approaching it. Would you be open to a short call?
Yours sincerely, Priya Nair