Skip to résumé

Sheet 01 · Chad Koslovsky

From sitting with a client to shipping the whole thing

Founding Full Stack Software Engineer, Consulting · OpenAI

Technical founder and full-stack engineer who works directly with clients to turn unfamiliar workflows into software people can use. Owns discovery, interfaces, APIs, integrations and production support. Builds AI-assisted features alongside explicit permissions, review steps and audit history.

Sheet 02

Cover letter

I build with clients, from the first messy workflow to the software they can use and the systems they can depend on.

Read full cover letterClose cover letter

I call myself a technomancer. I’ve been talking to computers my whole life, and now they talk back. That still kind of blows my mind. When I was a kid, getting a computer to do something I’d imagined felt like magic. Now I can sit down with a half-formed idea and go a lot further with it than I could on my own. I want to work on the technology that made that possible.

I also think some of the engineering work AI displaces will move into research. When it gets easier to build things, the hard part becomes knowing what’s worth building, what to test, and when a result is actually good enough to trust. That feels like a really good place to put the human brain. It’s the part of engineering I’ve always liked most anyway: pulling a system apart until I understand why it behaves the way it does.

At Technomancy IT, I built ticketing and CRM tools for a construction client after learning how they actually worked. I also ran the IT those tools depended on, so I got to see where my ideas held up and where they didn’t. That’s what caught my eye about OpenAI’s Consulting team. I’d get to sit with the people doing the work, build something they can try on a real engagement, and find out what it gets right or wrong. I’d love to do that with the same technology that changed how I work.

Sheet 03

Experience

Technomancy IT LLC · Present

Founder / Product Engineer / Systems Lead

Turned a construction client’s day-to-day workflow into ticketing and CRM tools, then supported the systems they depended on. Built React and TypeScript applications across UI, APIs and data, including tenant-aware support and billing services with integrations and explicit access boundaries.

Deep dive

For a construction client, I learned how they handled work before building the tools. The ticketing and CRM systems fit inside day-to-day operations rather than requiring the client to fit an off-the-shelf process. In my own practice, the support platform connects tickets with companies, devices, contracts and billing. I built tenant-aware services and integrations and stayed responsible for delivery and support.

Front Range Internet Inc. · 2015-2020

Senior Systems Engineer / Datacenter Architect

Led NOC operations and handled senior engineering escalations for internet and hosting services; built practical diagnostic tools for staff and customers. Modernized workloads with Docker and Kubernetes and owned SOC 1 and SOC 2 audit work, including recovery verification and evidence.

Deep dive

I ran the NOC and handled escalations the frontline team could not resolve. After several years at FRII, I held sole systems-engineering responsibility for about one year while the NOC continued its frontline coverage. I built tools that made diagnosis repeatable and helped turn operational controls into evidence that other people could review.

Office Evolution · 2014-2015

Systems / Software Engineer

Built shared applications connecting CRM, provisioning, onboarding and service handoffs across locations. Worked with the CEO and CIO on operational needs.

Deep dive

CRM, provisioning, onboarding and service requests had to pass between teams and locations. I worked directly with leadership and built shared systems that made those handoffs explicit.

PlumChoice / Everon · 2012-2014

Network & Systems Engineer

Supported managed client networks and systems, built repeatable diagnostics and worked directly with customers through incident recovery.

Deep dive

I worked with business owners and end users on managed client networks and systems. Monitoring and repeatable diagnostic tools helped us work through recurring failures. The employer used Network Engineer as the title.

IBM · 2010-2012

Infrastructure and Systems Focal

Coordinated changes and incidents, automated audit and backup workflows, and built a separate backup tool used by executives and other staff to reduce licensing costs. Wrote Perl, Bash, VBA and PHP scripts.

Deep dive

My work covered shared infrastructure, access, operational changes and escalations. I built automation for audit and backup workflows and separately built an internal backup tool for executives and staff to avoid licensing costs.

Sheet 04

Selected work

Completed client delivery

Velatis: client research workspace

Delivered a private workspace connecting notes, deterministic chart tools, sharing and context-aware AI. Built across the interface, services and identity flows so the product could handle private work and user-controlled sharing.

Deep dive

The work brought notes, interactive charts, identity, sharing and AI assistance together. I treated deterministic chart results and AI assistance as different kinds of information, and kept ownership and sharing rules explicit. My client delivery is complete; the public website is the product overview, not a test of the private workspace.

Velatis website ↗

Completed client contribution

ProofMark: document-signing workflows

Designed signing workflows across React, Next.js, tRPC and PostgreSQL, joining document routing, identity and audit history. Made security-sensitive states and fallbacks explicit so users could see what had happened and what they could do next.

Deep dive

I designed a signing flow where document fields, routing, verification and permissions affect what each participant can do. Audit history and explicit fallback paths mattered because a blocked step has to be understandable. My contribution is complete; the public link is the product site.

ProofMark website ↗

Independent framework project

Kerf: interface and developer tooling

Built an early TypeScript/TSX framework with a compiler, reusable UI, routing and actionable compiler diagnostics. Explored direct DOM updates and shared primitives to make interfaces and their tooling easier to reason about.

Deep dive

Kerf is an early TypeScript and TSX framework I built to explore reusable interfaces, compilers and developer feedback. It is independent work, not a claim of production adoption.

Kerf preview ↗

Sheet 05

Capabilities

  • Development: TypeScript, React, Next.js
  • Data: PostgreSQL
  • Infrastructure: Docker, Kubernetes