Hi LendingTree team,
I call myself a technomancer. Technology has felt like magic to me since I was a kid, and I still love the moment when something complicated becomes useful to someone else. That is what draws me to your Insurance engineering team: helping people compare their options depends on the less visible work of keeping applications, data and service handoffs dependable.
Your posting gives as much attention to supporting existing software as it does to building new features. That feels familiar. Through Technomancy IT, I take client needs from an unfinished idea into a working system and stay involved in the product, infrastructure and support behind it. I enjoy understanding why a process works the way it does before deciding which parts to change.
ProofMark is one example of that work. I completed a client engineering contribution to its document-signing workflow, connecting identity, PDF fields, recipient routing, audit history and integrations. The work crossed React interfaces, typed APIs and PostgreSQL data, with webhooks and embedded signing joining the surrounding workflow. Keeping security-sensitive state and fallback paths explicit mattered because a signing screen is only useful when the record behind it makes sense.
For my own practice, I have built a client-operations platform with TypeScript, Next.js and PostgreSQL. It connects support tickets with companies, contracts, invoices, devices and infrastructure context, while tenant-aware services preserve access boundaries. I also built delivery and restore-verification tooling: deployment scripts record image identity, apply migrations and check service health, and a separate workflow restores backups into a disposable database. Those are practical tools for understanding a release and investigating what happened afterward.
I am also building Kerf, an early-development TypeScript/TSX framework with its own compiler and full-stack routing, authentication and data architecture, alongside its UI tools. Its direct page updates and actionable compiler diagnostics reflect my interest in making UI code easier to reason about, including when coding agents help write it. I use AI heavily in my engineering work, but the design decisions and the responsibility for the result remain mine. Kerf is a separate framework from React; my longstanding React experience is part of my application work, including ProofMark.
Earlier, at Office Evolution, I connected CRM, onboarding, provisioning and service operations through centralized applications, working across departments and with the CEO and CIO. At Front Range Internet Inc., I ran the NOC, handled production escalations and migrated workloads from Hyper-V and ESXi into Docker and Kubernetes. Those roles taught me to connect a technical decision with the people who will operate and depend on it.
My strongest application experience is in TypeScript, React, Node.js and PostgreSQL. My C# and .NET exposure is limited, and I would need to learn your ASP.NET and SQL Server conventions. I appreciate that your team welcomes comparable experience and values the judgment to work carefully in an established codebase. I would bring that approach, curiosity about the Insurance business, and a willingness to make tradeoffs clear early.
I am based in Milliken, Colorado, and would welcome a conversation about the Denver team and the applications you are evolving. Thank you for taking the time to get to know my work.
Chad