In my opinion, you’re thinking about things in reverse: deciding you want to make a big impact through starting a business, and then looking for specific proble

In my opinion, you’re thinking about things in reverse: deciding you want to make a big impact through starting a business, and then looking for specific problems to solve that might lead to a business. A lot of people in the general tech/startup world believe that’s a totally normal order in which to approach things, and it probably works for some people, but if nothing is screaming at you to solve it, IMO you are better off building experience in a domain or skill and then revisiting this later. You probably don’t have enough experience or context to know what’s worth solving (and a viable problem to solve for a for profit company). Note that advice from VCs is from their perspective, not yours - they may be willing to take a bet on you being able to eg disrupt podiatry with at-home laser wart treatment, but do you really want to just be someone’s 100:1 bet? I worked for 5-6 years as a software engineer before recently starting my company, even though I’ve always known that I wanted to try founding a tech startup. And now I’m really glad I didn’t just immediately dive into entrepreneurship out of college. What I learned as an employee gave me experience in industries, technical problems, organizational practices/techniques/antipatterns, and soft skills that would have been major obstacles to starting a business. I have plenty of ideas for how to start a tech business now, because I know how I’d build the products and can identify a lot of problems/opportunities in the areas that I’m familiar with. So IMO it can actually help a lot to simply work as an employee in some area that interests you - marketing, sales, AI, cloud, webdev, robotics, whatever - with the long term goal of starting a company once you figure things out. That’ll help you identify real problems beyond just “X for Y”.