02Previous engagement · Banking
THROUGH INFOSYSLess waiting. More doing.
Performance work that made data-rich banking interfaces faster and easier to maintain.
Citi
Infosys
01The challenge
Complexity should not feel slow.
Data-rich enterprise screens need to stay responsive as features and state grow. My focus on the Citi engagement was to improve loading and rendering while continuing to ship product features.
02Think in systems
The interface is
only the visible layer.
User intent
An interaction should trigger the smallest useful update. Make loading, success, and error states explicit.
A conceptual explanation of frontend responsibilities, created for this portfolio. It does not document a client’s private system.
03My responsibility
Where I made
the difference.
- 01
Built 20+ interactive features, including dashboard graphs and data visualizations.
- 02
Applied code splitting and lazy loading to improve page load performance by 40%.
- 03
Optimized application state and component rendering, reducing unnecessary re-renders by 35%.
- 04
Worked with product, QA, and DevOps, and mentored three junior developers.
04Impact & quality
better page load performance
Reported career outcomes for the Citi engagement. These figures are not this portfolio’s Lighthouse or Core Web Vitals results, and no private performance traces are reproduced.
Quality is part of delivery.
State and API optimization work alongside regression coverage, code review, and collaboration with QA and product teams.
05The outcome
Built for what
comes next.
Faster page loads, fewer unnecessary renders, and reusable React components that supported continued feature delivery.
React / TypeScript / Next.js / Performance