viditparashar.me/faqFAQ

What should I put in the first email?

What you are building, what stage it is at, and what you would want me doing in the first month. If it is a role, the team size and who I would work with matters more to me than the title.

You do not need a formal spec. I will tell you honestly if it is not a fit rather than take a call to be polite about it.

Related results

  1. viditparashar.meviditparashar.me › hire

    Hire Vidit Parashar — open to interesting problems

    ContactIST (UTC+5:30)

    Currently open to interesting problems. Email viditsharma818@gmail.com — replies usually land within one working day, IST (UTC+5:30). Overlaps a full working day with…

  2. viditparashar.meviditparashar.me › projects › resup

    Resup.dev — a résumé builder aimed at the software that reads it first

    Case studyLive2026

    31 Mar 2026 — … the software that reads it first. Most résumés are rejected by software before a person sees them. Applicant tracking systems parse a document, and a layout that looks…

    • 2input formats accepted
    • parse → structure → optimise → exportpipeline stages
    • unknownmeasured effect on interview rate
    • Next.js
    • TypeScript
    • Python
    • Tailwind CSS
    • NLP
    • LLMs
  3. viditparashar.meviditparashar.me › projects › voxa

    Voxa — dictation that learns your words, and an assistant that can see…

    Case studyLive2026

    30 Jun 2026 — … trusting it. The confirmation step exists for a related reason: the honest answer to “what if the intent classifier is wrong about sending this email” is not a better…

    • 95%+wake-word accuracy
    • 2personalisation surfaces
    • 0irreversible actions without confirmation
    • ElectronJS
    • Node.js
    • TypeScript
    • Microsoft Azure
    • Azure Functions
    • LLMs
    • +2 more

Search this site for “What should I put in the first email?”

Vidit Parashar

Full-stack and AI engineer

I build AI features for domains where a confident wrong answer costs something — mostly clinical software and voice agents.

Gurugram, India · IST (UTC+5:30) · viditsharma818@gmail.com · @viditparashar96 · in/vidit-parashar-056707225 · viditparashar.framer.website

Summary

I have spent the last two years putting large language models into production rather than into demos. Most of that has been healthcare — an ambient scribe that turns a consultation into an EHR-ready note, and a set of clinical agents deployed into university health systems — where the interesting problem is never the model, it is what the system does when it is unsure.

Experience

Selected projects

Technologies

AI and LLM systems
LLMs, LangChain, LLM orchestration, NLP pipelines, Model fine-tuning, Speech to text, Full-duplex voice, Agent orchestration, Workflow automation, Screen understanding
Languages
TypeScript, JavaScript, Python, SQL, HTML, CSS, Java
Frontend
React, Next.js, Tailwind CSS, Redux, Redux Toolkit, Zustand, ShadCN, Material UI, NextUI, Styled Components, Bootstrap, GSAP, ApexCharts, Recharts, PWA
Backend and APIs
Node.js, Microservices, Socket.io, Azure Functions, Prisma, Mongoose
Databases
PostgreSQL, MongoDB, NoSQL
Infrastructure and tooling
Microsoft Azure, AWS, Docker, CI/CD, Git, Vercel, Firebase, Appwrite, Vite, Webpack
Mobile and desktop
Swift, SwiftUI, iOS (native), ElectronJS, React Native, Ionic

Education

Availability

open to interesting problems.