Skip to résumé

Sheet 01 · Chad Koslovsky

Build the services people can depend on.

Sr. Software Engineer - Backend (PST / MST ONLY) · Lively

I connect product requirements to the services, data and operational work behind them. My focus is making boundaries explicit, following problems through the stack and owning what happens after a system is delivered.

Sheet 02

Cover letter

I like the work behind the screen: data, integrations and operational decisions that let an interface make a promise it can actually keep.

Read full cover letterClose cover letter

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

Sheet 03

Experience

Technomancy IT LLC · Present

Founder / Product Engineer / Systems Lead

Own client systems from requirements through TypeScript/Node.js services, data, infrastructure and direct support.

Build OAuth/OIDC authentication, tenant-aware shared services and access-controlled SaaS integrations.

Deep dive

I own the path from incomplete client requirements to a production system: implementation, data, infrastructure and ongoing support. My work includes multi-tenant shared services and tenant-aware identity, policy, observability and support boundaries.

I implement OAuth/OIDC with PKCE and token exchange, selected SAML/SCIM integrations and workload identities. Access-controlled connectors span Slack, Google Workspace, Atlassian and internal tools; AI and SaaS integrations use MCP, mTLS and authenticated service boundaries.

NuPrice | Client engagement within Technomancy IT · 2019-2021

Product Engineering and IT (Long-Term Contract)

Built and operated marketplace-data ingestion, repricing rules, accounts, subscriptions and billing.

Owned analytics, customer support and technical operations across the application and its services.

Deep dive

NuPrice was a long-term client engagement from 2019–2021 that began while I was still at FRII. I built and operated the application, billing, customer support and technical operations.

The product joined marketplace and competitor-data ingestion, user-defined repricing rules, automated price decisions, monitoring, analytics, accounts, subscriptions, CMS and embedded support. This was long-term contracted technical ownership.

Front Range Internet Inc. · 2015-2020

Senior Systems Engineer / Datacenter Architect

Ran the NOC, handled engineering escalations and built tooling for hosting and colocation support teams.

Worked across AWS, Docker and recovery; ran SOC 1/SOC 2 audits and later held sole systems-engineering responsibility for about a year.

Deep dive

At FRII I ran the NOC, handled escalations and built tooling for operations teams supporting hosting, server and colocation customers, including extensive Docker work and connections between operational and customer systems.

I migrated Hyper-V/ESXi workloads into Docker and Kubernetes, completed smaller server/firewall upgrades and helped plan a full replacement that remained unfunded. I did substantial AWS work, codified infrastructure with Terraform and ran SOC 1/SOC 2 audits. My later period of sole systems-engineering responsibility lasted about a year.

Office Evolution · 2014-2015

Systems / Software Engineer

Built centralized applications connecting CRM, provisioning, onboarding and service operations across locations.

Worked with the CEO and CIO to turn business handoffs into shared operational workflows.

Deep dive

Office Evolution needed operational work to connect across departments and locations. I built centralized applications joining CRM, provisioning, onboarding and service operations, turning the handoffs into explicit workflows.

The role included the surrounding architecture across locations and client environments and collaboration with the CEO and CIO. It developed the habit of working through what people need from a shared application before deciding how to implement it.

PlumChoice / Everon · 2012-2014

Network & Systems Engineer

Supported business networks and endpoints directly with owners and end users in managed services.

Built diagnostic tooling, monitored recurring problems and handled on-call troubleshooting and recovery.

Deep dive

At PlumChoice / Everon I engineered and supported client networks, systems and endpoints in a managed-services setting. I used monitoring and repeatable diagnostic tooling, built support tools around recurring needs and communicated directly with business owners and end users.

I also handled on-call issues and worked with antivirus services. Working directly with owners and end users kept the diagnosis connected to the problem they needed resolved.

Sheet 04

Selected work

Own technical practice and client-operations product

Technomancy platform | Connected services and recovery

Joined support, CRM, scheduling and billing through TypeScript/PostgreSQL services with tenant-aware access boundaries. Delivery tooling records Git-derived release identity and checks health; separate tooling verifies PostgreSQL restores.

Deep dive

My own practice platform joins support/ticketing, CRM, scheduling, browser meetings, billing, analytics and infrastructure telemetry. TypeScript, PostgreSQL and container-based delivery connect operational records across companies, contracts, invoices and devices, with tenant-aware shared services preserving access boundaries.

Release tooling derives image tags from Git, applies SQL migrations, records deployment status and image identity, and checks container health and public HTTP responses. Separate recovery tooling checks a backup checksum, restores into disposable PostgreSQL and checks table counts.

Platform overview ↗

Completed client engineering contribution

ProofMark | Identity and document workflow state

Designed signing workflows spanning identity, PDF fields, routing, audit history and integrations. Connected APIs and PostgreSQL with explicit security-sensitive state, verification and fallback paths.

Deep dive

My completed client contribution covered document/PDF fields, signing, identity, routing, audit history, verification, encryption, webhooks and embedded signing. The recorded stack includes Next.js, React, tRPC, Drizzle, PostgreSQL and Rust.

The backend story is explicit security-sensitive state and fallback paths connecting UI, APIs, data and verification. My contribution is completed within this AGPL/open-source client product.

ProofMark ↗

Sheet 05

Capabilities

  • TypeScript / JavaScript / Node.js / API design
  • PostgreSQL / relational data modeling / tenant-aware services
  • OAuth / OIDC / integration boundaries / auditable workflows
  • AWS / Docker / release and restore tooling / production diagnosis