Technical Co-Founder & CTO
Kunstruct AI is an AI copilot for hardware engineering teams. We bring a company's engineering knowledge, drawing standards, and manufacturability guidance directly into the CAD environment, so problems surface while the fix is still an edit rather than a change order.
Engineering teams lose hundreds of hours to review work that happens too late. Drawings leave review with missing callouts or wrong tolerances, and the real feedback arrives from a machinist or supplier after release, when correcting it costs a full redesign cycle. In our April 2026 survey, 79% of engineers reported hitting redesign loops after release.
April 2026 survey of 24 senior mechanical engineers.
We are building for automotive and vehicle platforms, industrial equipment, and medical devices first. The same checks apply to anything with fasteners, tolerances, and a drawing package.
Winner of the 2026 Kelley EVC Pitch Competition, with business development and strategic support from the Kelley School of Business at Indiana University. Delaware C-corp formation in progress, IP strategy underway, and groundwork laid for our institutional seed round.
Being clear about this, because it defines the job.
There is a web-based drawing checker live at app.kunstruct.ai. It is free, and it exists to test demand and collect feedback on whether engineers want these tools at all. Early signal is good. It is a validation instrument, not the product.
The product is the copilot inside the CAD environment. Engineers do not want another browser tab. They want the checks, the standards, and the past-program knowledge available in the CAD session while they are still designing. Building that is the core technical challenge and the reason this role exists.
The roadmap behind it is the flow a design engineer actually runs: parsing customer requirements, matching against past programs and parts in PDM, recommending what has to change, running manufacturability analysis on live 3D geometry, and reviewing the drawing package. Plus the engineering work underneath: GD&T advisory, tolerance stack-ups, ECO generation, FAI packages, and inspection documentation.
Every company has its own release process, build plan, and quality flow, on systems that took years to stand up. We never ask them to replace any of it. We configure around their gates, checks, and internal standards, and our tools read and write the documents their process already produces. Their CAD, PLM, MES, and QMS stay where they are.
That means building against the real stack: SOLIDWORKS, NX, Creo, and CATIA on the design side, and Teamcenter, Windchill, 3DEXPERIENCE, ENOVIA, and PDM Professional behind them.
This is how we win, and it is the part of the job that is genuinely hard. If custom-fitting an AI system into a different enterprise environment each time sounds like a nightmare, this is not the role. If it sounds like the interesting problem, keep reading.
You own the technical roadmap. Architect, build, and ship, from 0 to 1. You are not implementing someone else's spec. You work directly on product strategy, architecture, and customer validation, and you grow into the CTO seat as we scale and hire.
We can teach the mechanical engineering domain. We cannot teach the interest in learning it.
- Roughly 10 focused hours a week to start, going full time when funding closes.
- US-based and able to relocate. Remote and hybrid flexible now, with New York or San Francisco likely as we scale.
- Onboarding within one to three months.