Skip to résumé

Sheet 01 · Chad Koslovsky

Platform EngineerKubernetes, Cloud & AI Workloads

Platform Engineer, AI Infrastructure · Focused

I build and run the infrastructure around the work: Kubernetes migrations, container releases, access-controlled AI integrations and the recovery steps teams need when things break. I’ve worked at the handoff between operating environments and developers, including a client data science team building a radar-sensing product.

Sheet 02

Cover letter

I’m a self-taught engineer. Much of what I learned about running infrastructure came from being the person who got called when it broke.

Read full cover letterClose cover letter

Hi Focused team,

I’m a self-taught engineer. Much of what I learned about running infrastructure came from being the person who got called when it broke. What interests me about this role is the chance to build the Kubernetes foundation and then work alongside client teams as they put real AI workloads on it. A platform is useful when those engineers can deploy to it, see what happened when something fails, and fix the next issue without waiting for the original builder.

At Front Range Internet, I migrated hosted workloads from Hyper-V and VMware ESXi into Docker and Kubernetes. I ran the NOC, handled escalations and owned recovery verification. I also built tooling for the operations team and hosting customers. The work taught me to care about the less visible pieces of a migration: how people recognize a bad release, where they look for answers, and what they need to bring a service back.

At Technomancy IT, I’ve worked on Azure client environments and Entra ID, with deeper hands-on cloud work in AWS. I built a release workflow for our operations platform that ties container images to Git, applies database migrations and checks both the container and the public HTTP endpoint. I built a separate restore-verification tool so a backup is something we can test, not just a file we assume we can use.

A long-term client brought me closer to the ML side. I handled full-stack engineering and DevOps setup and support alongside data scientists and ML engineers building a contactless radar sensor. My work was the software and delivery environment around their work, not developing the model. More recently I’ve built access-controlled MCP and SaaS integrations. I think about what a tool can see and what it’s allowed to do before I think about making it more autonomous.

TypeScript and shell automation are my strongest programming tools; my Python experience is scripting and supporting Python-using teams. I’d bring production Kubernetes, client-facing operations and AI integration work to the team while building deeper hands-on experience with AKS, GKE and Terraform. I’d like to pair with your senior platform engineer on those pieces and help client developers build something they can keep running after we leave.

Thanks, Chad Koslovsky

Sheet 03

Experience

Technomancy IT LLC · 2015-Present

Founder / Product Engineer / Systems Lead

Build and operate tenant-aware services for client software and internal workflows. Set access boundaries with OAuth/OIDC and build access-controlled MCP integrations for AI and SaaS tools.

Build container release workflows with Git-derived image tags, database migrations and service health checks. Provide hands-on cloud and production support to clients.

Deep dive

When a client team needs a shared service, I work from its access boundaries through release and support. I use OAuth/OIDC for application and API authentication and implement scoped access for tenant-aware services. MCP connectors bring AI tools into SaaS workflows without treating access to one service as permission to use another.

Front Range Internet Inc. · 2015-2020

Senior Systems Engineer / Datacenter Architect

Migrated hosted workloads from Hyper-V and VMware ESXi into Docker and Kubernetes. Built tooling for NOC and DevOps teams and hosting and colocation customers.

Led the NOC, owned escalations and recovery verification, and translated operational controls into procedures and SOC 1/SOC 2 audit evidence.

Deep dive

I migrated workloads into Docker and Kubernetes rather than replacing hypervisors in place. I also built tooling for the NOC, DevOps teams and hosting customers. Operators handled first-line coverage, and I handled their escalations, verified recovery and kept engineering procedures usable. During a later period of about one year I took sole systems-engineering responsibility, with first-line NOC coverage still in place.

Office Evolution · 2014-2015

Systems / Software Engineer

Built shared SQL and MongoDB applications joining CRM, provisioning, onboarding and support across office locations. Implemented VLAN-based segmentation and per-office access and bandwidth settings.

Deep dive

I built shared tooling to connect handoffs between CRM, company provisioning and office support. I also built a Linux-based routing device that placed each customer office on its own VLAN, mapped Wi-Fi users to the right office network and let staff provision access and bandwidth per office.

PlumChoice / Everon · 2012-2014

Network & Systems Engineer

Engineered and troubleshot networks and endpoints for managed-service clients. Built recurring diagnostics and handled on-call escalations directly with businesses.

Deep dive

At a managed-services practice, I diagnosed recurring network and endpoint problems across customer environments. Monitoring, diagnostic tooling and on-call support were part of the work. I communicated directly with business owners and end users so they could understand what changed and what needed follow-up.

IBM · 2010-2012

Infrastructure and Systems Focal

Supported shared enterprise infrastructure and hosted desktop platforms. Automated audit and backup work and coordinated changes with application, infrastructure and vendor teams.

Deep dive

I worked across application, infrastructure, vendor and business teams on changes and escalations. I supported virtualization labs and hosted desktop platforms and automated audit and backup tasks. I built an internal backup tool used by executives and others, without inferring a specific scale of adoption or savings.

Sheet 04

Selected work

Long-term client engagement

Radar-sensing R&D · ML team delivery

Handled full-stack engineering and DevOps setup and support alongside data science and ML engineers developing a contactless radar sensor. Owned the software and delivery environment scope, not model development or device firmware.

Deep dive

A long-running client engagement put me alongside data scientists and ML engineers developing a contactless radar sensor. I owned full-stack delivery and DevOps setup and support on the software side so the team had an environment for its work. That was platform support for an ML team, not evidence that I designed the model, built the sensor firmware or administered managed GPU clusters.

Practice-owned product and operational tooling

Technomancy IT · Client operations platform

Built a TypeScript, Next.js and PostgreSQL platform tying together support, records and infrastructure telemetry. Its Docker release tooling tags images from Git, applies SQL migrations and checks container and HTTP health. Built a separate restore-verification tool.

Deep dive

The platform joins client records, support activity and infrastructure telemetry while keeping tenant boundaries in place. Its Docker delivery script tags image versions from Git, applies database migrations, records deployment state and checks container and HTTP health. A separate script verifies the backup checksum, restores into a disposable PostgreSQL instance and checks table counts. Those are capabilities of the tooling, not a guarantee that every run used every check.

Platform overview ↗

Sheet 05

Capabilities

  • Kubernetes · Docker · workload migration
  • Azure · Microsoft Entra ID · AWS IAM
  • CI/CD · deployment health checks · restore verification
  • Production monitoring · runbooks · escalations
  • TypeScript · Bash · Python scripting · MCP / LLM APIs