←
Asheem Chandna1,591 posts
Asheem Chandna avatar✓

Asheem Chandna ✓

@chandna

@GreylockVC: partnering with outlier founders, to build category-defining companies. from idea to ipo, and beyond. 10x forbes midas list.

◷ Joined February 2008▧ 12 Photos and videos
Hari avatar
⟳ Asheem Chandna retweeted
Hari@hrkrshnn·Nov 16

Crazy day in security 1. @Chase, @BankofAmerica, @WellsFargo and @Zelle went down. They claim it's not a hack or security incident. Downtime will have huge downstream economic impact. 2. @Optimizely scripts were poisoned on 178+ sites: @Zoom, @BBC, @CNN, HSBC and more. Visitors were served malware. 3. @united had an outage and held flights. Root cause is unknown. 4. @Google reports the first fully automated patch-to-exploit pipeline. AI agents are now running attacks end to end. Will every day from now look like this?

Ali Partovi avatar
⟳ Asheem Chandna retweeted
Ali Partovi@apartovi·Nov 9

Altara's early team reminds me of some of the strongest startups I've ever backed: super-strong, super-technical.

Post attachment
Lenny Rachitsky avatar
⟳ Asheem Chandna retweeted
Lenny Rachitsky@lennysan·Nov 9

My biggest takeaways from Head of Product for @Gemini and Google's other frontier AI models—Tulsee Doshi (@tulseedoshi): 1. Great PMs are more in demand than ever. “When you can build anything, building something great actually is now where most of the value is,” Tulsee said. The scarce skill is now identifying which of the thousands of possible things to build is the one worth building. Alongside that is putting that judgment into practice: aligning people and converting speed-induced chaos into a coherent direction. 2. The PM role has shifted from writing requirements to creating something with “heft.” The PM who hands a requirements doc to an engineer and calls it done is not going to do well in this new environment. The new baseline is going one step further: actually producing something of substance, be it a prototype, a thorough data analysis, or even a ready-to-ship MVP. 3. Tulsee hires PMs who have opinions about models. She wants PMs who play with models every day, have their own use cases for judging whether a model is good, and stress-test capabilities themselves. They’re also technical enough to roll up their sleeves, dig into data, and build an eval. And they’re adaptive: “The space is changing every two weeks. A roadmap you wrote two months ago, you’re gonna be looking at it again and rewriting it.” 4. To understand a new model, test it on work you care about. When a new model comes out, some people try 3D animations, others creative writing or hard financial analysis. Tulsee’s advice for evaluating new models is to pick tasks where models “are already showing signs of life” but aren’t perfect by your own definition. That leaves room to see different models handle the problem differently, and it’s where you’ll notice how the models improve. 5. Model development is less like engineering and more like alchemy. “Model training is kind of like Snape’s potions class,” she says. “You can put all the ingredients in and be thoughtful about what you expect, but you also have to expect that there will be a little bit of magic.” Her team’s job is to identify where the model shines (often in ways no one planned) and to turn that into something great for users. 6. Tulsee’s 60-20-20 rule is a practical way to build ahead of the models. Your AI product roadmap should look like this: roughly 60% of what you build should work today, another 20% should be close—“not perfect, but you can see how the models might get here in the very near future”—and the final 20% should show glimmers of something magical that the model can’t quite do yet. The exact numbers are flexible, but the idea is to be ready to double down on something that just became possible. 7. Your first eval can be five prompts. When tackling evals, the most common mistake people make is waiting until you can build something large-scale before even starting. “Start with even just five prompts,” she says. “Start simple. Start with even just yourself as the rater.” A set of even 20 prompts that creates a signal between model A and model B is “so powerful.” Getting to a small, honest set of examples forces you to articulate what “good” looks like. Get clear on a set of good examples first, then scale up. 8. Burnout comes from chaos and grunt work more than from long hours. Tulsee admits everyone on her team is “putting in all of the hours.” But in her experience, burnout comes from churn and chaos, and work that feels like a waste of time. Work you’re excited about is exhausting but brings more joy. That’s why she hopes AI tools can reduce burnout by removing the grunt work, so people spend more time thinking and being creative. My tech workforce survey found the same thing: more hours doesn’t necessarily equal burnout. 9. Google’s full-stack AI strategy gives it an advantage few competitors can match. From custom TPU hardware to products used by over a billion people each, Google operates across the entire value chain. Tulsee describes Google’s goal as building models across the “Pareto curve of cost to quality”—not just the frontier LLM but models that serve a search user, a software engineer, and a cyber defender. Frontier competition matters to Google, and Tulsee is direct about Google’s intention to win the SOTA model race.

Brian Armstrong avatar
⟳ Asheem Chandna retweeted
Brian Armstrong@brian_armstrong·Nov 7

I've changed how I work over the last few weeks. I now have one lead agent for each area of focus, running all the time, and a chief of staff agent that oversees them. Each lead manages its own sub-agents that write code, test it, chase reviews, and coordinate with team members. Everything I need to decide or review comes into one prioritized queue, a simple local web app. Each product review includes screenshots and a video demo of the feature. I clear the queue in batches, mostly by voice and keyboard shortcuts. The leads also bring back ideas I hadn't considered. Working from one queue, instead of switching between dozens of chats, has cut a lot of mental overhead. The system keeps learning my preferences and distilling my judgment into a "Brian brain," so its recommendations and first drafts get better before they reach me. The goal is fewer corrections per change. Every change still goes through the same human review and security checks. It is eliminating tasks, not human judgment. What an exciting time to push the frontier of productivity, especially as we build the economy for agents (agentic finance). We should all keep pushing in this direction.

Robert Yang avatar
⟳ Asheem Chandna retweeted
Robert Yang@GuangyuRobert·Nov 2

revenue per employee tells you a lot about company culture & talent density jane street's revenue/employee only rivaled by anthropic ramp is highest among fintech startups, but still lower than goldman

Post attachment
Amir Efrati avatar
⟳ Asheem Chandna retweeted
Amir Efrati@amir·Oct 28

🕵️ Goldman Sachs' biggest AI expense is coding tools, but spending on AI for finding security bugs could soon be on par!

Post attachment
Harry Stebbings avatar
⟳ Asheem Chandna retweeted
Harry Stebbings@HarryStebbings·Oct 31

I have invested in 14 $BN over the last 10 years and the one mindset trait all of them share: They have a superiority complex; they fundamentally believe they are better than others. Their success is inevitable. Combined, with this they are incredibly critical of themselves. They are never content with where they are, their own performance. They always masochistically push themselves for more. All of the best founders share this seemingly parodoxical mindset.

Idobn avatar
⟳ Asheem Chandna retweeted
Idobn@idobn·Oct 29

Using advanced AI models @blockaid_ detected what is likely the biggest hack in the history of the world.

Post attachment
Blockaid avatar
⟳ Asheem Chandna retweeted
Blockaid@blockaid_·Oct 29

We are investigating a cluster of large outflows from Binance hot wallets that began at approximately 20:24 UTC on 29 October 2026. On-chain, the transfers look consistent with unauthorized movement from those wallets, but this has not been confirmed by Binance, and we cannot yet rule out an internal treasury or operational sweep. Observed chains: Ethereum, Arbitrum, and Avalanche, with related receipts also visible on Optimism. Observed scale (approximate, still being reconciled): Ethereum: about $2.5 billion from Binance 14 and Binance 16, plus an additional 780,000,000 USDC from a Binance smart account Arbitrum: about 8,426 ETH (~$19.5 million) Avalanche: about 1.81 million AVAX and 8.4 million USDT (~$24 million) Affected Binance wallets include: Ethereum Binance 14: 0x28C6c06298d514Db089934071355E5743bf21d60 Ethereum Binance 16: 0xDFd5293D8e347dFe59E90eFd55b2956a1343963d Ethereum smart account: 0xEe7aE85f2Fe2239E27D9c1E23fFFe168D63b4055 Arbitrum Binance 56 / Hot Wallet 1 / Binance 89: 0x1b5b4e441f5a22bfd91b7772c780463f66a74b35, 0xf92402bb795fd7cd08fb83839689db79099c8c9c, 0x3931dab967c3e2dbb492fe12460a66d0fe4cc857 Avalanche Binance 49 / 85 / 110 / 118: 0x9f8c163cBA728e99993ABe7495F06c0A3c8Ac8b9, 0x6D8bE5cdf0d7DEE1f04E25FD70B001AE3B907824, 0xABa2D404C5C41da5964453A368aFF2604Ae80A14, 0x3BCE63C6C9ABf7A47f52c9A3a7950867700B0158 Primary collection address (same across the affected chains): 0x5227f603C1eE34CE3C06eFe6477003BDfCCB2f8c Further destination wallets currently holding a large share of the funds include: 0x9749292D74Fd460982d0912eA9515EA24736C762, 0x0Ddf0480016e6bCb2C1F5d190D221FBA1320697e, 0x8532fa14acaf483729c449b8458aeddb900543d4, and 0x8d53903625b8e839b9DF4bd28B0EFb1CD6b8639A. We recommend treating this as unconfirmed until Binance issues an official statement. We will update as we verify more.

Post attachment
Reid Hoffman avatar
⟳ Asheem Chandna retweeted
Reid Hoffman@reidhoffman·Oct 26

Strategic optimism is the way to build a beautiful future.

Race 🕊️ avatar
⟳ Asheem Chandna retweeted
Race 🕊️@multiplanet1·Oct 11

A retired NASA engineer who had worked on the Space Shuttle program for 25 years was hired by SpaceX at age 62. He described the first week as the most disorienting experience of his professional life. At NASA, a design change required 3 meetings, 2 committees, a review board, and 6 to 18 months of documentation. At SpaceX, his new supervisor said "if it works, build it. If it doesn't, change it by Friday." He sat at his desk after the first day and called his wife. He told her he felt like a man who had been swimming with ankle weights for 25 years and someone just cut them off. He could move. He could decide. He could build something in the morning and test it in the afternoon. The constraint that he had accepted as the nature of aerospace engineering turned out to be the nature of bureaucracy. Within 6 months he had contributed to more design iterations than he had completed in his last 5 years at NASA. Not because he was working harder. Because the time between having an idea and testing the idea collapsed from months to hours. The same brain. The same knowledge. A different operating system. He described a specific moment where he proposed a modification to a Raptor engine component. At NASA, the proposal would have entered a queue. At SpaceX, the modification was machined by the end of the day and tested by the following morning. He watched his idea become a physical object in 18 hours. At NASA, 18 hours would not have been enough to schedule the first meeting to discuss whether to schedule a meeting. He told an interviewer: "I didn't get smarter when I went to SpaceX. I got faster. The intelligence was always there. The system was in the way." The difference between SpaceX and NASA is not talent. NASA has extraordinary talent. The difference is the time between a thought and a test. SpaceX compresses it. NASA elongates it. The same engineer produces 10x more at SpaceX than at NASA because the bottleneck was never the engineer. It was the meetings about the meetings about the work.

Asheem Chandna avatar
Asheem Chandna@chandna·Oct 14

When attackers use new sophisticated #AI, enterprise defenders cannot rely on legacy #cyber with AI only bolted on top. I’m excited about what @CylakeAI is building from the ground up, with customers keeping full control of their data and infrastructure. Thanks René Bonvanie for the insightful conversation.

Post attachment
Adam Shuaib avatar
⟳ Asheem Chandna retweeted
Adam Shuaib@adamshuaib·Oct 12

One of the worst predictors of founder success we've tracked is how well someone pitches; the correlation between pitch quality and outcome was often negative. Zuckerberg was so awkward in early investor meetings that VCs wondered if he could ever manage anyone, and Larry Page refused interviews and earnings calls for years. Bezos had to pitch 60 different investors to raise his initial $1 million. Highly articulate people are great with the 30min process of telling a story to strangers, but this is a pretty different skill to building a company. Founders who spend years optimising to be persuasive have often optimised away from the building skills that compound over the 10yrs of execution that come afterwards; it’s incredibly hard to do both well. The articulate founder will impress your partners but the awkward one will return your fund.