Frontend Platform Engineering · Fintech
Senior frontend engineer with 6 years building the systems behind fintech products used by hundreds of thousands of SMBs. I specialize in microfrontend architecture, GraphQL-driven UI surfaces, and cross-platform SDK development. The work sits at the layer where product teams meet platform scale.
What I'm looking for
Senior/Staff Frontend roles at companies investing in frontend as a platform. Fintech, devtools, or product orgs scaling beyond 20+ frontend engineers.
Career progression across fintech platforms, product engineering, and scalable frontend systems.
Full-time · Jul 2021 - Mar 2024
Software Engineer Intern
Shipped iOS 14 widgets for the flagship app and built serverless incident tooling (AWS Lambda, Terraform) that cut operational costs by ~10%.
Software Engineer
Built AWS S3 content delivery and adaptive video streaming for an edtech platform, lifting daily active engagement ~20%, and mentored junior engineers.
Application Engineer
Summer internship: production debugging and JIRA-driven issue analysis with data-backed UX recommendations.
A map of how I connect product surfaces, platform foundations, and delivery systems.
Patterns I have shipped, written to be reused. The structure, the cost, and when to reach for something else.
Split a frontend along ownership and deploy cadence, not along technical layers or page routes. The boundary is right when a team can ship its surface without coordinating with anyone else.
Platform DesignTreat the schema as a published contract with named owners and a deprecation policy, not as a type file any team may extend. Federation distributes authorship, which makes ownership the thing that has to be designed.
SDK ArchitectureShip an SDK as two layers: a headless core carrying logic, state, and API contracts, and a UI layer built on top of it. Clients take both or take only the core, without either path being second class.
Grouped around the systems I build and maintain.
Hover any cluster to explore
A personal project I'm actively developing outside of work.
Interactive study tool for Senior Frontend interviews
58 topics · 13 categories
Full senior frontend interview spectrum: JS, TS, CSS, React Core, Patterns, State, Testing, Performance, and more.
Live Sandpack editor
Each topic ships a pre-loaded code sandbox. Edit in-browser and see results instantly with no setup.
React Flow DAG roadmap
Visual dependency graph of all topics. Hover for tooltips, click to jump. See what to learn in what order.
Progress tracking
Mark-as-complete system with localStorage persistence. Your progress survives page refreshes.
Stack
Real problems, real constraints, and the platform decisions behind them.
BILL
Problem
BILL's Accounts Receivable platform was built on a legacy monolithic frontend. Slow to ship, difficult to test, and increasingly misaligned with the scale demands of hundreds of thousands of SMB customers.
Approach
Led modernization of core AR workflows into scalable microfrontend experiences. Integrated GraphQL-driven data fetching, rationalized LaunchDarkly feature flags, standardized Playwright automation patterns, and drove cross-functional alignment across product, backend, and platform teams.
Result
Shipped Bulk Mark as Paid, Recurring Invoices, Scheduling, Payment Links, and invoice customization, expanding AR capabilities for the full customer base. Measurably improved frontend performance, test coverage, and engineering velocity across critical workflows.
BillGo
Problem
Every new fintech client integration required bespoke frontend work from scratch. Duplicated effort, inconsistent quality, and multi-month timelines that blocked commercial growth.
Approach
Architected a cross-platform SDK with a clean headless/UI library split, giving clients flexibility without sacrificing consistency. Built native iOS and Android reference apps to validate the architecture, implemented Detox-based automation, and set up GitHub Actions pipelines for continuous delivery.
Result
Reduced downstream integration effort by approximately 90% across multiple client implementations. Cut end-to-end testing time by 50%. Delivered a platform that let new clients go from zero to integrated in days instead of months.
Notes on platform-scale frontend. What worked, what surprised me, and what I'd do differently.
You can have the best performance tooling in the world and still ship a slow product. Fast teams do not have better tools. They have different defaults.
Rewrites get underestimated by 3x because the old system refuses to stand still while you rebuild it. When rewriting is genuinely right, when it is not, and how to make the call honestly.
Your types at the API boundary are a description of last week's schema, not a guarantee about today's. Most teams have end-to-end type theater, and the gap only shows up at runtime.
Every field you add to a GraphQL schema is a promise to every consumer. The teams that do GraphQL well treat the schema like a roadmap, not a database migration.
Most shared component libraries are graveyards within 18 months. Not because engineers built them wrong, but because adoption was never the actual goal.
Feature flags solve real problems early, but become technical debt unless managed rigorously. A pragmatic look at when they make sense and how to keep them from consuming your codebase.
A working framework for deciding which workflows become independent microfrontend surfaces and which stay in the monolith. Drawn from modernizing BILL's AR platform.
How splitting a fintech SDK into a headless layer and a UI layer let the platform work for both fast-moving and design-strict client teams, without forcing either to compromise.
Up next
The monorepo vs polyrepo debate resurfaces every few months, and it is almost never about repo structure. Slow CI, unclear ownership, and under-funded tooling wear the repo as a costume.
What managers and peers I've shipped with say.
Josh Foeh
Staff Software Engineer at BILL
Senior peer at BILL
“I've been consistently impressed by his ability to understand exactly what needs to be built and then to build it at lightning speed. His questions are thoughtful and show that he approaches problems from a holistic perspective rather than just trying to close a ticket.”
Becca Moss
Staff Software Engineer at BILL
Senior peer at BILL
“Anshul combines strong engineering skills with a genuine commitment to our customers. His customer-first mindset makes him a trusted partner across the organization. He is an outstanding teammate, thoughtful, collaborative, and always willing to help others succeed.”
Earlier endorsements
Chris Petrillo
Innovative Software Engineering Leader
“Anshul single-handedly productized our native offering and delivered it plug-n-play-style in iOS and Android. He will be an indispensable asset to any team.”
Manager at BillGo · January 2024
Jacob Juszak
Full Stack Engineer
“He writes code at a very fast pace, but does not lose any quality in doing so. He consistently provides high-value code reviews and is one of the best developers and teammates I have worked with.”
Senior peer at BillGo · January 2024
Dheeraj Jain
Technical Head
“Diligent and meticulous in his work and has a keen eye for detail. His outstanding interpersonal skills are noteworthy in context of team building and the overall success of the project.”
Manager · 2-year working relationship · August 2019
Nitin Khurana
Software Architect · Android and iOS Applications
“He starts and finishes anything given to him with full dedication and energy. His understanding and problem-solving ability separates him from everybody else.”
Peer · 2 years on the same team · August 2019