Skip to content
building.in.public · est. 2026

Vamshi Krishna V.

> Technical Lead & Architect · Patient work, woven in public.

Eleven years shaping enterprise systems. By day, leading API integration at Birlasoft × Synchrony. By night, building Foundry and writing Loomwork.

read loomwork →$ ./view-work
~/foundry — agent runtime
agent latency
0ms
monthly cost
$0.04
tools mapped
0/40
uptime
0.9%
01 // about

I build the unglamorous middle — the integrations, the contracts, the systems that quietly hold under load.

For over a decade I've worked where enterprises feel the most pain: the seams between systems. API platforms, cloud architecture, and the integration work that turns a roadmap into something that ships.

Today I lead API integration for Synchrony through Birlasoft. On the side I build Foundry, and I'm Creator & Technical contributor on MindloomHQ — a curriculum from Python to production AI agents. I built the engineering side; the business operates as a separate principal.

// now
ShippingFoundry alpha — fixing the launcher race condition
WritingIssue 004 — opening Foundry to readers
ReadingA Philosophy of Software Design, Ousterhout
Day-jobTechnical Lead & Architect · Synchrony
Stuck onWhy my retry policy keeps double-firing on cold starts
0
Years shipping
0
Loomwork issues
0
Tools mapped
02 // modules
MindloomHQlive

MindloomHQ

A structured curriculum from Python to production AI agents — 10 phases, 19 courses, a lesson-aware AI tutor, an in-browser sandbox. I built the engineering side; the business operates as a separate principal.

// Creator & Technical contributor
Next.jsTypeScriptSupabaseVercel
Visit MindloomHQ →
Foundrybuilding

Foundry

A launcher and stack-tracker for builders running too many tools. Solving the "40-tool problem" — the cognitive overhead of remembering which subscriptions, which projects, which keys. Documented week-by-week in Loomwork.

// Building solo
Next.jsTypeScriptTauriPostgreSQL
Visit Foundry →
03 // loomwork.log
[08]

The classifier prompt I rewrote four times (and why)

I built a PR classifier for Foundry and watched it score 0%, 29%, 0%, then 65% across four prompt rewrites. The fix wasn't smarter reasoning — the model understood the task the whole time. It was one line forcing a bare, lowercase word instead of a markdown explanation. The real lesson: without an eval set you own, you're not engineering prompts, you're just typing them.
8m[07]

Picking Sonnet vs Haiku per agent (the cost math)

Every agent calls a model, and the wrong model on the wrong job quietly burns money. Haiku for the narrow work, Sonnet for synthesis, a hard ceiling enforced in code. The real per-run numbers — and why the whole pipeline runs for about a dollar a month.
4m[06]

The architecture I'm betting on for the first agent

Before writing a line of the agent, I had to decide what it even is — a monolith, a chain, or a set of small specialists reporting to one synthesizer. The design I committed to, the alternatives I rejected, and the bet underneath all of it.
6m[05]

How I'm using Claude Code to build this

I build Foundry mostly through an AI coding agent — but not the way the demos suggest. The guardrails, the handoff docs, and the gates that keep it from shipping nonsense. The actual workflow behind a solo build that moves fast without breaking the live site.
6m
04 // trace
Apr 2026 → present

Started Loomwork & building Foundry

Weekly Sunday newsletter from a builder with a day job. Foundry — a launcher and stack-tracker for the 40-tool problem — is in active alpha, documented week by week.

2025

MindloomHQ — Creator & Technical contributor

A structured curriculum from Python to production AI agents — 10 phases, in-browser sandbox, lesson-aware AI tutor. I built the engineering side; the business operates as a separate principal.

Sep 2023 → present

Technical Lead & Architect — Birlasoft × Synchrony

API Integration Lead for Synchrony — a Fortune 500 financial services company and the #1 Best Company to Work For in the U.S. (Fortune · Great Place to Work, 2026). Lead architecture and delivery across 5 agile teams; own enterprise API platform on Java, Spring Boot, Apigee, and AWS. Spearhead application migrations and data governance for systems that cannot afford to fail.

Jan 2021 → Sep 2023

Technical Specialist — Birlasoft × Synchrony

Led API modernization and cloud migration to AWS and PCF. Owned solution design reviews, mentored developers, and partnered with business teams to ensure compliance and regulatory alignment.

Mar 2018 → Jan 2021

Senior Software Developer — Birlasoft

Designed and built APIs and microservices for financial applications. Worked extensively with Kafka, messaging systems, and early cloud migration projects for enterprise clients.

Apr 2016 → Feb 2018

Senior Software Applications Developer — CenturyLink

Enterprise Java APIs for telecom domain solutions. Requirements analysis, messaging systems, and system integration work improving scalability across distributed platforms.

Jun 2014 → Mar 2016

Senior System Software Engineer — Great-West Financial

Backend applications in Java and Pro*C supporting financial and retirement systems. First financial-domain engineering — where the habit of boring, reliable infrastructure took root.

2014

First commit, professionally

Java, a monolith, and a deep curiosity that hasn't wound down.

05 // signals
Your clear communication, strategic approach to problem-solving, and approachable nature have truly set you apart. Under your leadership, I was honored to receive the prestigious CEO Award — your guidance and mentorship played a key role in that recognition.
Kanduri Sai Vamsi
Software Engineer II · JPMorgan Chase · Colleague · Synchrony · 2025
He is one of the few I have always admired for honesty, integrity, and dedication — with a habit of going deep on every requirement, not hesitating to bring up risk upfront, and assisting junior team members.
Ajay Yadav
Principal Engineer · Enterprise Architect · Client · Synchrony Financial · 2022
Vamshi was a skilled and trusted team member who was always willing to dig in for the tough issues to find solutions. Very good developer and trusted team member.
Gregg Wachter
Engineering Manager · Comcast · Direct manager · CenturyLink · 2018

Let's build something that scales.

Open to conversations about API platforms, cloud architecture, and AI agents — or comparing notes on building in public.

$ mail vamshi.veggalam@gmail.com →
LinkedInGitHubRSSNowUses