David Karam
United States
2K followers
500+ connections
View mutual connections with David
David can introduce you to 10+ people at Microsoft
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
View mutual connections with David
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
About
Helping AI companies build amazing experiences by deploying the best of Research…
Activity
2K followers
-
David Karam shared thisWanted to share some wonderful news; Pi Labs, Inc. team is joining Microsoft after a wild year and a half on the startup rollercoaster. It's been an absolute joy working with the awesome “Pi Boys” (yes, a real nickname that Zachary's 10 year old son chose for us!) day and night for 18 straight months; grueling, but rewarding in its own way! And it feels like the journey just got started as we now go on to tackle even bigger challenges together at Microsoft. Huge thanks to all the amazing folks at Microsoft: Guha for being our relentless champion, Dee, Kevin, Walt, Jason and Perry for welcoming us with open arms. And the amazing M&A team for orchestrating such a smooth process & landing for us! Huge thanks to all our amazing advisors, angels, founder friends, and investors; Nafis our partner on the journey from day 1 as well as the entire Accel team. Eyal, Pi's close friend and advisor from its very first to its very last day. The strength of the founder & investor community was something that blew our mind every day for the very short time we were part of it. Thanks for teaching us much needed lessons in community, grit and radical optimism. Huge amounts of love and gratitude to Achint, my corporate soulmate (the person I want to work with forever :). I don’t know what I did to deserve this gift, but life saw it fit to cross our paths together many years back, and it’s been nothing but magical ever since! 🙏🙏❤️❤️ Dhruv, John, Nam, Prashant, Sidd, Suneel, ZacharyDavid Karam shared thisWelcoming Pi Labs to Microsoft Some of the greatest joys of my career have come from working with a small group of collaborators who share a passion for building something that gets used by billions of people, including friends and family, who benefit from that effort day in and day out. Each generational technology shift offers a fresh chance to be part of one of these projects, with every cycle giving us better tools and better ways to solve the enduring challenge of finding information and making it useful. To do it once in a career is a privilege. To do it twice with the same team is extraordinarily rare, so getting the chance to "get the band back together for another tour" is truly something special. With that, I'm thrilled to welcome old friends and collaborators Achint Srivastava, David Karam, and their team from Pi Labs to Microsoft. I have high hopes for what we'll achieve together, and I can't wait to share more soon! Walt Drummond Sam Schillace
-
David Karam shared thisTry it at withpi(dot)aiDavid Karam shared this𝗥𝘂𝗻𝗻𝗶𝗻𝗴 𝗘𝘃𝗮𝗹𝘀 𝘄𝗶𝘁𝗵 𝗣𝗶 𝗦𝘁𝘂𝗱𝗶𝗼 𝗜𝘀 𝗥𝗶𝗱𝗶𝗰𝘂𝗹𝗼𝘂𝘀𝗹𝘆 𝗦𝗶𝗺𝗽𝗹𝗲 ⚡ Once you have a Pi rubric, getting to insights takes seconds—not hours. Here's the entire workflow: 📤 Upload your data – Drop in the outputs you want to evaluate (a CSV, JSON, or paste directly) 📋 Choose your rubric – Select an existing Pi rubric or create a new one in moments ▶️ Run the eval – Click run and get results immediately That's it. No complex setup. No infrastructure to configure. No eval framework to learn. 🎯 The studio handles everything so teams can focus on what matters: understanding quality and iterating fast. Whether you're testing a new prompt, comparing model versions, or validating before deployment—Pi Studio makes evaluation feel effortless. withpi(dot)ai
-
David Karam shared thisIf you’re still “debugging” your AI system, you might be missing the point. The real work is learning how to shape distributions—and this post explains why that shift changes everything.David Karam shared this𝗧𝗵𝗲 𝗔𝗜 𝗕𝘂𝗶𝗹𝗱𝗲𝗿’𝘀 𝗠𝗶𝗻𝗱𝘀𝗲𝘁 𝗦𝗵𝗶𝗳𝘁: 𝗙𝗿𝗼𝗺 𝗗𝗲𝗯𝘂𝗴𝗴𝗶𝗻𝗴 𝘁𝗼 𝗦𝗵𝗮𝗽𝗶𝗻𝗴 𝗗𝗶𝘀𝘁𝗿𝗶𝗯𝘂𝘁𝗶𝗼𝗻𝘀 Traditional software can be debugged. AI systems can’t—because they’re not broken. They’re stochastic. And that means the right mindset for builders isn’t debugging. It’s shaping distributions. ⚙️ 𝗗𝗲𝘁𝗲𝗿𝗺𝗶𝗻𝗶𝘀𝘁𝗶𝗰 𝗦𝘆𝘀𝘁𝗲𝗺𝘀 In traditional code: • Input → Known Output • Errors = something is “wrong” • Debugging = find and fix until the system behaves correctly • Tests = binary pass/fail The entire culture of software engineering was built around this deterministic logic. 🎲 𝗦𝘁𝗼𝗰𝗵𝗮𝘀𝘁𝗶𝗰 𝗦𝘆𝘀𝘁𝗲𝗺𝘀 AI systems flip that script. • Input → Distribution of Possible Outputs • Errors ≠ bugs. They’re inevitable outcomes of probability. • The question isn’t “is this right or wrong?” but: “What does the range of outcomes look like, and how often do we see them?” Imagine your AI assistant succeeds 86% of the time on sampled queries. That doesn’t mean it’s broken. That’s its profile of behavior. Your job isn’t to eliminate variance (you can’t). It’s to shape it—so that the system is predictably good within acceptable bounds. 🔍 𝗧𝗵𝗲 𝗕𝘂𝗶𝗹𝗱𝗲𝗿’𝘀 𝗡𝗲𝘄 𝗝𝗼𝗯 This is where AI development starts to look more like data science than traditional engineering: • 𝗗𝗲𝗳𝗶𝗻𝗲 𝗚𝗼𝗼𝗱𝗻𝗲𝘀𝘀 → Is “good” an accurate fact? A persuasive summary? A consistent tone? You need clarity before you can measure. • 𝗠𝗲𝗮𝘀𝘂𝗿𝗲 𝗗𝗶𝘀𝘁𝗿𝗶𝗯𝘂𝘁𝗶𝗼𝗻𝘀 → Instead of one test case, you need curves: precision/recall, success rates, error surfaces. What percentage of inputs fail? Which clusters of queries underperform? • 𝗦𝗮𝗺𝗽𝗹𝗲 𝘁𝗵𝗲 𝗦𝗽𝗮𝗰𝗲 → Infinite queries can’t be tested. But you can cluster, stratify, or generate representative slices to understand behavior. • 𝗜𝘁𝗲𝗿𝗮𝘁𝗲 𝗼𝗻 𝗦𝗵𝗮𝗽𝗲, 𝗡𝗼𝘁 𝗔𝗯𝘀𝗼𝗹𝘂𝘁𝗲𝘀 → The win condition isn’t perfection. It’s predictability. You’re nudging a distribution toward usefulness. 🔄 𝗗𝗲𝗯𝘂𝗴𝗴𝗶𝗻𝗴 𝘃𝘀 𝗦𝗵𝗮𝗽𝗶𝗻𝗴 Think of the contrast like this: • 𝗗𝗲𝗯𝘂𝗴𝗴𝗶𝗻𝗴 → Fix the bug, rerun the test, green check mark ✅. • 𝗦𝗵𝗮𝗽𝗶𝗻𝗴 𝗱𝗶𝘀𝘁𝗿𝗶𝗯𝘂𝘁𝗶𝗼𝗻𝘀 → Understand the landscape of outcomes, identify where the system is strong, weak, or unpredictable, and adjust levers (data, retrieval, prompts, architecture) to reshape the curve. One is about chasing certainty. The other is about designing resilience. AI systems are not deterministic machines to be debugged. They’re probabilistic systems to be shaped. The sooner we internalize this shift, the faster we’ll build AI products that users actually trust. 💡 How do you evaluate and shape your system’s distribution today—through metrics, sampling, or live user feedback loops? Link to image
-
David Karam shared this⚡ Metrics that reflect real user preferences, not theoretical ideals. Anyone who's tried to label AI outputs as "good" or "bad" knows how fuzzy those boundaries are. But asking "which is better?" That's actually answerable. The challenge has been turning all those A/B comparisons into something actionable. Excited that Pi Studio solves this by crunching the preference data and extracting what "better" actually means for specific applications. withpi(dot)aiDavid Karam shared this𝗧𝘂𝗿𝗻 𝗣𝗿𝗲𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗗𝗮𝘁𝗮 𝗜𝗻𝘁𝗼 𝗔𝗰𝘁𝗶𝗼𝗻𝗮𝗯𝗹𝗲 𝗠𝗲𝘁𝗿𝗶𝗰𝘀 𝘄𝗶𝘁𝗵 𝗣𝗶 𝗦𝘁𝘂𝗱𝗶𝗼 Here's a truth about AI quality: sometimes it's impossible to say if a response is "good" or "bad" in absolute terms. But it's easy to say "A is better than B." Teams collect tons of A/B comparisons, but struggle to turn those relative judgments into concrete eval metrics. The insights are trapped in the data. 📊 𝗣𝗶 𝗦𝘁𝘂𝗱𝗶𝗼 𝗮𝗰𝘁𝘀 𝗮𝘀 𝘆𝗼𝘂𝗿 𝗱𝗮𝘁𝗮 𝘀𝗰𝗶𝗲𝗻𝘁𝗶𝘀𝘁. It analyzes preference pairs and feedback signals to: ⚡ Extract what "better" actually means for your application 🎯 Calibrate rubric criteria based on real user choices 📈 Evolve metrics as you gather more comparisons The result? Eval metrics that align with how users actually experience quality—not just how you think they should. No need to force binary "good/bad" labels when the world works in shades of "better than." Pi Studio meets you where your data already is. 👍👎
-
David Karam shared thisSo many teams know they need evals but get stuck at "what should we even measure?" The blank rubric is real—and it's why eval strategies get pushed to "later." Pi Studio lets teams start with what they already have (PRD, system prompt, or just a description) and get to a working rubric in moments. ⚡ No more analysis paralysis. Just a clear starting point to build from. Check it out: withpi(dot)aiDavid Karam shared this𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝗶𝗻𝗴 𝗣𝗶 𝗦𝘁𝘂𝗱𝗶𝗼: 𝗙𝗿𝗼𝗺 𝗣𝗥𝗗 𝘁𝗼 𝗘𝘃𝗮𝗹 𝗥𝘂𝗯𝗿𝗶𝗰 𝗶𝗻 𝗠𝗼𝗺𝗲𝗻𝘁𝘀 ⚡ Many of our customers are early in their AI quality journey and don't know how to start with evals. 𝗧𝗵𝗲 𝗯𝗹𝗮𝗻𝗸 𝗿𝘂𝗯𝗿𝗶𝗰 𝗽𝗿𝗼𝗯𝗹𝗲𝗺 You know you need to measure quality, but staring at an empty eval template wondering "what even IS good for my app?" is paralyzing. So evals get delayed or built on gut feel instead of real criteria. 𝗣𝗶 𝗦𝘁𝘂𝗱𝗶𝗼 𝘀𝗼𝗹𝘃𝗲𝘀 𝘁𝗵𝗶𝘀. 🚀 Drop in something you already have: 📋 A product requirements doc 💬 Your system prompt ✍️ A simple description of what you're building Pi Studio analyzes it and generates a working eval rubric immediately. Not generic metrics—your metrics, tailored to what you're actually trying to achieve. From there, run your first eval in seconds. No PhD in ML required. No weeks of rubric design. Just a clear starting point you can refine as you learn. 🎯 Stop letting "where do I start?" block your eval strategy. Withpi(dot)ai
-
David Karam shared thisSo much of what makes AI products brittle comes from using deterministic playbooks on stochastic systems. This post captures that shift perfectly — it’s not about debugging errors, it’s about shaping distributions. Until builders internalize that, our products will keep shining in demos and breaking in the wild.David Karam shared this𝗪𝗵𝘆 𝗗𝗼 𝗦𝗼 𝗠𝗮𝗻𝘆 𝗔𝗜 𝗣𝗿𝗼𝗱𝘂𝗰𝘁𝘀 𝗙𝗲𝗲𝗹 𝗕𝗿𝗶𝘁𝘁𝗹𝗲? 𝗔 𝗣𝗹𝗮𝘆𝗯𝗼𝗼𝗸 𝗳𝗼𝗿 𝗕𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗔𝗜 ⚠️ So many AI products work great in polished demos… and collapse the moment they hit real users. Think about it: • That chatbot that crushed a staged “track my order” demo, but melted when someone asked “My package arrived wet—can I get a refund?” • The AI travel planner that impressed investors with a Paris itinerary, but in production suggested London in the morning and Rome by dinner. • Or the code assistant that handled simple boilerplate in a demo, but in real use inserted subtle bugs you didn’t catch until deployment. These aren’t isolated failures. They’re symptoms of 𝗮𝗽𝗽𝗹𝘆𝗶𝗻𝗴 𝗱𝗲𝘁𝗲𝗿𝗺𝗶𝗻𝗶𝘀𝘁𝗶𝗰 𝘁𝗵𝗶𝗻𝗸𝗶𝗻𝗴 𝘁𝗼 𝘀𝘁𝗼𝗰𝗵𝗮𝘀𝘁𝗶𝗰 𝘀𝘆𝘀𝘁𝗲𝗺𝘀. 𝗗𝗲𝘁𝗲𝗿𝗺𝗶𝗻𝗶𝘀𝘁𝗶𝗰 𝘃𝘀 𝗦𝘁𝗼𝗰𝗵𝗮𝘀𝘁𝗶𝗰 In traditional software, everything is 𝗱𝗲𝘁𝗲𝗿𝗺𝗶𝗻𝗶𝘀𝘁𝗶𝗰: • Same input → same output • Bugs can be traced and fixed • Unit tests stay green once they pass We’ve built 50 years of engineering practices on that foundation. But AI systems are 𝘀𝘁𝗼𝗰𝗵𝗮𝘀𝘁𝗶𝗰: • Ask ChatGPT the same question twice → you’ll often get two different answers • Search “best restaurants in NYC” → one day Yelp dominates, the next day Reddit • Build a pipeline with 5 steps at 90% reliability → you don’t get 90%, you get ~60% This isn’t failure. It’s how stochastic systems behave. 𝗧𝗵𝗲 𝗠𝗲𝗻𝘁𝗮𝗹 𝗦𝗵𝗶𝗳𝘁 ❌ Not debugging errors ✅ But shaping distributions 👉 𝗦𝗵𝗮𝗽𝗶𝗻𝗴 𝗱𝗶𝘀𝘁𝗿𝗶𝗯𝘂𝘁𝗶𝗼𝗻𝘀 𝗺𝗲𝗮𝗻𝘀: • Define what “good” looks like in your context (accuracy, tone, trust, coverage). • Measure how often the system lands inside those bounds (e.g. does a support bot answer FAQs correctly 85% of the time?). • Accept variance as the baseline, not the exception. Without this shift, you’ll keep shipping brittle systems that shine in demos but collapse in the wild.
-
David Karam shared thisFinally, an eval tool that speaks the language of AI builders. 🧪 We just launched Pi Studio and it's solving something teams struggle with on every AI project: translating vague, diffuse product requirements into concrete, measurable eval criteria. What's clever: it can extract quality definitions from existing artifacts ⚡ 📋 System prompts 💬 User feedback 🔄 A/B tests ...and evolve them over time. No more manual rubric tuning. Plus it integrates with tools teams already use (Braintrust, Arize, etc.) so it fits right into existing workflows. 🌐 Worth checking out for teams serious about AI quality ⬇️David Karam shared this🚀 𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝗶𝗻𝗴 𝗣𝗶 𝗦𝘁𝘂𝗱𝗶𝗼: 𝗬𝗼𝘂𝗿 𝗔𝗜 𝗗𝗮𝘁𝗮 𝗦𝗰𝗶𝗲𝗻𝘁𝗶𝘀𝘁 𝗳𝗼𝗿 𝗕𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗖𝘂𝘀𝘁𝗼𝗺 𝗔𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗘𝘃𝗮𝗹𝘀 Turn the messiness of "what good looks like" into metrics that actually matter. 😰 𝗧𝗵𝗲 𝗽𝗿𝗼𝗯𝗹𝗲𝗺: You've built an eval dashboard, but your metrics don't tell you anything useful. "Goodness" is scattered across PRDs, system prompts, Slack threads, annotated examples, and user feedback. 🧪 𝗣𝗶 𝗦𝘁𝘂𝗱𝗶𝗼 𝘀𝗼𝗹𝘃𝗲𝘀 𝘁𝗵𝗶𝘀 𝗯𝘆 𝗮𝗰𝘁𝗶𝗻𝗴 𝗮𝘀 𝘆𝗼𝘂𝗿 𝗱𝗮𝘁𝗮 𝘀𝗰𝗶𝗲𝗻𝘁𝗶𝘀𝘁. It learns what "good" means for your application by analyzing: • Your product requirements and system prompts 📋 • Team knowledge buried in documents and code 💡 • User feedback signals (thumbs up/down, A/B preferences) 👍👎 • Domain expertise from across your organization 🎯 𝗛𝗼𝘄 𝗶𝘁 𝘄𝗼𝗿𝗸𝘀: 𝟙. 𝘎𝘦𝘵 𝘴𝘵𝘢𝘳𝘵𝘦𝘥 𝘪𝘯 𝘮𝘰𝘮𝘦𝘯𝘵𝘴 ⚡ Drop in a description, PRD, or system prompt. Pi Studio generates a working eval rubric immediately. 𝟚. 𝘌𝘷𝘰𝘭𝘷𝘦 𝘤𝘰𝘯𝘵𝘪𝘯𝘶𝘰𝘶𝘴𝘭𝘺 🔄 As you gather more feedback and examples, Pi Studio's agent refines and calibrates your metrics to align with real user preferences. 𝟛. 𝘋𝘦𝘱𝘭𝘰𝘺 𝘦𝘷𝘦𝘳𝘺𝘸𝘩𝘦𝘳𝘦 🌐 Run evals in seconds through our studio or integrations with Arize AI , Braintrust , Promptfoo , and more. Use your rubric as the north star for agent and search optimization. Stop guessing what to measure. Start building evals that drive real improvements. ✨ Withpi(dot)ai
-
David Karam shared thisShout out to my old friends from Search & KG wanted to highlight this really fun role working with a really inspiring founder and close friend Dara Ladjevardian! If you're interested in linguistics, the theory of the mind, the intersection of knowledge representations & LLMs, and hard core engineering in a frontier space and high growth company, reach out to Dara or ping me and I'll put you in touch. Exciting times!David Karam shared thisWhat does it mean to have a mind? What is a mind composed of? How can we evaluate whether a mind is true to its owner? At Delphi, these are not abstract thought experiments - they’re engineering challenges. Our mission is to recreate the human mind in digital form: its reasoning, its memory, its language, its essence. To do this, we’re hiring for a role that sits at the intersection of: 1. Prompt Engineering (designing systems of thought and language for AI) 2. Computational Linguistics (understanding the structure and function of language) 3. Cognitive Science (theories of consciousness, reasoning, and memory) The ideal candidate is: • Inspired by thinkers like Minsky and Kurzweil • Obsessive about the nuances of words and meaning • Equally technical and philosophical • Deeply aware of why humans matter in an AI world If questions of mind, consciousness, and identity keep you up at night, and you want to work at the frontier where engineering meets humanity, we’d love to talk.
-
David Karam shared thisStarting to work with the BlueJay team, first eval platform I've seen that's dealing with both the harness and the quality. Not just "we'll run your test cases" but more so "we'll help you figure the right test cases and right metrics to judge them". Excited about this change in the evals space and can't wait to bring Pi Labs, Inc. technology and Bluejay (YC X25) automation to bear on voice agent evals!David Karam shared thisRohan Vasishth and I left Amazon and Microsoft to build Bluejay (YC X25) (7 days a week), and got backed by Y Combinator. The reason we started Bluejay was simple: We were sick and tired of manually call-testing our voice agent 50 times before every release. So, we built a product that can simulate 1 month of customer interaction in 5 minutes. Think about it: SaaS has robust, feature-rich E2E testing platforms, CI/CD, and regression testing. Why don’t AI voice agents have the same? For us, building Bluejay wasn’t a “let’s see if this works” idea. It was a no-brainer. Voice agents need automated, scalable testing. And we won’t stop at voice. Bluejay will be the quality assurance platform that guarantees stability for ANY AI agent. So, what the hell is Bluejay? It’s how to trust your AI voice agent. Stop vibe-testing. Quality is engineered. We're live at: getbluejay.ai Thanks Pete Koomen, Tom Blomfield, and Garry Tan for believing in us! #llm #ycombinator #ai #ml #tech #startup #launch #vc #uchicago #uiuc 🧿
-
David Karam liked thisDavid Karam liked thisIt’s time to share more about what we’ve been working on: Common Fabric is a social computing lab building a medium for software that revolves around people, not apps. The walled gardens of apps cost the most where our lives intersect with others’. We’re creating systems that mold around the contours of people’s real lives and relationships. And that requires a new trust model. We are inverting the physics of trust to unlock the potential energy of software. This is both urgently necessary and newly possible in the agentic era. Sign up for the waitlist: commonfabric.com Team Alex Komoroske, Bernhard Seefeld, Tony Espinoza, Daniel Shiplacoff, Ian Hickson, Dan Bornstein, Gideon Wald, Mike Salisbury, William Kelly, Robin McCollum, Ben Follington, Mary Allen Advisors include Tim O'Reilly, Simon Willison, Bruce Schneier, Elizabeth Churchill, Amelia Wattenberger, Ink & Switch
-
David Karam liked thisDavid Karam liked thisWe have FHL - Fix Hack Learn going on this week. In addition to playing with Claude Code and Code Apps, I also got time to delve into the materials that David Karam has been talking to the team about - core first principles of AI foundational concepts. Selfishly, I need to immerse myself in mental models that resonate and I realized these concepts of how a model learns, the various architectures, how you optimize (cost functions) and how it reasons over data representations have some very direct PM, Leadership and Life analogies. I loved this thought exercise. #aifoundations #learningarchitectures #costfunctions #representation #analogiesHow AI Foundations map to PM, Leadership and Life!!How AI Foundations map to PM, Leadership and Life!!Kavita K.
-
David Karam reacted on thisDavid Karam reacted on thisMany of you have already seen the news about Pi Labs joining Microsoft, but I wanted to take a moment to share what this journey has meant to me. The last 18 months have been intense, surprising, and deeply meaningful for all of us at Pi Labs. What started as a simple idea between David Karam and me grew into a journey of learning, building, selling, and stretching ourselves far beyond what we imagined. I’m deeply grateful to everyone who believed in us — our team, our advisors, our investors, and the founder community that lifted us up at every step. A heartfelt thanks to our champions at Microsoft. Guha has been a mentor to me for years, and the chance to work with him again means more than I can express. Thanks Walt for championing us, looking forward to reconnecting in this new chapter. And big thank you to Dee, Kevin, Jason and Perry for welcoming us with such open arms. Thanks Microsoft M&A team for guiding us through the acquisition with clarity and care. Big thanks to Nafis, I learnt so so much from you about life, business and startups. And the entire Accel team for being great partners from day one. Thank you to Eyal, who has been with us since the very beginning and all the way to the end — always there, thoughtful, supportive and willing to help us work through the hardest questions. And finally, David — building Pi with you was something truly special. You helped me believe in myself on days when I doubted everything. We pushed each other, and kept finding our way forward. I couldn’t have asked for a better partner or a better friend. I’m grateful we get to keep building together. To our amazing team — Dhruv, John, Nam, Prashant, Sidd, Suneel, and Zachary — thank you for giving this little company everything you had. Nothing about this outcome was guaranteed, and yet you showed up every single day with energy, humility, and a desire to build something excellent. Excited for what comes next at Microsoft. 🙏❤️
-
David Karam reacted on thisDavid Karam reacted on thisThrilled to announce Pi Labs, Inc. has been acquired by Microsoft ! This past year has been unreal- filled with countless v0s, challenging problems, and teamwork I’m deeply proud of. I’ve had the privilege of working with AI experts and lifelong mentors like David Karam and Achint Srivastava who have not only taught me lessons about software and teamwork, but also about joie de vivre (the joy of life). Smart decisions > hard work. Simplicity > complexity. We do some of our best work when incentives are aligned. At Pi labs, we developed products faster than I ever thought was possible, all while having a blast and forming lifelong memories. Very excited to carry over our momentum into Microsoft, where we can truly make an impact in the whole industry! A sincere thanks to all who have supported us along the way. Here’s to a bright future ahead!!
-
David Karam reacted on thisDavid Karam reacted on thisWelcoming Pi Labs to Microsoft Some of the greatest joys of my career have come from working with a small group of collaborators who share a passion for building something that gets used by billions of people, including friends and family, who benefit from that effort day in and day out. Each generational technology shift offers a fresh chance to be part of one of these projects, with every cycle giving us better tools and better ways to solve the enduring challenge of finding information and making it useful. To do it once in a career is a privilege. To do it twice with the same team is extraordinarily rare, so getting the chance to "get the band back together for another tour" is truly something special. With that, I'm thrilled to welcome old friends and collaborators Achint Srivastava, David Karam, and their team from Pi Labs to Microsoft. I have high hopes for what we'll achieve together, and I can't wait to share more soon! Walt Drummond Sam Schillace
Experience
Education
-
Eidgenössische Technische Hochschule Zürich
-
-
Conducted my Masters Thesis in the "Web of Things" project. Thesis investigated a computational framework in the context of the Web of Things.
-
-
-
-
-
-
Publications
-
A Computational Space for the Web of Things.
Proceedings of the 3rd International Workshop on the Web of Things (WoT 2012)
In this paper, we propose the concept of
a computational marketplace as a framework to enable the analysis and aggregation of real-time data. Here, multiple tiers of hyperlinked algorithms from different providers interact to refine data within computational graphs.Other authors
Languages
-
English
Native or bilingual proficiency
-
Arabic
Native or bilingual proficiency
-
German
Limited working proficiency
-
French
Limited working proficiency
View David’s full profile
-
See who you know in common
-
Get introduced
-
Contact David directly
Other similar profiles
Explore more posts
-
David Rajesh Sundardas
ISB Alumni • 5K followers
Connecting LLMs to Multiple Systems 🔗 The real strength of AI isn’t just in generating text - it’s in how well it can work with the systems and data you already have. That’s where the Model Context Protocol (MCP) comes in. MCP allows you to connect an LLM to multiple, diverse systems - ERP, MES, IoT platforms, or custom tools - without rebuilding your entire architecture. This means the LLM can combine data from different sources, add context, and deliver insights that are actually useful. Because MCP is modular, you can integrate new systems or update existing ones without disrupting the whole pipeline. It’s a flexible, scalable approach that makes experimentation and innovation much easier. This is how we move from isolated AI models to connected, context-aware systems. Have you seen LLMs used as an “integrator” for different systems? Which use cases do you find most promising? #AI #MCP #SystemIntegration #LanguageModels #FutureOfAI
27
-
Rhonda Coleman Albazie
PRIVILEGE HEALTH ™️ -… • 493 followers
RIaaP-aligned world model evolution in AI: Dec 26, 2025 article discusses “world models” that enable robots to understand and plan in physical settings, predicting that models designed for real-world understanding will be a key frontier beyond LLMs and digital agents. After LLMs and agents, the next AI frontier: video language models #RIaaP #worldmodels #ai #llm #videolanguagemodels https://lnkd.in/g62D9qug
1
-
Matthew Anderson
Microsoft • 2K followers
Today at #MSIgnite, we got a look at how #Windows is evolving in the age of #AI, and it's fascinating! This VentureBeat article is a great summary of our redesign of Windows for autonomous AI agents—creating a platform for innovation and intelligent automation. https://msft.it/6044tZK7a 🌐
-
Harald Leitenmueller
Microsoft Österreich Gmbh • 4K followers
𝐓𝐡𝐞 𝐅𝐮𝐭𝐮𝐫𝐞 𝐨𝐟 #𝐀𝐈 𝐇𝐚𝐫𝐝𝐰𝐚𝐫𝐞 𝐈𝐬 𝐕𝐞𝐫𝐭𝐢𝐜𝐚𝐥—𝐚𝐧𝐝 𝐒𝐨𝐯𝐞𝐫𝐞𝐢𝐠𝐧 We’ve long known that Moore’s Law is slowing, and the von Neumann bottleneck is choking AI scalability. Now, a new architecture breaks through both. The 𝐌𝟑𝐃-𝐋𝐈𝐌𝐄 𝐜𝐡𝐢𝐩, published in Nature Communications, integrates logic, compute-in-memory, and content-addressable memory in a monolithic 3D stack. It achieves one-shot learning with 𝟗𝟔% 𝐚𝐜𝐜𝐮𝐫𝐚𝐜𝐲—matching GPU performance—while consuming 𝟏𝟖× 𝐥𝐞𝐬𝐬 𝐞𝐧𝐞𝐫𝐠𝐲 and running 𝟐.𝟕× 𝐟𝐚𝐬𝐭𝐞𝐫. This isn’t incremental. It’s foundational. 𝐀𝐧𝐚𝐥𝐨𝐠 𝐑𝐑𝐀𝐌 enables neuromorphic efficiency. 𝐓𝐂𝐀𝐌 𝐚𝐫𝐫𝐚𝐲𝐬 perform real-time Hamming distance calculations. 𝐁𝐄𝐎𝐋-𝐜𝐨𝐦𝐩𝐚𝐭𝐢𝐛𝐥𝐞 𝐟𝐚𝐛𝐫𝐢𝐜𝐚𝐭𝐢𝐨𝐧 ensures manufacturability and sovereignty. + 𝐅𝐨𝐫 𝐄𝐮𝐫𝐨𝐩𝐞, this means we can build 𝐞𝐧𝐞𝐫𝐠𝐲-𝐞𝐟𝐟𝐢𝐜𝐢𝐞𝐧𝐭, 𝐬𝐨𝐯𝐞𝐫𝐞𝐢𝐠𝐧 𝐀𝐈 𝐢𝐧𝐟𝐫𝐚𝐬𝐭𝐫𝐮𝐜𝐭𝐮𝐫𝐞 without relying on legacy architectures. + 𝐅𝐨𝐫 𝐩𝐨𝐥𝐢𝐜𝐲𝐦𝐚𝐤𝐞𝐫𝐬, it’s a call to rethink digital strategy from the silicon up. 𝐖𝐞 𝐦𝐮𝐬𝐭 𝐬𝐭𝐨𝐩 𝐜𝐡𝐚𝐬𝐢𝐧𝐠 𝐩𝐞𝐫𝐟𝐨𝐫𝐦𝐚𝐧𝐜𝐞 𝐭𝐡𝐫𝐨𝐮𝐠𝐡 𝐛𝐫𝐮𝐭𝐞 𝐟𝐨𝐫𝐜𝐞 𝐚𝐧𝐝 𝐬𝐭𝐚𝐫𝐭 𝐝𝐞𝐬𝐢𝐠𝐧𝐢𝐧𝐠 𝐢𝐧𝐭𝐞𝐥𝐥𝐢𝐠𝐞𝐧𝐜𝐞 𝐭𝐡𝐚𝐭 𝐫𝐞𝐬𝐩𝐞𝐜𝐭𝐬 𝐞𝐧𝐞𝐫𝐠𝐲, 𝐩𝐫𝐢𝐯𝐚𝐜𝐲, 𝐚𝐧𝐝 𝐥𝐨𝐜𝐚𝐥𝐢𝐭𝐲. https://lnkd.in/dg_8XVj8 𝘛𝘩𝘪𝘴 𝘤𝘰𝘯𝘵𝘦𝘯𝘵 𝘩𝘢𝘴 𝘣𝘦𝘦𝘯 𝘤𝘳𝘦𝘢𝘵𝘦𝘥 𝘸𝘪𝘵𝘩 𝘵𝘩𝘦 𝘩𝘦𝘭𝘱 𝘰𝘧 𝘋𝘰𝘯𝘯𝘢, 𝘮𝘺 𝘈𝘐.
6
-
Anjali Batra
3K followers
🚀 Making Models Pay Attention: Inside the Mind of an LLM If you caught my earlier post on LLM — you already know that a Large Language Model is, at its core, a sophisticated text predictor. But have you ever wondered how it decides which words to focus on when generating an answer? How does your prompt — “What’s the recipe for dosa?” — transform into a coherent, context-aware response? That’s where the Attention Mechanism comes in — the heart of the Transformer architecture and the reason LLMs revolutionized NLP. 🧩 Here’s the intuition: Attention helps the model decide which tokens matter most when predicting the next one. It’s like giving each word a spotlight based on its importance to the overall meaning. When you input a sentence, the model computes three vectors for each token — Query, Key, and Value — and determines how much each token should “attend” to others. This is how the model captures relationships like: ‘The staple food of Punjab is Paratha, and the staple food of South India is ___.’ the model pays attention to the region–food pattern and confidently serves you Dosa! 🥞😋” That’s how LLMs learn — by attending to patterns, not memorizing cookbooks! What’s fascinating is that modern LLMs like GPT-4, Llama 3, and Mistral use multi-head attention, meaning multiple “perspectives” analyze context in parallel — enabling richer understanding and creativity. ⚡ Fun fact: Researchers discovered something called the Attention Sink, where the first token often attracts disproportionate attention — a curious artifact that might actually help stabilize training! The attention mechanism is what allowed Transformers to surpass older architectures like RNNs and LSTMs — and scaling it up is what made models suddenly capable of reasoning, coding, and storytelling. Let me know if you’d like me to dive deeper into how the attention mechanism really works.
11
-
Dr. Habib Shaikh, PhD (AI)
Northern Trust • 24K followers
𝐇𝐞𝐫𝐞 𝐚𝐫𝐞 6 𝐝𝐞𝐬𝐢𝐠𝐧 𝐩𝐚𝐭𝐭𝐞𝐫𝐧𝐬 𝐬𝐡𝐚𝐩𝐢𝐧𝐠 𝐭𝐡𝐞 𝐧𝐞𝐱𝐭 𝐠𝐞𝐧𝐞𝐫𝐚𝐭𝐢𝐨𝐧 𝐨𝐟 𝐀𝐈 𝐚𝐠𝐞𝐧𝐭𝐬: ➤ Sequential Architecture Tasks are processed step-by-step using a defined flow. Great for predictable, structured automation. ➤ Tool-Enhanced Memory LLMs access external tools to recall, transform, and reason with long-term data. Think smarter context, better answers. ➤ Multi-Agent Collaboration Multiple agents work together - each with specific roles. From researchers to planners, they form a digital workforce. ➤ Shared Tool Interfaces Agents use common tools (e.g., browsers, code editors) to stay aligned. Enables coordination and parallel task handling. ➤ Hierarchical Agent Design Supervising agents delegate tasks to sub-agents. Allows scalable, modular execution. ➤ Human-in-the-Loop AI + Human judgment = best outcomes. Crucial for oversight, ethics, and decision quality. 🌟 Follow the AIKaDoctor (Free AI & Data Science Resources) channel on WhatsApp: https://lnkd.in/dCTCEKKc 📌Follow Habib Shaikh For more such content.
147
27 Comments -
Morsy Cheikhrouhou
RingCentral • 6K followers
GPT-5.4 can now control your computer. Not APIs — actual mouse and keyboard. The implication nobody's grasping: we're moving from "AI helps me" to "AI acts for me." That changes the human role entirely. From orchestrator to conductor. #AI #AIAgents #FutureOfWork https://lnkd.in/gwYveVN5
5
-
Georgios Mappouras
LinkedIn • 425 followers
I think Sam Altman, in his recent interview, essentially agreed with my paper “Turing Test 2.0: The General Intelligence Threshold”! He proposed that if a future AI model could “…figure out quantum gravity and could tell you its story,” that would indicate that AI has achieved AGI, and that a truly creative AI would “…come up with new scientific knowledge”. This perfectly aligns with the framework I proposed for testing AGI. I define AGI as the ability to generate new functionality by applying new knowledge that was not previously introduced through training. My framework (Turing Test 2.0) generates tests that can determine if a model has achieved AGI in a simple fail-pass result. I even present some examples of applying these tests to popular LLMs! Having a precise and measurable definition for AGI can help us better understand how close we are to achieving this goal. If you want to learn more about my work, you can read my paper, or you can listen to me discuss my work with Prof. Robert J. Marks in his podcast MindMatters in a three-part series (links below). You can read my paper here: https://lnkd.in/gStXD_pF You can listen to me talk about my work here: Part 1: https://lnkd.in/g-_tzJZt Part 2: https://lnkd.in/gdnZX6pz Part 3: https://lnkd.in/gaCBzPvZ Sam Altman’s interview: https://lnkd.in/gtENirSu
28
1 Comment -
Mike Vitale
Wowza • 2K followers
If your streaming workflow needs precise business logic, custom modules are the answer. This Thursday, Ian Zenoni and I are digging into how to extend Wowza Streaming Engine through scalable, real-world implementations. We’ll cover when modules make sense, walk through a practical example of custom metadata injection, and share hard-earned tips on testing, debugging, and running modules in production. If you’ve ever said “I just need Engine to do one more thing,” this session is for you. I will, of course, be dressed in my finest sports coat and strongly encourage audience participation. Bring your questions.
15
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top contentOthers named David Karam
-
David Karam
Los Gatos, CA -
David Karam
Greater Montreal Metropolitan Area -
David Karam
Amsterdam -
David Karam
United Kingdom
68 others named David Karam are on LinkedIn
See others named David Karam