Skip to résumé

Sheet 01 · Chad Koslovsky

Build with AI. Own what it does.

Senior Software Engineer (Full-Stack, AI-Native) · Marvin

I combine full-stack implementation with hands-on operations and AI tooling. My focus is the useful system around the model: clear interfaces, explicit state, connected context and a way to investigate what went wrong.

Sheet 02

Cover letter

AI has expanded what I can build, not changed who is responsible for it. I connect product interfaces, real application context and reviewable workflows.

Read full cover letterClose cover letter

Hi Marvin team,

I call myself a technomancer. Technology has felt like magic to me since I was a kid, and AI has opened up more ways to build with it. What matters to me is still the same: understand what the system is doing, check the result and take responsibility when someone relies on it.

Your distinction between building with AI and building AI into a product feels familiar. I use AI heavily, but I also build the interfaces, connectors and boundaries that make it useful. For Marvin, that work serves people trying to understand their options and find support. A confusing answer or a broken handoff is more than an inconvenient screen.

Through Technomancy IT, I own client products from requirements through React and TypeScript interfaces, APIs, data and ongoing operation. My own platform connects customer and support records through tenant-aware TypeScript/PostgreSQL services. Its graph modeling, indexed retrieval and batch evaluation sit alongside MCP connectors and structured AI outputs. I care about keeping the surrounding application deterministic, with review gates and a traceable path through the workflow.

My completed ProofMark contribution connected signing, identity, document fields, routing and audit history through React, Next.js, APIs and PostgreSQL. Explicit state and fallback paths matter there. I’m also building Kerf, an early TypeScript/TSX framework with its own compiler and UI tools, including actionable diagnostics for people and coding agents. It is a practical way to explore how clearer contracts help both build better software.

That product work grew out of hands-on operating responsibility. At FRII, I set up hosted web services, developed in PHP and JavaScript and handled billing-system development and replacement alongside systems engineering. I ran the NOC and handled escalations too. Shipping something and supporting what happens afterward have never felt like separate jobs.

I’m self-taught and learn by building, questioning and checking. I would bring that curiosity, full-stack ownership and clear-eyed approach to AI to your team, while learning the particular responsibilities of your member experience.

Chad

Sheet 03

Experience

Technomancy IT LLC · Present

Founder / Product Engineer / Systems Lead

Own client products from requirements through React/TypeScript interfaces, APIs, data and ongoing operation.

Build MCP connectors, authenticated integrations and tenant-aware services that keep AI tools connected to real application context.

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 workflows, repricing rules, accounts, subscriptions and billing.

Owned application support and technical operations across a sustained full-stack client engagement.

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

Set up hosted web services, developed in PHP and JavaScript, and handled billing-system development and replacement.

Combined that software work with NOC leadership, engineering escalations, Docker and production recovery.

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.

At FRII I also ran and set up hosted web services, developed in PHP and JavaScript, and handled billing-system development and replacement. This software work sat alongside responsibility for the infrastructure and the customers using it.

Office Evolution · 2014-2015

Systems / Software Engineer

Connected CRM, provisioning, onboarding and service operations through centralized applications.

Worked with the CEO and CIO to turn cross-location business handoffs into shared 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.

Sheet 04

Selected work

Own practice and client-operations product

Technomancy platform | Connected context and AI workflows

Connected customer, support and billing records through tenant-aware TypeScript/PostgreSQL services. Use graph modeling, indexed retrieval and batch evaluation alongside tool integrations and structured workflows.

Deep dive

My own platform connects support/ticketing, CRM, scheduling, browser meetings, billing, analytics and infrastructure telemetry. TypeScript, PostgreSQL and container delivery link company, contract, invoice and device records while tenant-aware shared services preserve client and internal boundaries.

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

Platform overview ↗

Completed client engineering contribution

ProofMark | Explicit document and identity state

Connected signing, identity, document fields, routing and audit history in a completed client contribution. Built React/Next.js, API and PostgreSQL workflows with explicit security-sensitive state 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 useful architectural contribution is explicit security-sensitive state and fallback paths connecting the interface, APIs, data and verification within this AGPL/open-source client product.

ProofMark ↗

Own framework, early development

Kerf | Tools for people and coding agents

Built an early TypeScript/TSX framework with its own compiler, UI tools, routing and data layer. Develop reusable contracts and actionable compiler diagnostics for people and coding agents.

Deep dive

Kerf is my independent TypeScript/TSX framework in early development. It has its own compiler and UI tools, with routing, authentication and data capabilities. The public preview describes small direct DOM/page updates and actionable compiler errors for coding agents.

It expresses my interest in reusable UI contracts, frontend architecture and developer experience. It complements longstanding React experience; it is not a React runtime.

Kerf preview ↗

Sheet 05

Capabilities

  • TypeScript / React / Next.js / Node.js / PostgreSQL
  • MCP connectors / structured AI outputs / retrieval and review gates
  • Identity / typed APIs / document workflows / reusable UI contracts
  • AWS / Docker / delivery checks / production troubleshooting