Anshul
Shanker
Engineer at heart. I build systems, think about how teams build software, and occasionally write down what I figure out.
I'm a staff engineer at OneMain Financial in Chicago. My day-to-day lives at the intersection of product, architecture, and delivery — working on the loan servicing experience that over a million customers use every month, across a stack of distributed services that really can't have a bad day.
I've been in fintech long enough to have opinions — about how roadmaps get shaped, where architecture decisions actually get made, and why delivery falls apart in the same places every time. Loyola CS grad, for what it's worth (Go Ramblers 🐺).
As AI became part of how engineering teams work, I started noticing a pattern — teams shipping faster individually but drifting apart collectively. Code style, architecture decisions, design intent: all quietly diverging with every AI session. The tooling was great. The structure around it wasn't. I spent a long time thinking about how to fix that without adding ceremony nobody has time for. That became PACE.
📍 Chicago, IL
PACE: Plan, Agentic Context, Execute
A framework for teams adopting AI coding tools — structured context, versioned blueprints, and a design review gate before any agent writes application code. The missing governance layer most organisations realise they need after the fact.
Read the paper →Say hi