Hi AgentSync team,
I call myself a technomancer. Technology has felt like magic to me since I was a kid, and I still get a kick out of taking something complicated and making it feel natural to use. The interface is where that happens for most people. It is also where all the decisions underneath finally have to make sense.
Your posting caught my attention because you are asking for someone to own that whole experience, not just turn a design into components. A new React and TypeScript app, shared packages, a design system and the freedom to work out the UX alongside the code is the kind of responsibility I enjoy. I have spent years moving between frontend design, application logic and the systems that keep the product running. React is familiar territory, but I do not like stopping at the edge of a component when the real problem is somewhere else.
That interest in how interfaces fit together also led me to build my own framework: Kerf, formerly Weft, with its own TSX compiler and the Warp UI toolkit. It is still early, but working on reusable UI contracts, routing and useful diagnostics for coding agents has made me think much harder about the foundations I would normally take for granted. Your shared design system and AI-native way of building are a big part of why this role interests me.
Through Technomancy IT, I take client needs from the first incomplete conversation through the product, deployment and ongoing support. My own platform brings customer records, support, scheduling and billing together in TypeScript, Next.js and PostgreSQL. I have implemented OAuth/OIDC flows and tenant-aware services, so access boundaries are part of how I think about an experience, not something to bolt on after the screen works. I also bring in other specialists when the work benefits from their craft and make sure the pieces hold together.
Proofmark is a useful example of how I approach a complicated workflow. My completed client contribution connected identity, document fields, signing routes, audit history and verification across a React/Next.js interface and its APIs and data. The person signing needs to understand what is happening and what comes next. Keeping the underlying state and fallback paths explicit matters just as much as making the page look good. I see a similar design challenge in your producer onboarding: making the next step clear without hiding the rules that determine whether someone is ready to sell.
NuPrice taught me another side of that ownership. I built and operated the full reseller application for a long-term client, including pricing rules, accounts, subscriptions, billing and support. When you are also helping the people using the software, you learn quickly which decisions actually make their day easier.
I use AI as an extension of my engineering work, including tool-aware workflows, structured outputs and evaluation. I like the direction you describe: make the problem clear enough that another engineer or an agent can carry it forward, then take responsibility for what comes back. My backend strength is Node.js and API-driven systems; my Go and Java exposure is more limited. I would bring the frontend and product ownership you need while learning your service stack properly.
I am based in Milliken, Colorado. I would enjoy helping your team make all that insurance infrastructure feel straightforward for the people who rely on it. When the hard parts are handled well enough that someone can simply get on with their work, that still feels like magic to me. Let’s talk.
Chad