(2022-2026) as an everything-dev (literally: backend, fullstack web, qa), during which I:

• (proudest milestone btw) Independently redesigned and rebuilt the 15-year-old recommendations experience
• With enough hot-fixes over 15 years, recommendations were broken -- mostly only worked in English (despite being live in non-English marketplaces); the same content being recommended to a customer multiple times on the same page; all customers getting the same “personalized recs”; recs straightup not working in some countries; requiring a 2-week deployment cycle for updates; infrastructure costing our team over $3000 a month; I really can keep going :(
• migrated the experience to a modern tech stack to leverage AWS-powered improvement → infra costs dropped by 99% (under $30 a month world wide); availability at/over 99.999% world wide (yay, revenue); 14-hour deployment cycles; cut latency from >700ms to 200ms in our worst region
• migrated from Audible’s custom recs engine to a more robust one owned and managed by a dedicated Amazon team for consistent, personalized, and less-repetitive recs for customers → CTR (click-through-rate) on recs increased over 50%, directly translating to revenue
• wrote comprehensive unit, integration, and end-to-end tests and integrated those into the deployment workflow → removed the need for manual QA; reduced new bugs shipped to production to zero
• fixed existing accessibility issues and added checks to the deployment workflow → making sure accessibility wouldn’t silently be neglected again
• made it easier and faster for Audible to expand its presence to non-Audible pages on Amazon retail websites
• Audible historically struggled (time and effort) to expand its presence to other Amazon pages
• I led design and implementation across the board (frontend, database, recommendations-generation, checkout experience, and cart teams), and helped various Audible teams switch to modern Amazon tech stacks → had new features ready to launch in as little as one month, where similar efforts previously took multiple quarters
• fixed a bunch of things that bothered customers, other devs, and/or me :)
• credit and membership APIs were violating SLAs
• I refactored both APIs to execute asynchronously → reduced API latencies by 40-50%
• Audiobooks were incompatible with Amazon’s cart-based widgets, forcing teams to own a frustrating number of custom implementations of widgets available to other teams
• I reviewed a painful chain of APIs, found a ‘!’ (required param) in a client where docs and server expected an ‘?’ (optional param) , and shipped a non-intrusive fix → eliminated the need for custom widgets, saved Audible devs from needing to “reinvent the wheel”, made sure future devs
• WhisperSync For Voice (Audible + Kindle) customers frequently complained about price inconsistencies across various pages
• I centralized backend pricing logic → ensuring customers always see the best eligible price for audiobooks, regardless of the page
• the legacy sample player was a mess (inconsistent across pages, suspiciously high latency, poor accessibility score)
• I refactored the sample player and published it as a reusable widget → latency dropped by 75%, resolved 100% of flagged accessibility issues at the time
• mentored and/or onboarded transfer-teammates, new hires, and interns :)

(2021-2022) as an android developer on a 2-man team, during which I:

• implemented a credit-line-increase workflow (frontend and backend) for the Barclays android app
• helped implement a digital onboarding workflow for new customers ahead of Barclays’ acquisition of GAP’s credit card portfolio in 2022