If it's a software solution, the idea that the skills for the “built a solution” part of that are not related to coding seems to be generally untrue. Yes, a solo project of the type involved more than coding skills, but product owner skills without tech skills don't call forth software from the depths of the abyss, though they can produce a nice idea of what a software solution would look like if someone was available to build it.
Many people can fight through learning enough code to whip out an MVP. But did they do it effectively, or did they spend 3 months doing what most coders do in 3 days? Did they do it well, or is it brittle code that needs major refactoring?
So while you are right that coding has to happen, I stand by the original statement that the mere presence of code does not inspire me to interview the person who created it.
What it would inspire me to interview you for is an junior PO role. You found a problem, built a solution, got a few customers, and have kept them happy. The skills to do that are not related to the coding -- they are product design/ownership skills.