About
Hi, I'm Abhishek.
I'm an engineering leader in the San Francisco Bay Area. For about fifteen years I've built the systems that sit between a company and its customers: CRM platforms, data pipelines, routing, billing, and lately the LLM tooling on top of all of it.
Today I'm a Staff Software Engineer and Technical Lead Manager at Uber on the Data Platform & CRM team. I manage 21 engineers, seven in the U.S. and fourteen in India, and I own the technical direction for the sales-automation platforms and the data pipelines behind them: ingestion, change data capture, and deduplication on Kafka, Spark, and Hudi, plus the workflow tooling the team runs them with. Performance reviews, expectations, hiring, and the roadmap are mine too.
Before Uber I was in Okta's Business Technology group, where I architected MCP servers that connect LLM agents to enterprise systems and built GenAI tools, including a customer-support chatbot. Before that I spent five years at LinkedIn building the CRM and routing systems behind its global sales organization, managing a six-person team, and integrating a GPT-based model into the enterprise tools used by more than 10,000 people. Earlier stops include Adobe and Pandora, and before those, years as a Salesforce developer and architect. That is where this domain's name comes from, and why the oldest posts here are about Apex and Visualforce.
How I work
- If it isn't written, it isn't decided. Design docs and short decision records, open to comments across time zones, before anything ships.
- Review designs, not pull requests. I want to be in the room when the schema is chosen, not the gate every change waits on.
- One bar, everywhere. The same hiring loop, the same review calibration, and the same ownership expectations in California and in India.
- Measure before and after. An LLM feature without an eval set is a demo. A migration without a baseline is a guess.
- Keep one small project of my own. It keeps my design feedback specific, and it keeps me honest about the tools the team is adopting.
Experience
- 2026 to present Uber · Staff Software Engineer, Technical Lead Manager, Data Platform & CRM
Manage 21 engineers across the U.S. and India. Own technical direction for the sales-automation platforms and the data pipelines behind them.
- 2025 to 2026 Okta · Staff Software Engineer, Business Technology
Architected MCP servers connecting LLM agents to enterprise systems. Built GenAI tools including a customer-support chatbot.
- 2020 to 2025 LinkedIn · Staff Software Engineer, Sales Systems
Managed a six-person team building CRM and routing systems for the global sales organization. Integrated a GPT-based model into enterprise tools used by 10,000+ people.
- 2017 Adobe · Software Engineer (contract)
- Pandora · Software Engineer, Payments and subscriptions
Built payment and subscription systems for listener products.
- Before 2017 Earlier · Salesforce developer and architect
SSO, partner and customer communities, integrations, and platform architecture for Salesforce customers. Eleven Salesforce certifications, including System Architect.
Certifications
Eleven Salesforce certifications, earned during the architecture years and kept current where it still matters.
- Salesforce Certified System Architect
- Identity and Access Management Architect
- Integration Architect
- Development Lifecycle and Deployment Architect
- Platform Developer II
- Platform Developer I
- Platform App Builder
- Administrator
- Sales Cloud Consultant
- Community Cloud Consultant
- Force.com Developer
Elsewhere
LinkedIn is where my work history lives in full. The fastest way to reach me is email.