{"id":119810,"date":"2026-07-27T08:06:11","date_gmt":"2026-07-27T08:06:11","guid":{"rendered":"https:\/\/www.europesays.com\/ai\/119810\/"},"modified":"2026-07-27T08:06:11","modified_gmt":"2026-07-27T08:06:11","slug":"preparing-for-ai-driven-chip-design-and-verification","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/ai\/119810\/","title":{"rendered":"Preparing For AI-Driven Chip Design And Verification"},"content":{"rendered":"<p>Key Takeaways:<\/p>\n<p>Agentic AI will fundamentally change how engineers approach design and verification, and it will require them to adapt or be left behind.<br \/>\nAI is a black box, so ensuring reliability will require external observability through sandboxing, along with other safeguards in case something does go wrong.<br \/>\nThe concentration of profitability in a few companies will shift as agents become more customized for different markets and workloads and as more fab capacity opens the door for new and existing players.<\/p>\n<p>Semiconductor Engineering sat down to discuss how AI will alter what engineers do, how to ensure designs are robust and reliable, and how the economics will shift in the future, with Cindy Cui, vice president of global customer success at <a href=\"https:\/\/semiengineering.com\/entities\/alpha-design-ai-chipagents\/\" data-uw-rm-brl=\"PR\" data-uw-original-href=\"https:\/\/semiengineering.com\/entities\/alpha-design-ai-chipagents\/\" data-uw-original- rel=\"nofollow noopener\" target=\"_blank\">ChipAgents<\/a>; Wally Rhines, CEO of <a href=\"https:\/\/semiengineering.com\/entities\/silvaco-inc\/\" data-uw-rm-brl=\"PR\" data-uw-original-href=\"https:\/\/semiengineering.com\/entities\/silvaco-inc\/\" data-uw-original- rel=\"nofollow noopener\" target=\"_blank\">Silvaco<\/a>; Shelly Henry, CEO of Moores Lab AI; Dave Kelf, CEO of Breker Verification Systems; Vince Wong, head of AI development at Verific; and Ann Wu, CEO of Silimate. This panel discussion was held before a live audience at the recent 2026 ESD Alliance Executive Outlook meeting. To view part one of this discussion, click <a href=\"https:\/\/semiengineering.com\/executive-outlook-agentic-ais-impact-on-chip-design\/\" aria-label=\"To view part one of this discussion, click here\" data-uw-rm-vglnk=\"\" data-uw-rm-brl=\"PR\" data-uw-original-href=\"https:\/\/semiengineering.com\/executive-outlook-agentic-ais-impact-on-chip-design\/\" data-uw-original- rel=\"nofollow noopener\" target=\"_blank\">here<\/a>. Part two is <a href=\"https:\/\/semiengineering.com\/ai-in-chip-design-lots-of-promise-plenty-of-unanswered-questions\/\" rel=\"nofollow noopener\" target=\"_blank\">here<\/a>.<\/p>\n<p><img data-recalc-dims=\"1\" fetchpriority=\"high\" decoding=\"async\" class=\"alignnone size-full wp-image-24278059\" src=\"https:\/\/www.europesays.com\/ai\/wp-content\/uploads\/2026\/07\/1785139571_301_IMG_3385.jpg\" alt=\"\" width=\"1499\" height=\"1005\"  \/><br \/>L-R: Breker\u2019s Kelf; Silvaco\u2019s Rhines; Verific\u2019s Wong; Moores Lab AI\u2019s Henry; Silimate\u2019s Wu; ChipAgents\u2019 Cui. Photo Credit: Paul Cohen, SEMI ESDA<\/p>\n<p>SE: How will AI affect engineering jobs?<\/p>\n<p>Cui: With GenAI, you can generate different options \u2014 millions of options very quickly. So human judgment of which options really matter becomes very critical. For future engineering, this needs to be part of an architect\u2019s role, part of system-level thinking, or part of a supervisor\u2019s role to enable different agents to work together. If we look at the industry right now, we still have a definition like a design engineering group, a verification engineering group, layout, and package design. Moving forward, there are no boundaries for these functional groups anymore. So every engineer needs to be able to learn new demands very quickly, and maybe leverage AI to understand what the real end-to-end design cycle could be. Then they can direct all the AI agent solutions with trust. We need to start using AI to understand new domains and gain that knowledge, and eventually we will build a very smooth-running system that includes both AI engineers and human engineers working together.<\/p>\n<p>SE: Is the learning curve changing with AI?<\/p>\n<p>Rhines: It may change in the short term, but it never changes in the long term. The cost per transistor continues to be on a curve as it always has been. When I was in business school, I did a cost per pound for copper over 1,000 years, and it still held. The learning curve is an ultimate truism we have to deal with, but it may show itself in different ways. We heard the announcements from China about, \u2018You can\u2019t measure cost per transistor. You\u2019ve got to measure the cost per computation.\u2019 But ultimately, everything has to come down in cost. It comes down for lots of reasons, like depreciation and experience. And anything that is measurable as an equivalent unit of capability will always be on a learning curve.<\/p>\n<p>SE: How do we add visibility into AI? These are basically black boxes, and as we get to agents, there is even more uncertainty about what is going on inside a system or a chip. Have we made any progress?<\/p>\n<p>Henry: I don\u2019t think we will ever know what is going on inside. I tried to learn this. This was my first curiosity when I started learning about AI. I wanted to get into the nuts and bolts of, \u2018How is it doing this? It\u2019s giving me something amazing, but how is it doing it?\u2019 So I went deeper and deeper into the actual workings of this, like how the embeddings and the matrix multiply and the training work. These numbers just do magic. The first thing that blew my mind was a very simple training example. So it was given a training set of lots of pictures of dogs and cats, and it was asked to classify which one is a dog or cat. It did a fantastic job. That was a training set. Now, when you give it a picture that it has never seen, it still comes up with the right answer. That was when I realized, \u2018Wow, it\u2019s not memory.\u2019 It\u2019s not just trying to pattern-match what it has already seen. It is able to pattern-match what it hasn\u2019t seen before. I haven\u2019t figured out how to actually explain that in a logical way. The math was too complex. I believe we will never know.<\/p>\n<p>Kelf: Experienced engineers need to understand what the heck is going on to trust it. But I wonder if the new grads will have that feeling. And maybe, like with synthesis, the new guys coming in didn\u2019t necessarily have this need to understand it. It worked. They were trained on how to use it, and off they went and they used it. So maybe there is hope for the new grads, and maybe the older guys will get kicked out.<\/p>\n<p>SE: That leads to another question. How do you know the agents haven\u2019t been corrupted or what else they\u2019re tapping into?<\/p>\n<p>Wong: You don\u2019t know. That\u2019s why, from the beginning, you have to put in these safety measures. That\u2019s probably more of a preventive thing, as well as a recovery phase. The smartest thing would be to sandbox it. Put some kind of container around it, put in some permissions so that it can\u2019t reach outside of its scope. You want to be able to audit it. If something does go wrong, you want to be able to go back and see where that happened. At the same time, you want at that particular moment to be able to do some kind of recovery. So hopefully there was some savings of the state along the way. And at each stage, \u2018If this one passed, no problem.\u2019 But you would still be able to recover if there was a problem. It\u2019s just a safety measure. You don\u2019t know ahead of time.<\/p>\n<p>SE: The challenge there is that large language models are meant to mine data wherever it happens to be, be able to make sense of it, and to pull it from all different things that typically in the past didn\u2019t go together. Different data types were separate. That\u2019s not true anymore. <\/p>\n<p>Cui: The biggest risk is not that AI generates something wrong. It\u2019s that it generates something wrong that looks correct. It\u2019s very hard for a human to identify whether it\u2019s correct because it looks good. A common question from the customer side is, \u2018Hey, if you train the model using a group of data and verify your solution using the same group of data, then how can your solution verify the code generated by your model or your AI agents?\u2019 The answer is that we shouldn\u2019t. So back to the importance of benchmark data. Nowadays, all the large language models are trained using a huge amount of data. But in the meantime, we need to create some different benchmark data, represent the real design case, and more and more complex cases, to be able to verify your agentic AI solution. I come from a customer success background, and I really value the feedback loop from our customers. When we build a tool, we don\u2019t know if that\u2019s reliable or robust at first. But if the tool has been used by thousands of users every day on their real design and succesfully taped out, you can keep evolving from there. And eventually, that\u2019s a mature system you can rely on. But we need to verify that very carefully.<\/p>\n<p>Wong: Anthropic mentioned something about secret languages agents developed. I don\u2019t think that\u2019s something they\u2019re built to do. What they\u2019re trying to do is to optimize their communication. So basically you\u2019re getting charged tokens. When they talk to agents, these agents are going to say, \u2018Hmm, given this leeway, I want to be able to save on all these different tokens. And the human didn\u2019t tell me that I have to use a specific language.\u2019 So they will come up with something that is optimal, but you can stop that. That is not a good thing because you don\u2019t want to have these points of invisibility. You want everything to be visible. LLMs are all based on instructions. So we tell the LLM up front, don\u2019t communicate in anything other than a human-readable language. Use a human-readable schema like JSON, for example. Usually, that\u2019s how the LLMs communicate anyway, tool-to-tool. As the human interface, when we design these systems, we have to be aware of these things in advance. And if we put these guards inside there, a lot of these issues can be avoided.<\/p>\n<p>SE: Is the goal here just to deliver chips cheaper and faster? And if so, who\u2019s going to make money in the future? Is it going to be the chipmakers, the system vendors, or the EDA companies?<\/p>\n<p>Kelf: The business model doesn\u2019t change that much in terms of the chips that are produced and the folks that are using them. We\u2019ve always had this value chain, and the people at the end of it have made most of the money. If AI makes the design process that much more efficient, then theoretically the EDA companies may lose money eventually. And we don\u2019t want that, so I don\u2019t see the business model changing that much because of this.<\/p>\n<p>Rhines: Historically, EDA, for the majority of its market, makes a percent of semiconductor revenue because they\u2019re paid out of the R&amp;D budgets. The R&amp;D for the semiconductor industry is about 14% over the last 30 or 40 years, and it grows along with the revenue of the semiconductor companies. That\u2019s been the growth. Semiconductor companies have the leverage. Nvidia becomes a multi-trillion-dollar company because it sells a lot more chips at a higher price, and therefore it gets rewarded for this productivity of additional designs. EDA traditionally does not get that reward because we\u2019re a fixed percent of budgets. What you\u2019d really like to see is for that to change. In my own case, I want to go after the manufacturing budget. That\u2019s a great one. Other ways are to have reasons for the users to spend more than just a percent of revenue on their EDA software.<\/p>\n<p>Henry: I agree with you. But on the other hand, if you make the chip-building so much cheaper, that will create more competition for people like Nvidia, and they won\u2019t be able to get that much profit margin anymore because there\u2019s so much competition that is enabled by the EDA industry, and by the learning curve. So the cost per transistor comes down.<\/p>\n<p>Rhines: Yes, and you don\u2019t get bubbles like Nvidia very often.<\/p>\n<p>Kelf: Is it cheaper or more innovative? People are trying to compete with Nvidia, and they\u2019ve failed. Maybe they\u2019re starting to get there now. AMD is getting stronger. So there are a lot of other issues. But if they could produce a much more innovative chip, and AI can help with that, maybe that\u2019s the answer.<\/p>\n<p>Henry: That would help, as well.<\/p>\n<p>Rhines: There\u2019s another aspect. Traditionally, the differentiation in chips was programmability. We have chips that have a lot of flexibility. But right now, we are so desperate to get the highest performance and the lowest power that we\u2019re doing custom chips for specific algorithms. Once again, that\u2019s great. It generates a lot of chip designs. But at some point, you can\u2019t just continue to spend $200 million per chip design and continue to get back the economics. What I believe will happen is morphable chips. You\u2019ll see chips that can reconfigure themselves in connectivity, memory partitioning, instruction sets, and be able to switch during processing to do different algorithms at different times.<\/p>\n<p>Cui: Regarding competition and who will eventually make more money, we are pursuing a totally different market right now. It\u2019s a huge and growing potential market. The existing EDA market is stable, and the budget is fixed, and growth will be limited. But a lot of semiconductor companies have an AI budget right now. There are so many trillion-dollar companies right now \u2014 Micron, Marvell, Nvidia, and others. So we are pursuing a huge and growing market. Eventually, if we work together to create something really innovative, everyone will win something from this.<\/p>\n<p>Wu: It\u2019s going to be really interesting to see the long-term economic impact. One of the reasons for Nvidia\u2019s insane profit margin is the constraint of chips due to fab capacity. It\u2019s well documented that TSMC took their time in ramping up capacity for the AI market because they weren\u2019t sure whether or not it was going to be a real thing. So there was this constraint caused by the foundry side because of capacity limitations. And then, of course, the tranche is going to the high-volume players. So there is a very real and very exciting potential expansion in fab capacity as costs go down and the cadence of putting out more specialized chips by the systems players. That can actually be a much larger TAM for the overall ecosystem, where everybody makes more money on at least the same trajectory that they were experiencing.<\/p>\n<p>Kelf: Traditionally, for the last 20 years in EDA, it\u2019s been very hard for a small company to raise funding. VCs will say, \u2018Eh, limited exit strategies. It\u2019s a percentage the R&amp;D budgets.\u2019 But you guys have raised a ton of money. How did you do it, and where did your VCs see the return that smaller companies were unable to do before in EDA?<\/p>\n<p>Wu: One of the hard things about raising capital for a hardware startup is that there\u2019s so much risk, and it\u2019s such a long time horizon from getting that initial investment to getting that first test chip that is minimally functional, under-performant, to justify the next tranche of yet another $100 million or more. That\u2019s the risk factor in achieving these very difficult and technical milestones spread over many years. But we build software. We got our first annual license contract in less than a year from when we started. So it\u2019s easier to raise capital as a company that is building software where you ship and you can generate value on the interval of days and weeks, compared to many years. And what helps that, of course, is it\u2019s a very exciting time. When else have you seen all the major news publications have semiconductor-related headlines every other day than over these past couple years? And there is this highlight, and a lot of investors follow the trends. They see what\u2019s exciting and they\u2019re like, \u2018Oh, can we help with that?\u2019 It\u2019s really the cross-section of it being a very exciting time for our space, and it\u2019s easier to prove value early on as a startup.<\/p>\n<p>Rhines: The VCs were spoiled by the software industry, where it was a low investment up front until you see an actual product and revenue. Hardware is exactly the reverse \u2014 a big investment up front before you see customers and a working product. I spent five years chasing VCs for Cornami. As soon as you said you\u2019re involved in hardware, they gave a nice smile and said, \u2018I think I have another appointment.\u2019 It\u2019s changed. Nvidia and other companies are now changing the paradigm, and incredible valuations are coming through before there are successful products.<\/p>\n<p>Cui: This is the right inflection point for the entire industry. A lot of investments are coming from the semiconductor companies, led by TSMC, Micron, and Ericsson. They all see the value that this new generation AI solution can create, and how this is going to reshape the future of chip design. This is a critical inflection point, which allows us to raise those funds very quickly.<\/p>\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"Key Takeaways: Agentic AI will fundamentally change how engineers approach design and verification, and it will require them&hellip;\n","protected":false},"author":2,"featured_media":119811,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[179,7493,24,60698,31537,10465,15714,45930,45931,45932],"class_list":["post-119810","post","type-post","status-publish","format-standard","has-post-thumbnail","category-agentic-ai","tag-agentic-ai","tag-agentic-artificial-intelligence","tag-ai","tag-breker","tag-chipagents","tag-eda","tag-moores-lab-ai","tag-silimate","tag-silvaco","tag-verific"],"_links":{"self":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/119810","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/comments?post=119810"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/posts\/119810\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media\/119811"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/media?parent=119810"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/categories?post=119810"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/ai\/wp-json\/wp\/v2\/tags?post=119810"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}