About
I…
Activity
5K followers
-
Nitin Bhat shared thisGreat experience attending Code w/ Claude. The sessions were practical, sharp, and energizing, especially the fireside chat with Dario Amodei, Boris Cherny, and Guillermo Rauch. It was exciting to see how quickly AI-native development workflows are evolving and what that means for how we build software next. Left with a lot of ideas and inspiration. #AI #Claude #DeveloperTools #SoftwareEngineering
-
Nitin Bhat shared thisI will be at Code w/ claude developer conference tomorrow in San Francisco. Feel free to reach out if you are attending let's catch up!
-
Nitin Bhat shared thisHeading to the a16z Speedrun Cafe tomorrow. Excited to meet founders and builders in AI. Being in the space myself, I love seeing what people are shipping. If you'll be there, let's connect.
-
Nitin Bhat shared thisKnowledge graphs are having a moment. Not because they're new. Because they're the missing layer for self-improving agents. Static context → evolving context. Prompt engineering → graph engineering. Been going deep on this for a few weeks. If you're building in this space or have favorite resources / products, send them my way. Will share what I learn.
-
Nitin Bhat reposted thisNitin Bhat reposted this🚀 Shape the Future of Connected Health with AI! We’re building something bold at Health100—an AI‑native health technology platform that brings together pharmacies, providers, insurers, PBMs, and digital health into one seamless, consumer‑first ecosystem. Powered by Google Cloud AI, our mission is to reinvent how personalized health experiences are delivered at scale. Come join Tony Ambrozie, Deepu Kumar, Gaurav Sachdeva, Sridharan P.'s team! We’re looking for a Principal Software Engineer who’s ready to set technical direction, influence platform strategy, and build cloud‑native, event‑driven systems that truly matter. 💡 Why this role is exciting Architect and lead enterprise‑grade, distributed platforms from prototype to production Drive innovation across cloud, microservices, Kafka/event‑driven systems, and AI/GANative solutions Partner with product, architecture, and engineering leaders to shape roadmaps and core frameworks Stay hands‑on where it counts—mentoring senior engineers and raising the bar for quality, reliability, and performance Work on technology that directly impacts how people experience health and care 📍 Location: Prefer hybrid in Woonsocket, RI (remote considered for exceptional talent) If you’re passionate about cloud architecture, AI‑powered platforms, and building systems with real‑world impact, this is your opportunity to lead at scale and leave your mark. 👉 Ready to build the future of connected health? Apply now or reach out to learn more. https://lnkd.in/gXJpzdNZ #Hiring #PrincipalEngineer #CloudEngineering #AIInHealthcare #HealthTech #SoftwareEngineering #GoogleCloud #EventDrivenArchitecturePrincipal Software Engineer (Health100 Platform) in One CVS Drive, Woonsocket, Rhode Island,United States | Innovation and Technology at CVS HealthPrincipal Software Engineer (Health100 Platform) in One CVS Drive, Woonsocket, Rhode Island,United States | Innovation and Technology at CVS Health
-
Nitin Bhat reposted thisHow did this secret get out? Swastik Saxena thanks for editing this, loved the conversation. P.S. Not really a crazy secret I'm worried about getting leaked, that was just for the clickbait!Nitin Bhat reposted thisSometimes the best user research hack isn’t surveys… it’s just buying people’s time. Rishit Chaturvedi figured this out early while building Mazle AI instead of chasing users for feedback, he simply booked time with them on topmate.io No cold DMs. No begging for replies. Just high-intent conversations with people who actually show up. Simple, slightly counterintuitive… but ridiculously effective. Full Episode, coming out soon!
-
Nitin Bhat reposted thisNitin Bhat reposted thisWe launched the SigmaMind AI MCP server on Product Hunt today. Building a voice agent typically means stitching together a telephony layer, speech-to-text, an LLM, text-to-speech, and tool calling -- and then managing all of it through a separate dashboard. The MCP server removes that context switching. You can spin up an agent, assign a phone number, define the workflow, and trigger calls directly from inside Claude. We built it on top of the same infrastructure that's already handling 5M+ calls and powering 2,500+ voice agents in production -- so it's not a demo layer. It's full access to the platform. If you're building with voice AI and want a faster way to iterate, it's worth trying. An upvote on Product Hunt today would mean a lot to us. Link in comments -
-
Nitin Bhat shared thisA new grad told me today they followed 20 roadmaps. Still can't land a job. I wasn't surprised. Roadmaps are the most overrated content on LinkedIn. Every guru has one. "How to crack system design." "How to become an AI engineer in 2026." Step 1, step 2, and step 47. None of them work. Here's why: - Engineering is not a checklist. It's exploration. - You don't become a good engineer by following someone else's path step by step. - You become one by getting curious, trying things, breaking things, and learning why they broke. What's helped me most in my career: * Breadth-first search followed by depth-first search. * Explore widely. Find what clicks. Then go deep. Kubernetes? I didn't follow a roadmap. I got curious about why pods kept dying in production, went down the rabbit hole, and came out with a CKA score of 97. Building AI agents and backend systems? Same thing. Curiosity led to building. Building led to breaking. Breaking led to understanding. The engineer following 20 roadmaps knows a little about everything and deeply understands nothing. That's the trap. Roadmaps give you the illusion of progress without the depth that actually lands a job. Stop following roadmaps. Start following rabbit holes. What actually made you a better engineer—a structured roadmap or unplanned curiosity?
-
Nitin Bhat shared thisOpenAI just launched a $100/month Codex tier. Anthropic has been fumbling for weeks. The timing isn't a coincidence. Here's what OpenAI saw: Claude Code has been unreliable. Outages, throttled limits, long-running tasks that refuse to finish. The power users Anthropic built its reputation on have been quietly frustrated for a month. Meanwhile, Codex usage exploded. 3 million weekly users. 1 million added in 30 days. The $20 Plus plan couldn't handle power user demand. The $200 Pro plan was too steep for most to commit to without trying first. So OpenAI did the obvious thing: they built the bridge. $100/month sits exactly in the gap between "curious about Codex" and "all-in on Codex." It's the tier designed to pull power users off Claude without asking them to commit $200 on day one. This is textbook market capture. Anthropic stumbled, and OpenAI didn't wait for them to recover. They priced a product specifically to poach the users most likely to leave. The lesson isn't about which AI is better. It's that AI coding tool loyalty is the thinnest it's ever been in tech. One bad month of reliability can flip an entire market. Anthropic has 30 days to fix Claude Code before this tier becomes the default for serious engineers. Is OpenAI about to win the AI coding war, or is Anthropic going to recover in time?
-
Nitin Bhat reacted on thisNitin Bhat reacted on thisI work on healthcare AI. I also navigate the healthcare system as a caregiver. Those two experiences don't always match — and that gap is the most important design input I have. The moments where the system fails a caregiver aren't usually dramatic. They're small. A piece of information not surfaced at the right moment. A workflow that assumes the clinician has context they don't have. A decision support tool that gives an answer without giving the reasoning behind it. Each small failure costs something. Time. Confidence. Sometimes safety. What I've learned building healthcare AI from both sides of that experience — the problem is almost never the model. It's whether the people building it understand what it feels like to need it. That understanding doesn't come from data. It comes from proximity to the human experience the system is supposed to serve. The most important input to healthcare AI isn't in the training data. It's understanding what it feels like to need the system when something important is at stake.
-
Nitin Bhat reacted on thisNitin Bhat reacted on thisThis week, I have seen a lot of founders receiving YC rejection emails. And whenever I speak with founders after a rejection, the first thing they usually assume is: we probably didn't have enough traction. Having helped review a few YC applications over the years, and also going through the process ourselves, I actually think traction is one of the most misunderstood parts of the application. We made this mistake too. In hindsight, we probably applied later than we should have because we kept waiting for more traction before applying. Traction definitely matters, but mostly because it shows that a team can execute. What matters much more is the team itself and whether you have unique insight into the market you are building for. One mistake I see repeatedly is market sizing. Founders often say things like, "this is a $300B opportunity." Reality is, almost nobody builds for the whole world on day one. Pick one market and stick to it because realistically, you are probably committing the next few years of your life to understanding that market anyway. Maybe it is the US. Maybe India. Showing deep understanding of one market is much more convincing than throwing around huge numbers without showing clarity about who you are building for. Another thing I see often is founders trying too hard to sound sophisticated. Applications become full of jargon, acronyms, technical language, and complicated explanations. My usual advice is simple. Explain your startup exactly how you would explain it to a friend you met at a bar who knows nothing about your industry. The simpler you explain it, the easier it becomes for someone reading your application to understand why it matters. I also think founders underestimate how important talking to users is. Market sizing can be wrong. Markets themselves can change. Sometimes categories don't even exist when founders start building. What creates conviction is when founders clearly understand users better than everyone else. And finally, for everyone who got rejected this week, I genuinely want to say this: do not over-interpret a rejection email. A rejection is not a permanent verdict on either your company or your abilities. Simplify the story, get closer to users, sharpen your understanding of the market, continue building, and apply again if you still believe in what you are doing. Whether YC happens or not, long-term outcomes are usually decided by what founders do after rejection, not by the rejection itself.
-
Nitin Bhat liked thisNitin Bhat liked thisHosting just got a whole lot easier just in time for this summer’s global soccer tournament! 🛒⚽️ We are thrilled to officially introduce Shipt Kits—our newest, frictionless feature designed to completely redefine how consumers prep for major hosting moments. Whether prepping for a high-stakes watch party or a summer cookout, consumers often face the fatigue of bouncing between screens to build the perfect basket. Shipt Kits simplifies the entire experience, transforming occasion-worthy grocery lists into curated bundles that can be added to a cart with just one click and delivered same-day. We’ve teamed up with the phenomenal Eva Longoria to show fans how to effortlessly host like a pro. From "Fan Food" to the ultimate "Game-Day Grill Out," we're making sure you don't miss a single whistle. Read more on Shipt’s newsroom on how to simplify your game day watch party! https://lnkd.in/gmXj6g3m
-
Nitin Bhat liked thisNitin Bhat liked thisPaying taxes should mean better roads, better healthcare access, and better governance — not being stuck for hours because a VIP convoy needs a clear road. No citizen should suffer, especially during a medical emergency, because “important people” are passing by. A system that delays emergency care for protocol needs serious reflection. Respect is earned through public service, not through blocking the public. India needs smarter traffic management where ambulances, emergency cases, and citizens come first — regardless of who is on the road. What are your thoughts on VIP movement affecting common people? Narendra Modi please sir look into this #Bengaluru #VIPCulture #India #Traffic #Governance #PublicSafety #EmergencyCare #TaxPayers #CivicSense #RoadSafety #LinkedInIndia #SocialAwareness #Narendramodi
-
Nitin Bhat reacted on thisNitin Bhat reacted on thisHe quit his stable job recruiting 40,000 workers monthly with no plan, just the itch to build something of his own. Interviewed Rishit Chaturvedi, founder of Mazle AI Worked at Vahan recruiting delivery workers at 40,000 people per month. Quit because he wanted to build something of his own. No plan, just boredom and conviction. Started researching legal tech. LinkedIn search for "ex-Anand and Anand" returned people named Anand Kumar and Anand Prakash. Completely useless. Kept digging. Realized the real problem: every interview round asked the same redundant questions. From GPM to CPO, identical questions every time. What are they actually getting from interviews? That became Mazle AI. Doesn't automate sourcing or screening. Solves the interview layer everyone ignores. Bot joins calls, gets instant evidence-backed feedback in one minute. Not 48 to 72 hours later. Five customers currently. Users say once they try it, they never go back to manual feedback. Advice: Everyone will say your idea is terrible. Listen to everyone, then do what you want anyway. What's broken in your hiring process that everyone accepts as normal? Vakada Rohit
-
Nitin Bhat liked thisNitin Bhat liked thisWhat companies are the best to work for in San Francisco right now? We dug into the local data to find the answer, uncovering the top 10 workplaces for long-term career growth in the San Francisco Bay Area. From Salesforce to Google, this list highlights the companies investing in their employees locally. It’s also a resource to identify open jobs, build your network and pinpoint the sectors fueling growth across the city. See who made the cut and join the conversation below: What trends are defining the work landscape in the Bay Area right now — and how can professionals capitalize on them? #LinkedInTopCompaniesLinkedIn Top Companies 2026: The 10 best employers to grow your career in San FranciscoLinkedIn Top Companies 2026: The 10 best employers to grow your career in San Francisco
Experience & Education
-
CVS Health
View Nitin’s full experience
See their title, tenure and more.
or
Licenses & Certifications
Volunteer Experience
-
Musician
NU Sanskriti
- Present 3 years 11 months
Arts and Culture
performed in multiple events in front of a huge audience as a singer/guitarist.
-
Web Developement Lead
Google Developer Student Clubs - JSSSTU
- 1 year 4 months
Science and Technology
organising workshops and maintaining web apps for the club.
-
-
Courses
-
Algorithms
CS-5800
-
Database Management Systems
CS-5200
-
Intro to data management
DS-5110
-
Program Design Paradigm
CS-5010
Projects
-
Stock Trading Platform
-
- Built a Stock Trading platform to manage user portfolios in Java, the application allows buying stocks, selling stocks, investing using a dollar-cost averaging strategy, and rebalancing a portfolio.
- We implemented multiple design patterns while working on the project, such as adapter, builder, facade, and command design patterns.
- Extensively tested the application using Junit and Abstracted code into appropriate interfaces and classes using SOLID design principlesOther creators -
-
PrepZone
-
See project- I implemented a coding platform IDE from scratch with features like remote code execution on the backend server and support for more than 5 programming languages.
- Containerized the application using docker and deployed it on the Heroku cloud.
- Built the application using MERN (Mongo Express React Node) stack and used Redux for state management.
Test Scores
-
Toefl
Score: 103
R 25 L 30 S 25 W 23
-
GRE
Score: 317
166 Q 151 V 3.5 AWA
Languages
-
English
Native or bilingual proficiency
-
Hindi
Limited working proficiency
-
Kashmiri
Limited working proficiency
Recommendations received
5 people have recommended Nitin
Join now to viewOther similar profiles
Explore more posts
-
Satyam Parmar
Here’s how I cracked the Senior Software Engineer (L5A) round. Last week, I received an L5A Senior Software Engineer offer from Uber — and I want to share my interview experience so it helps anyone targeting similar roles. I didn’t prepare for an Uber interview… I prepared for the level of engineer Uber expects. This wasn’t luck. It was clarity, consistency, and preparation aligned to how top-tier companies actually evaluate engineers. Here’s the complete breakdown 👇 --- 🧪 1. Coding Business Phone Screen (60 mins — Elimination Round) One single question. Medium-hard → Hard. No fancy tricks. No rare patterns. Just pure logical reasoning and clean code under pressure. The problem involved geometry + spatial logic. They cared more about: How I structured the problem Whether my code was clean & testable My ability to think out loud Lesson: The first round filters mindset, not memorization. --- 💻 2. Algorithms & Data Structures (Coding Round 1) Two LeetCode-style problems: ✔ One Medium (Trees) ✔ One Hard (Graphs + Topological Sorting) This round tested: Data structure fundamentals Depth of reasoning Edge cases Ability to optimize Tip: Practice graph problems deeply. Uber LOVES graph reasoning. --- ⚙️ 3. Depth in Specialization — Machine Coding Round (Coding Round 2) This wasn’t a typical coding round. They expected production-quality engineering: Correctness SOLID & OOP Concurrency handling Clean abstractions Readability Extendable design The task: Build a small real-world service end-to-end. This round clearly differentiates senior engineers from mid-levels. --- 🏗️ 4. System Design & Architecture Interview The most important round. I had to design a full system from scratch: Requirement clarification High-level architecture API design Storage choices Scalability plan Bottleneck analysis Trade-offs & reasoning They were looking for: Clarity of thought Real production experience Ability to foresee failures Decision-making under constraints --- 🤝 5. Collaboration & Leadership Round (60 mins) This one surprises many people. It was: 25% technical 75% behavioral They evaluated: Ownership Crisis handling Stakeholder management Mentoring & leadership Communication clarity Impact measurement Senior roles are not just about code — they are about influence, alignment, and decision-making. --- #Uber #InterviewExperience #SeniorSoftwareEngineer #SystemDesign #MachineCoding #DSA #BackendEngineering #TechCareers #CareerGrowth #SoftwareEngineering #LeadershipInTech #CodingInterview #TechJobs #InterviewPrep
2 Comments -
Shivam Gupta
Excited to be speaking at Rootconf this Saturday! I'll be sharing practical lessons from operating Aerospike at multi-million QPS scale in InMobi's real-time advertising systems—covering scaling challenges, data-model tradeoffs, migration surprises, and production reliability patterns. If you're interested in databases, distributed systems, or operating low-latency infrastructure at scale, I'd love to see you there. Event link: https://lnkd.in/gBjBqbYR Hasgeek Zainab Sandeep Talina Ranganadh #rootconf #databases #inmobi
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content