San Lee

Senior Product Associate, Content Creation & Collaboration · Jersey City, NJ

• Own planning, build, and delivery of collaboration features across SharePoint Online and OneDrive for the entire firm (300,000+ employees), moving them through a structured release lifecycle.
• Drive an on-premises SharePoint to SharePoint Online migration for the firm's data retention and governance groups: run the weekly stakeholder cadence, structure unstructured requirements, and present them to a vendor, internal engineering, and Microsoft.
• Run the program standups and the migration office hours that support 200+ employees a week; send technology communications across lines of business and support OneDrive migrations.
• Launched a SharePoint Framework (SPFx) pilot with recruited users; field feature requests across lines of business, including a proof of concept for executive directors.
• Run incident response for the migration queue, troubleshooting blocking issues directly with Microsoft engineers; built Power Automate flows that cut its manual triage.

Full-time MBA in Seoul, South Korea — career break for graduate study, then relocated back to the U.S. Details under Education.

Senior Associate, Software Engineer III · Jersey City, NJ

• Built and ran microservices on a 4–5 engineer team working toward zero-touch provisioning (ZTP) of network devices — fully shared ownership, everyone with a hand in every service rather than an isolated slice.
• Practiced test-driven development and pair programming; designed and documented REST APIs (Swagger/OpenAPI), containerized services with Docker and Kubernetes, built event-driven flows with Kafka, maintained CI/CD pipelines, and remediated security scan findings to firm standards.
• Worked with SRE on observability — instrumenting endpoints and tracing API calls with OpenTelemetry to troubleshoot latency — and shared the team's operational load: documentation, on-call, and weekend failover and resiliency testing.
• Right-sized infrastructure orders to “just enough” to keep costs in check; pushed back on stakeholders with clear tradeoffs to keep scope and budget grounded.

Analyst, Merchant Services Command Center Engineer · Jersey City, NJ

• Owned real-time monitoring and incident response for mission-critical merchant network systems supporting $1T+ in annual transaction volume.
• Coordinated cross-functional triage across engineering, infrastructure, and operations — prioritizing by business impact and risk — and drove systemic fixes that reduced recurring incidents.

Corporal, Infantryman / Team Leader · Freehold, NJ

• Led a 3-person infantry team on a security-force (SECFOR) deployment to Qatar (Operation Enduring Freedom, 2014–2015) — entry-control-point and guard-tower operations; honorably discharged.

Built and documented in the open — every claim links to its writeup and public code. sanlee.me

• LLM eval harness (defense-news classifier) — built the eval before trusting the model: an LLM-as-judge scored against a hand-labeled gold set caught two changes I'd have shipped on instinct (a “cleaner” prompt, an unproven retrieval add) that actually regressed accuracy. The product call: gate every change on evidence, not on how confident it feels. → sanlee.me/projects/defense-news-classifier
• telltale — a Go terminal app whose council mode puts one brief to five coding-agent CLIs side by side (Claude Code, Codex, Antigravity, Cursor, Grok), over a cross-vendor statusline and HUD. Every number comes from measured tool output; an unmeasured reading renders absent, never zero. Ran a month-long evaluation of the AI coding agents against a fixed close date; the result changed my operating policy. → sanlee.me/projects/telltale · github.com/sanlee-ys/telltale
• Cross-repo LLM system — evidence-gated model routing (cheaper model by default, escalate only where an eval proves the lift), wired across three services with frozen wire contracts and an idempotent async pipeline. Built the premium-tier upgrade, measured it, and shipped the negative result: it moved zero rows at ~1.97× the cost, so the shipped path stays single-model. → sanlee.me/projects/the-system