Skip to résumé

Sheet 01 · Chad Koslovsky

Build for the people making things.

Senior Software Engineer · Suite Studios

I enjoy turning technical constraints into tools and experiences people can use. My work combines creative collaboration, full-stack implementation and hands-on responsibility for production systems.

Sheet 02

Cover letter

Creative work and systems work meet in the details: how content is reused, how tools explain themselves and what happens when someone makes the next change.

Read full cover letterClose cover letter

Hi Suite team,

I call myself a technomancer. Technology has felt like magic to me since I was a kid, and art has always been part of that curiosity. I like figuring out how a small amount of code can produce something rich, useful or surprising. The technical constraints are often where the interesting work starts.

Suite’s focus on keeping creative teams in flow caught my attention. I have worked on both sides of that problem: building experiences with artists and designers, and supporting the infrastructure people depend on. Waiting on a system or fighting its handoffs takes attention away from the work someone actually wants to make.

I’m building Kerf, an early TypeScript/TSX framework with its own compiler and UI tools. Clear contracts and useful diagnostics matter to me because they help someone make the next change without having to understand everything at once. I enjoy the design work as much as the implementation: deciding what a tool should make easier, and what complexity it should keep out of someone’s way.

In my completed ProofMark contribution, I connected signing, identity, document fields, routing and audit history through React, Next.js, APIs and PostgreSQL. Explicit state and fallback paths keep the workflow understandable when something does not go to plan. My own client-operations platform applies the same interest in connected context to support, customer records and infrastructure, with separate tooling that checks recovery rather than assuming it works.

My operating background also shapes how I write software. At FRII, I developed PHP and JavaScript web services and handled billing-system development and replacement alongside NOC leadership, Docker and recovery. Through Technomancy IT, I still own client work from incomplete requirements through implementation and support. I want to understand what happens after a feature ships.

I’m self-taught and enjoy learning with other people. I would welcome practicing XP with your team and bringing that mix of creative curiosity, full-stack ownership and hands-on troubleshooting to the problems you are solving.

Chad

Sheet 03

Experience

Technomancy IT LLC · Present

Founder / Product Engineer / Systems Lead

Own client software from requirements through interfaces, APIs, data, delivery and ongoing support.

Work with specialists and client teams to connect application behavior with the systems behind it.

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, through Technomancy IT · 2019–2021

Full Stack Engineer (long-term client)

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

Owned application support and technical operations across a sustained 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 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 ran and set up hosted web services, developed in PHP and JavaScript, and handled billing-system development and replacement alongside systems engineering.

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

Completed client engineering contribution

ProofMark | Explicit workflow state across the stack

Connected signing, identity, document fields, routing and audit history in a completed client contribution. Built React/Next.js, API and PostgreSQL workflows with explicit 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 | Clear contracts for evolving interfaces

Built an early TypeScript/TSX framework with its own compiler, UI tools, routing and data layer. Develop reusable contracts and actionable 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 ↗

Own practice and client-operations product

Technomancy platform | Connected operations and recovery

Connected support, customer records, billing and infrastructure telemetry through tenant-aware services. Delivery tooling records release identity and health; separate tooling verifies PostgreSQL restores.

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 ↗

Sheet 05

Capabilities

  • TypeScript / React / Node.js / PHP and JavaScript
  • Reusable interfaces / APIs / relational data / compiler diagnostics
  • Workflow state / identity / diagnostic tooling / reusable data contracts
  • AWS / Docker / hosted services / production recovery