Joined Atlassian on the Jira platform side, focused on performance and developer experience. Headline impact across my tenure on Jira CI: • Rebuilt CI reliability from 56% → 99.6% (from "engineers can't trust green" to best-in-class), cut CI cost by 44%, reduced pipeline runtime from ~80 min to under 30 min. Deploy velocity across Jira engineering moved meaningfully as a result — one of the highest-leverage internal-platform investments made that year. • Built a hybrid deterministic + AI model for build failure classification that made above possible, hitting 97%+ accuracy. • Led a 5-engineer team building Jira's next-generation performance test framework — covering site inflation (populating realistic customer-scale data), test execution & validation, and analysis pipelines. This became the standard framework Jira teams used to validate performance before large rollouts. • Served as AI & Ops Champion for the team — designed and shipped automation for PR reviews and work item triaging, further reducing manual overhead across engineering..

Software Engineer II on the devices team, working on the cross-platform UI stack powering Amazon's hardware devices. • Built a React Native-like cross-platform UI framework tailored specifically for Amazon's hardware — off-the-shelf frameworks couldn't meet the memory, performance, and hardware-integration constraints of embedded consumer devices, so the team built its own. My work spanned the framework's runtime and developer-facing APIs.

Joined BlackFish (Marlin Protocol) as one of the early engineers when the team was ~5–10 people. Over 3+ years I: • Architected AWS Nitro Enclave-based microservices in Rust for a secure distributed processing product — a stack almost no Indian teams were running in production at the time • Built the company's blockchain indexer from scratch (Go + Postgres + Redis) — the data layer several downstream products depended on • Set up GitHub Actions pipelines for both public and beta release channels • Designed and shipped a custom CLI that handled configuration, downloads, and version upgrades for end users This chapter is why I understand early-stage engineering realities from the inside — small team, hard problems, no dedicated infra/DevOps org, ship-or-die urgency.

▪ Full stack development for a game with over 4 million daily active users. ▪ taking a feature from an idea to the production ready state ▪ deciding and reviewing designs to make highly scalable systems ▪ build logic and system for detecting fraud/cheating in game

▪ Design and development of scheduler in the L2 layer. ▪ Improving the performance of the current system. ▪ Volunteered and solved a tough design problem which had a huge business impact. ▪ Leader of the team responsible to enhance problem solving skill among other employees. ▪ Winner of the in house Professional coding challenge (among 600 participants).

▪ Design and development of various features. ▪ Building high optimised systems real time systems. ▪ Leader of the team responsible to enhance problem solving skill among other employees. ▪ Winner of the in house Professional coding challenge (among 600 participants).

▪ Automated the testing of modules ▪ Found good performance improvement and reduced complexity of the system