Skip to résumé

Sheet 01 · Chad Koslovsky

Full StackTypeScript, React and PostgreSQL

Senior Full Stack Engineer · GridUnity

I build full-stack tools for workflows where people need to understand what the data says, who can act on it, and what changed. My work spans React, TypeScript, APIs and PostgreSQL, with a background running production systems and building tools for the people who support them.

Sheet 02

Cover letter

The part of interconnection that caught my attention is the handoff. A developer needs to know what’s missing from an application, a utility needs a defensible record of its review, and an operator needs to see what changed without piecing together emails.

Read full cover letterClose cover letter

Hi GridUnity team,

The part of interconnection that caught my attention is the handoff. A developer needs to know what’s missing from an application, a utility needs a defensible record of its review, and an operator needs to see what changed without piecing together emails. I like building software that makes those steps easier to follow without hiding the underlying rules.

At NuPrice, I built and ran a marketplace repricing product for a long-term client. Merchants could define the rules, see what the system was doing with competitor data, and check the resulting prices. I also owned subscriptions and customer support, which meant I had to be able to explain what the software was doing when a customer needed help. In my completed work on Proofmark, I used React, Next.js, tRPC and PostgreSQL to connect document preparation, identity, signing and audit history. What mattered there was that the interface and the underlying record agreed about what had happened and what could happen next.

I bring an operator’s perspective to that work. At Front Range Internet, I ran the NOC and built diagnostics so the next engineer on call had somewhere better to start than a blank terminal. At Technomancy IT, I’ve carried that into client delivery: work out the data and access boundaries early, make supportable choices, and stay close to what happens after release. I like sharing the reasoning behind a design, especially when a teammate will be the one debugging it later.

I’d like to bring that mix of product engineering and production ownership to GridUnity. I’d be especially interested in how your team models a review as it moves across organizations, where the workflow needs to be configurable and where everyone needs a consistent record to trust.

Chad Koslovsky

Sheet 03

Experience

Technomancy IT LLC · Present

Founder / Product Engineer / Systems Lead

Own client software delivery from discovery and architecture through deployment and on-call support. Build React and TypeScript applications, typed APIs and tenant-aware shared services with clear identity and access boundaries.

Translate client workflows into product decisions and work directly with clients and technical collaborators on delivery and operational handoffs.

Deep dive

I own client application work from discovery through design, implementation, deployment and support. Across product and shared-service work, I connect what a user needs to do with what the API and underlying data should allow.

I implement OAuth/OIDC, PKCE and token exchange as part of application and API authentication. I build tenant-aware shared services with distinct access and support boundaries for client products and internal tooling. I work with clients directly and bring in specialists when a project needs them.

NuPrice · long-term client · 2019-2021

Application, billing, support and IT (Contract)

Owned the application, billing, support and IT for a long-term client engagement that began alongside FRII during the transition to longer-term independent client work.

Deep dive

NuPrice was a long-term client engagement from 2019 to 2021, beginning while I was still at FRII. I built and operated the reseller application and owned its billing, customer support and technical operations.

The application brought marketplace and competitor data into user-defined repricing rules and automated price decisions, with monitoring and analytics alongside accounts, subscriptions, a CMS and embedded support. That sustained responsibility meant following issues from the customer-facing workflow through the application and its operation. The product was acquired; my role was the client’s technical delivery, not ownership of the company.

Front Range Internet Inc. · 2015-2020

Senior Systems Engineer / Datacenter Architect

Ran NOC operations and owned senior engineering escalations. Built diagnostics and operator tooling used by NOC, DevOps, hosting and colocation teams.

Replaced the billing system and ran PHP and JavaScript web services and hosting. Migrated workloads from Hyper-V and VMware ESXi to Docker and Kubernetes, with responsibility for recovery verification.

Deep dive

At FRII, I ran the NOC and took sole systems engineering responsibility for approximately a year during an ownership transition. The NOC continued first-line coverage and escalated engineering issues to me. I built operator diagnostics for recurring issues that affected NOC and DevOps teams, as well as web-hosting and colocation customers.

I also ran PHP and JavaScript web services and replaced the billing system. Infrastructure work included moving workloads from Hyper-V and VMware ESXi to Docker and Kubernetes, with responsibility for monitoring, recovery checks and escalation.

Office Evolution · 2014-2015

Systems / Software Engineer

Built centralized applications connecting CRM, provisioning, onboarding and service operations across locations. Turned handoffs between teams into explicit application workflows.

Deep dive

Office Evolution’s operational work crossed departments and locations. I built centralized applications connecting CRM, provisioning, onboarding and service operations so those handoffs were represented in shared systems.

The role combined software with the architecture around it: learning how people needed to work together, translating the handoffs into explicit workflows and supporting the surrounding systems across locations and client environments. I worked with the CEO and CIO as part of that delivery.

PlumChoice / Everon · 2012-2014

Network & Systems Engineer

Engineered SMB networks and endpoints, built diagnostic tools and handled on-call issues directly with clients.

Deep dive

At PlumChoice / Everon, I worked as a network and systems engineer across managed-service clients, supporting networks and endpoints and communicating directly with business owners and end users. The work required diagnosing a problem in its business context rather than stopping at a single device.

I used monitoring and diagnostic tooling, built support tools around recurring operational needs, and handled on-call issues. Working across client environments developed the practical troubleshooting and communication I still bring to software delivery and production support.

IBM · 2010-2012

Infrastructure and Systems Focal

Supported enterprise infrastructure, automated audit/backup workflows and coordinated cross-team changes.

Deep dive

At IBM, I was the infrastructure and systems focal for shared enterprise environments. The work crossed application, infrastructure, vendor and business teams, with incidents and changes requiring coordinated ownership rather than isolated fixes.

I automated audit and backup workflows, managed virtualization test labs and hosted desktop platforms, and supported access, change and escalation work around shared infrastructure. That experience established an operating perspective that complements my later full-stack product work.

Sheet 04

Selected work

Completed client contribution

Proofmark | Full-stack signing workflows

Completed a client contribution across React/Next.js, tRPC and PostgreSQL, linking document preparation and signing states to identity, verification and audit history.

Deep dive

I completed client engineering work on a signing workflow that needed to stay consistent from the editor through the audit record. I worked across React and Next.js, tRPC APIs, and Drizzle/PostgreSQL to connect document fields, identity and signing paths to verification.

The project is a concrete example of making sensitive workflow states and fallback paths explicit in both the interface and the underlying data, without treating either as the only record of what happened.

Proofmark product website ↗

Long-term client engagement · 2019–2021

NuPrice | Marketplace repricing

Built and operated marketplace repricing software that combined competitor-data ingestion, merchant-defined pricing rules and reporting. Owned billing, monitoring and customer support.

Deep dive

From 2019 to 2021, I built and operated a pricing tool for a long-term client. It took marketplace and competitor data into customer-defined pricing rules, automated price decisions and gave resellers monitoring and analytics alongside their accounts and subscriptions.

Owning billing, support and the application together meant tracing problems from what a merchant saw to the rule or workflow behind it. The engagement began while I was at FRII; I owned the technical delivery, not the client company.

Sheet 05

Capabilities

  • TypeScript, React, Next.js and Node.js
  • Typed APIs, REST and PostgreSQL
  • Workflow automation, data modeling and audit trails
  • Multi-tenant services and identity controls
  • Production observability, incident response and release support