I'm a software engineer at PayPal, working on the internal Agent Toolkit. It decides which checkout, merchant, and invoicing operations an AI agent is allowed to perform, and holds that line when one asks for more.
Most of what I build has to hold up when something goes wrong. A wallet ledger that rebuilds every balance by replaying its event log. A proxy that cuts token spend and then has to prove it didn't change the answer. I like working under that kind of constraint. It makes you say out loud what happens on failure instead of hoping it doesn't come up.
Before this I spent two years at Deloitte on an internal search platform, getting compliance and policy documents in front of the people who needed them without getting them in front of anyone else. Different domain, same shape of problem: someone eventually asks what the system did, and the honest answer has to already be written down.
The agent work turned out to be made of familiar parts: keeping events in order across processes, checking that a system actually did what it said, and making any of it readable to the person watching. What's new is the blast radius, since the tool on the other end moves money.
I also taught Python and AI at Fullerton for a year and a half, around 40 students a section. Reading that many submissions changes how you write code. You start noticing every way an instruction can be misread.
I'm in San Francisco, CA. If you want to talk about backend systems, distributed systems, or agent infrastructure, email me.