Resume and public footprint
Do these before the next HM screen. Each row is a cleanup item from resume vs evidence ledger. I don’t wait for chapter 3 to start asking AI-platform recommenders — that warmth runs in parallel.
Checklist
| # | Fix | Today | Target wording | Status |
|---|---|---|---|---|
| 1 | Experience years | “19 years”; FTE timeline from 2009 visible | Keep 19 years; add pre-2009 internship lines (employer/dates/role) so the math is auditable | [x] count locked · [ ] internships listed on PDF |
| 2 | Lucid dates | PDF: “Nov 2023 – Aug 2026”; still FTE, looking out | Nov 2023–present everywhere public; looking-out private until disclosed | [x] status locked · [ ] PDF date line updated |
| 3 | Substack count | “18 essays” | Live RSS count on interview week | [ ] |
| 4 | Easy to misread as Google employee | “Apple/Google client work via Sparity” everywhere | [ ] | |
| 5 | BS school name | “Jawaharlal Nehru University, Anantapur” | Exact diploma name (often JNTU Anantapur) | [ ] |
| 6 | Open vs Lucid | Resume keeps “Designed AegisAI” Lucid bullet (no rewrite) | Spoken: Lucid required gateway/HITL/audit; public AegisAI is O inspectable pattern — not Lucid’s GitHub binary | [x] resume decision locked · [ ] rehearse spoken line |
| 7 | Catalog numbers | “12 live / 18 repos” | Recount from one canonical source before each screen | [ ] |
| 8 | LinkedIn headline | May still read general | Paste the pitch-page headline (governed agents / Sr Staff AI Platform / Founding) | [ ] |
| 9 | LinkedIn Featured | Weak / mobile-era | Featured: hire + AegisAI + technical-review | [ ] |
| 10 | Recommendations | iOS/mobile quotes dominate | Ask 3 AI-platform recommenders — referrals | [ ] |
| 11 | EDI / savings wording | PDF: “projected $5–7M” and/or “$8–9M” / rolled-up “$10M+” | Spoken + new PDF: $10M TrueCommerce licensing eliminated (realized) + $7M annual net after platform costs; Kafka $1M+ separate. Do not mash. | [x] spoken locked 2026-08-13 · [ ] PDF source still stale |
One-paragraph resume summary (paste)
Principal-depth AI architect (Sr. Staff title at Lucid, Principal-scope work) with 19 years shipping platforms (including documented pre-2009 internships). Last three years: governed agent systems — runtime policy/HITL/audit, access-aware RAG, eval-gated CI. At Lucid (Nov 2023–present) led enterprise AI 0→1: in-house EDI/supplier platform for 20,000+ suppliers (3 orchestrators, 34 specialists, dual RBAC UIs) — $10M TrueCommerce licensing eliminated, $7M annual net — plus Kafka/MSK ($1M+) and multi-rail payments (Stripe, GIB, Chase ACH). Public inspectable spine: AegisAI, Enterprise RAG, VAP, golden-eval CI — principles aligned with production work, not a claim those repos ran inside Lucid. Earlier: Volvo multi-market ecommerce (Java/Spring), Kaiser HIPAA platform leadership, Sparity Apple/Google client engagements.
LOCKED 2026-08-13: spoken savings = $10M licensing eliminated + $7M net (realized). Still do on PDF: date → present; add internship rows; replace “projected $5–7M” / “$8–9M” mush.
LinkedIn About (short)
Same paragraph + CTA:
Open to Sr Staff / Principal AI Platform and Founding roles. Technical review: https://venkat-ai.com/technical-review
FDE / Applied flavor is a sentence, not a second About: discovery → wedge → HITL for irreversible tools. Same person.
Spoken lines I use when the PDF is still dirty
“Were you a Google employee?”
No. Apple and Google were client engagements through Sparity. I don’t claim a Google W-2 I don’t have.
“Are you still at Lucid?”
Yes. November 2023 through present. I’m looking, confidentially.
“Your resume says 19 years but I only see 2009.”
The count includes pre-2009 internships. I’ll get those rows on the PDF. Until then I can name dates and employers — I’m not going to let the math look like a trick.
Spoken line I rehearse for AegisAI
At Lucid I required gateway, HITL, and audit for agent side effects. The public AegisAI repo encodes that control-plane pattern so a panel can inspect it. I’m not claiming Lucid ran that binary.
What I will not “fix” by inventing
- Fake P95 / SLO tables
- Fake Google employment
- Claiming public AegisAI is Lucid’s production binary
- Softening 10→2 into “redeployed” if eliminations happened