Hi Vorto team,
What caught my attention is that your software has to work on a messy day, not just in a demo. At Front Range Internet, I ran the NOC and handled engineering escalations for hosting and colocation customers. I also maintained production web services and replaced billing software. Working on both sides taught me to build tools that tell operators what happened and give them a clear next step.
NuPrice brought a different version of that problem. I built and operated a marketplace repricing application that pulled in competitor data and applied rules customers controlled. I owned the application, billing and support, so I saw how a data or workflow decision played out for the people using it. I’ve since built React and TypeScript interfaces, typed APIs and PostgreSQL workflows for client products, and put AI-assisted workflows to work with explicit data boundaries and a person reviewing the output.
I’d bring that mix of product engineering and production ownership to Vorto. I’d like to learn which steps still make people leave the software and chase down an answer, then build something that takes that work off their hands.
Thanks,
Chad