Context before prompts
An agent needs what a new engineer needs: a map of the system, the team’s standards in writing, and the right tools.
About

Senior software engineer and tech lead in the Denver area, working on fintech APIs and AI agent tooling.
I started in technical support at a card-payment company, configuring devices and fixing merchant accounts. To handle the repetitive parts of the job, I taught myself Python and automated account setup, returns tickets, database repairs and reporting. I earned a computer science degree at the same time, while working full time.
Charles Schwab hired me through its new-developer program in 2021. I’ve spent nearly six years since on the platform financial advisors use to move money and securities between their clients’ accounts, and on the APIs that let outside firms submit the same requests from their own software. I work across the stack in C#/.NET and Angular.
Before taking the tech lead role formally in November 2025, I had been doing much of it: onboarding new engineers, coordinating across teams and leading a major approval-workflow feature to release. Today I own delivery, API contracts and production readiness, and I still write and review code.
Automation has been the common thread. Most recently I designed a GitHub Copilot toolkit of agents, skills, instructions and scripts that my team uses for code review, delivery and production triage. Read the case study.
Currently Tech lead at Charles Schwab. Building a public demo of the agent toolkit.
An agent needs what a new engineer needs: a map of the system, the team’s standards in writing, and the right tools.
Pushes, merges, ticket changes and messages wait for a person to approve them. These guardrails are why the team trusts the tools enough to use them.
Agent output should be easy to check: a timeline, a link to the log entry, the file and line it points to. Output that can’t be verified quickly isn’t finished.
Adoption is voluntary, so the first tools targeted the repetitive work that cost the team the most time.
Senior software engineer and tech lead on the platform financial advisors use to move money and securities between client accounts. I lead delivery of partner APIs, own API contract governance and performance baselines, am the team’s primary code reviewer, and built the agent toolkit we use day to day.
Technical support for the CryptoPay card-payment platform. I taught myself Python here and automated account setup, returns tickets, database repair and reporting.
Role-by-role detail is on the résumé. See the résumé
04Contact
For questions about this work, reach me on LinkedIn or by email.