Skip to résumé

Sheet 01 · Chad Koslovsky

I build interfaces for the people who run the system

Senior Software Engineer – Frontend-Focused Full-Stack (Remote) · Hypori

Your Console is where administrators turn secure mobile access into something their teams can actually use. I build React and TypeScript software for that kind of work: clear actions, visible boundaries, and enough context to recover when something goes wrong.

Sheet 02

Cover letter

Why Hypori

Read full cover letterClose cover letter

What drew me to Hypori is that the Console is where the privacy promise becomes an everyday job for someone. A group or tenant admin needs to know what they are changing, who it affects, and what to do if it fails. That's the kind of interface I enjoy building.

At Office Evolution, I built a front-desk Wi-Fi support tool and the provisioning behind it. Each customer office had its own VLAN, and individual Wi-Fi accounts had to land on the right network. The hard part wasn't putting a reset button on a page. It was giving receptionists enough control to solve a real problem without asking them to think like network engineers. That experience still shapes how I design administrative interfaces.

More recently, I designed the React and Next.js document workflow for ProofMark, from PDF fields and recipient routing through signing and verification. I worked across the interface, typed APIs and data so the steps and fallback paths made sense to the person using them. I've also been on the other side of that work, running NOC escalations at Front Range Internet and building diagnostics for the people who inherit a problem after it reaches production.

I like to keep the account scope and the status of an action visible at the point where an operator commits a change. I'd like to bring both perspectives to Hypori: making the Console easy to extend for the engineers who build it and easy to reason about for the people trusted to run it. I'd start by listening to the admins and support staff who know where the current workflows slow down, then trace those issues from the UI to the service before deciding what to change.

Chad Koslovsky

Sheet 03

Experience

Technomancy IT LLC · Present

Founder / Product Engineer / Systems Lead

Own technical delivery and production support for client applications and internal operations tools. Built React and TypeScript interfaces and a Next.js/PostgreSQL support platform that connected tickets, devices, contracts and billing while keeping customer access tenant-scoped.

Deep dive

Support work forced me to think through the boundary behind each screen: which account it belongs to, what the operator can see, and how to find the affected records without losing context. I implemented OAuth/OIDC in application and API authentication flows, and built and supported client products from the interface through their service and data layers.

Front Range Internet Inc. · 2015-2020

Senior Systems Engineer / Datacenter Architect

Led NOC operations and engineering escalations for a web hosting and colocation provider. Maintained PHP and JavaScript web services, replaced billing software, built customer and operator diagnostics, and migrated workloads to Docker and Kubernetes.

Deep dive

Hosting incidents often looked like a problem in a customer-facing service before the underlying cause was clear. I built diagnostic tools that helped operators narrow it down, while also maintaining the application and infrastructure they depended on.

Office Evolution · 2014-2015

Systems / Software Engineer

Built tools for customer onboarding and operations across a shared-office business. Built a front-desk interface for password resets and Wi-Fi troubleshooting atop a Node.js provisioning workflow and tenant-isolated Linux routing.

Deep dive

Each customer office needed its own VLAN and its own speed, bandwidth and access settings. Individual Wi-Fi accounts mapped to the right office. The front-desk tool kept common support tasks within reach without requiring receptionists to make router configuration changes.

PlumChoice / Everon · 2012-2014

Network & Systems Engineer

Supported client networks, systems and endpoints in a managed service environment. Built recurring-issue diagnostics and worked directly with business owners and end users during troubleshooting.

Deep dive

Working directly with users taught me to make diagnostic steps practical to repeat and to explain what changed without assuming the person calling had my view of the system.

IBM · 2010-2012

Infrastructure and Systems Focal

Coordinated enterprise systems changes, incident escalations and access. Wrote Perl, Bash, VBA and PHP automation and built an internal backup tool used by executives and other staff to reduce licensing costs.

Deep dive

I wrote scripts around the operating work people actually needed to get done and coordinated changes with the teams that depended on the same shared infrastructure.

Sheet 04

Selected work

Completed client contribution

ProofMark | Document signing and verification

Designed a React and Next.js document workflow covering PDF fields, recipient routing, signing and verification, with explicit fallback paths and an audit record.

Deep dive

The key interface decision was to keep document preparation, signing and verification distinct so a user could tell which step they were in and what remained. My work spanned UI, typed APIs and verification, with attention to the state around security-sensitive actions.

ProofMark product website ↗

Employer project · 2014–2015

Office Evolution | Tenant-aware Wi-Fi provisioning

Built a front-desk Wi-Fi support interface and Node.js provisioning behind it. Individual accounts connected to their office VLAN; speed, bandwidth and access were provisioned per office.

Deep dive

The customer office was the boundary in the underlying Linux routing system. The interface gave front-desk staff a place to handle common Wi-Fi tasks while the provisioning layer kept account and network scope tied to the right customer.

Independent project · Early development

Kerf | Frontend framework and compiler

Built a TypeScript/TSX framework and published its app scaffold. Designed component, routing and data conventions and made compiler diagnostics concrete enough for developers to act on.

Deep dive

Kerf is an independent runtime, not React. Working on the compiler and scaffold made me think about what a component API communicates to the next person using it, and how to make bad states easy to diagnose.

Kerf framework preview ↗

Sheet 05

Capabilities

  • Frontend architecture: React, TypeScript, Next.js, reusable components
  • Product interfaces: operator workflows, tenant-aware access, explicit state and recovery
  • Full-stack delivery: Node.js, REST APIs, tRPC, PostgreSQL, OAuth/OIDC
  • Operations: AWS, Docker, Kubernetes workload migration, production troubleshooting