Hi Lively team,
I call myself a technomancer. Technology has felt like magic to me since I was a kid, and I still get excited when it makes something difficult feel natural. Frontend work is where that becomes visible: someone can understand a choice, finish a task and get on with their day. Lively caught my attention because those moments involve money people may need for care, as well as savings they are building for the future. A clear interface matters a great deal when someone is deciding what they can spend or move into investments.
I spent time with your HSA and investment pages, especially the way Lively brings cash, transfers and the Schwab and Devenir options into one dashboard. The engineering challenge I see is keeping a connected experience understandable while the systems behind it have different responsibilities. I enjoy that meeting point between interface design and the rest of a product. I have long worked with React and TypeScript, but I have also stayed responsible for APIs, data, deployment and the people who need help when something goes wrong.
ProofMark is a completed client engineering contribution that reflects how I approach sensitive workflows. I designed the signing flow across identity, document and PDF fields, routing, audit history and verification, with explicit handling of security-sensitive state and fallback paths. React and Next.js were part of a stack that also included tRPC, Drizzle, PostgreSQL and Rust. The work joined the interface to the underlying document record rather than treating signing as an isolated screen. I would bring that care for state and handoffs to Lively's account and investment experiences, while learning the details of your financial partners and benefits domain.
At NuPrice, a long-term client engagement from 2019 to 2021, I built and operated the application that brought marketplace and competitor data into user-defined repricing rules and automated price decisions. Accounts, subscriptions, billing, analytics and embedded support were part of the same product responsibility. Supporting customers kept me close to the consequences of a confusing workflow or an integration problem. That experience is one reason your emphasis on both product feedback and production troubleshooting appeals to me: I like following a problem through to the person using the result.
I am also building Kerf, an early-development TypeScript/TSX framework with its own compiler and its UI toolkit. Working on reusable UI contracts, routing, authentication, data and actionable diagnostics for coding agents gives me room to think carefully about how an interface is put together and how another engineer will work on it. It is an independent framework, separate from my React work, and still developing. I use AI extensively in my engineering and creative work, and I remain responsible for understanding and checking what I ship.
My earlier systems work gives me another useful perspective. At Front Range Internet, I ran the NOC, handled escalations and ran the SOC 1 and SOC 2 audits. I worked with the CEO and CIO through an engineering tenure that included a company purchase and, later, about a year with sole systems-engineering responsibility while the NOC continued first-line support. I learned to make changes with the operating system and the people around it in mind. That habit still shapes how I investigate failures and communicate with a client or teammate.
I would enjoy bringing that mix of frontend craft and sustained responsibility to Lively. I am based in Milliken, Colorado, in Mountain time, and would welcome a conversation about where your investment experience needs the most attention. Helping people feel confident using something important is work I would be glad to do with your team.
Chad