If it's serious, I'll respond.
Speaking, podcasts, collaboration on AI infrastructure or developer tooling, serious work. I read everything and reply to the things worth replying to. Best path is to tell me clearly what you're working on and what you need.
Open to full-time roles — globally remote, or relocation with visa sponsorship (EU/Gulf).
LinkedIn DM
For everything: speaking invitations, podcast bookings, collaboration, intros. Direct messages here get read within 24 hours.
linkedin.com/in/jitangupta Best for detailFor anything with context, attachments, or that needs a longer answer. Use the form below if you'd rather not open your mail client.
hi@jitangupta.com Best for codeGitHub
Issues, PRs, discussions on any of the open-source projects. If your question is about a specific build, the repo is the right place.
github.com/jitangupta Best for "I saw your video"YouTube
Comments on episodes. Public Q&A. If your question is about something I covered, this is where to ask it.
@jitanguptaWorth your message.
- Speaking invites at serious AI-builder events, technical workshops, and conferences with a practitioner audience.
- Podcast bookings on AI tooling, MCP, agent architectures, or AI-assisted dev workflows.
- Collaboration with founders and senior engineers shipping serious AI infrastructure or developer tooling.
- Specific technical asks from teams already in the work — not "could you explain MCP".
- Hello from a builder shipping something interesting. Always welcome.
Not the right inbox.
- Cold sales pitches, lead-gen, SEO link exchanges, agency outreach.
- "Quick call to pick your brain" — try a specific question instead.
- Generic "we're looking for a content creator" partnerships.
- Beginner Claude Code support — the channel and the GitHub repos answer most of it.
- Anything that could be solved by reading a README.
Send a message.
Be specific. Tell me what you're working on and what you'd like from me. Replies usually come within a few days.