Hi Lively team,
I call myself a technomancer. Technology has felt like magic to me since I was a kid, and I still enjoy figuring out how the pieces fit together. These days, a lot of that work is behind the screen: the data, integrations and operational decisions that let an interface make a promise it can actually keep.
Lively caught my attention because benefits are already complicated enough for the person using them. Integrations, balances and access should feel dependable, not like another system they have to manage. I would enjoy working on the backend that makes that experience possible.
At Technomancy IT, I own the path from an incomplete client need to a working product and its ongoing support. My platform uses TypeScript, PostgreSQL and container-based delivery to connect support, CRM, scheduling, billing and infrastructure telemetry. Tenant-aware services preserve access boundaries while bringing related records into a useful operational context. My identity work includes OAuth/OIDC, PKCE and token exchange, and I build access-controlled integrations with external services.
For NuPrice, a long-term client, I built and operated the application, billing, support and technical operations. It joined marketplace data with user-defined repricing rules, automated decisions, subscriptions and analytics. Being responsible for the whole system meant following a customer problem beyond the first layer where it appeared.
My completed contribution to ProofMark covered document-signing workflows across identity, routing, audit history and integrations. That work brought React interfaces together with APIs, PostgreSQL and explicit security-sensitive state. FRII added years of production troubleshooting, recovery and infrastructure ownership. Today my delivery tooling records release identity and checks container and HTTP health, while separate tooling verifies restores into disposable PostgreSQL.
I’m self-taught and still learn by building, investigating and checking what happens. AI tools extend that process, but they do not replace understanding the behavior or taking responsibility for it. I would bring that curiosity, practical backend ownership and willingness to follow a problem through to your team.
Chad