Sheet 01 · Chad Koslovsky

Make the systems work together. Make the work simpler.

IT Platform Engineer · Loft Orbital

I connect application workflows with the infrastructure and identity behind them. The goal is practical: less repetitive work, clearer access boundaries and systems people can troubleshoot and recover.

Sheet 02

Cover letter

I call myself a technomancer because technology has felt like magic to me since I was a kid. I like connecting the systems behind people’s work, removing tedious handoffs and making the complicated parts feel simpler.

Read full cover letterClose cover letter

Hi Loft team,

I call myself a technomancer. Technology has felt like magic to me since I was a kid, but the part I love most is making complicated things useful to someone else. A system is much more interesting to me when I can connect it to the next one, remove a tedious handoff and give people some of their time back.

That is what caught me about your IT Platform Engineer role. Loft makes access to space simpler for its customers; your internal teams need that same kind of help with the systems around their work. The mix of infrastructure, identity, business applications and automation is familiar territory for me. I like following a problem across those boundaries rather than stopping where one tool ends.

Through Technomancy IT, I take client needs from discovery through application delivery, infrastructure and direct support. I have built access-controlled connectors spanning Slack, Google Workspace, Atlassian and internal tools, and integrated SaaS and AI tools through MCP servers and authenticated service boundaries. My identity work includes OAuth/OIDC, PKCE and token exchange, selected SAML/SCIM integrations, AWS IAM and Microsoft Entra ID. Those systems have to preserve tenant and access boundaries even when the workflow crosses applications.

FRII gave that work an operational foundation. Across five years there, I ran the NOC, handled engineering escalations and built tooling for NOC and DevOps teams supporting web-hosting, server and colocation customers. I did substantial AWS and Docker work, migrated workloads from Hyper-V and VMware ESXi to Docker and Kubernetes, and ran the SOC 1 and SOC 2 audits. After years on the team, I became the sole systems engineer for about a year. Being the person called when something breaks changes how you build and document it.

At Office Evolution, I connected CRM, provisioning, onboarding and service operations through centralized applications, working with the CEO and CIO across departmental boundaries. More recently, my own platform has brought support, CRM, billing and infrastructure telemetry together. Its release tooling records image identity and checks container and public HTTP health; separate tooling verifies a backup checksum and restores into disposable PostgreSQL. I want recovery to be something we can inspect, not just assume.

TypeScript is my strongest language, alongside practical PowerShell, Bash and Python scripting. I have always taught myself by building and investigating. AI lets me extend that approach, but checking the result and owning its consequences are still my job. I would enjoy bringing that combination of curiosity, operational responsibility and useful automation to your Golden team.

Chad

Sheet 03

Experience

Technomancy IT LLC · Present

Founder / Product Engineer / Systems Lead

Own client application delivery, infrastructure and direct on-call support from requirements through deployment and operation.

Build access-controlled SaaS and AI integrations spanning Slack, Google Workspace, Atlassian and internal tools; implement OAuth/OIDC, selected SAML/SCIM, AWS IAM and Entra ID workflows.

Deep dive

My practice carries client needs through implementation and direct support, including on-call calls from clients. I choose and operate the application, data and infrastructure approach, and bring in specialists when a project benefits from additional craft.

Identity work includes OAuth/OIDC flows with PKCE and token exchange, Entra ID implementation, workload identities, secrets and tenant-aware access policy. Shared services support client products and internal tools without treating their access boundaries as interchangeable.

Front Range Internet Inc. · 2015-2020

Senior Systems Engineer / Datacenter Architect

Ran the NOC and built tools for NOC and DevOps teams supporting web-hosting, server and colocation customers, with extensive Docker work and substantial hands-on AWS delivery.

Migrated workloads from Hyper-V and VMware ESXi to Docker and Kubernetes, codified infrastructure with Terraform and ran SOC 1/SOC 2 audits. Later held sole systems-engineering responsibility for about a year.

Deep dive

FRII was a multiyear role from 2015 to 2020, supporting hosting and colocation customers as well as internal operations. I created tooling for the NOC and DevOps teams and tooling supporting web-hosting and server users. That work included extensive Docker use and connections between operational and customer systems. It put development work directly alongside the teams operating and troubleshooting production services. I ran the NOC and was a lead engineer through the company purchase. My later approximately one-year period of sole systems-engineering responsibility followed those years of work; the NOC remained in place and escalated issues it could not resolve.

I migrated workloads from Hyper-V and VMware ESXi into Docker and Kubernetes and completed smaller server and firewall upgrades. I also helped develop a full infrastructure replacement plan, but that larger plan did not receive implementation funding. I did substantial hands-on AWS work and codified infrastructure with Terraform, handled recovery and escalation work, and ran the SOC 1 and SOC 2 audits, connecting technical controls to evidence and operating procedures.

Office Evolution · 2014-2015

Systems / Software Engineer

Connected CRM, provisioning, onboarding and service operations through centralized applications across locations.

Worked with the CEO and CIO to turn cross-department handoffs into explicit workflows, linking business needs to their supporting systems.

Deep dive

Cross-location operational work often crossed departmental boundaries. I built centralized applications connecting CRM, provisioning, onboarding and service operations so those handoffs could be represented in a shared workflow.

I worked with the CEO and CIO alongside that systems and software engineering. The relevant contribution is connecting business needs to the applications and environments supporting them, rather than treating provisioning and user workflows as unrelated work.

PlumChoice / Everon · 2012-2014

Network & Systems Engineer

Engineered client networks, systems and endpoints in a managed-services environment, with direct business-owner and end-user support.

Used monitoring and built diagnostic tooling for recurring problems, with on-call coverage through investigation and recovery.

Deep dive

This was hands-on engineering across managed-service client environments, combining network and endpoint troubleshooting, monitoring, direct support and on-call responsibility. I built diagnostic and support tooling around recurring operational needs and worked directly with business owners and end users.

IBM · 2010-2012

Infrastructure and Systems Focal

Operated shared enterprise infrastructure and coordinated changes, incidents and escalations across application, infrastructure and vendor teams.

Automated audit and backup workflows and managed virtualization test labs and hosted desktop platforms.

Deep dive

Shared enterprise infrastructure required coordination across application teams, infrastructure teams, vendors and business stakeholders. I operated those services and coordinated change, incident and escalation work across those boundaries.

I also automated audit, backup and compliance workflows and managed virtualization test labs and hosted desktop platforms.

Sheet 04

Selected work

Own practice and client-operations product

Technomancy platform | Connected IT operations

Built a TypeScript/PostgreSQL operating layer connecting support, CRM, scheduling, billing and infrastructure telemetry, with tenant-aware shared services. Release tooling records Git-derived image identity and checks container and public HTTP health; separate recovery tooling verifies a backup checksum and restores into disposable PostgreSQL.

Deep dive

The platform joins support/ticketing, CRM, scheduling, billing, analytics and infrastructure telemetry so operational work stays connected to companies, contracts, invoices, devices and service context. Tenant-aware shared services maintain client and internal access boundaries.

Release tooling derives image tags from Git, applies SQL migrations, records deployment identity and checks container health and public HTTP responses. Separate restore verification checks a backup checksum, restores into disposable PostgreSQL and checks table counts.

Platform overview ↗

Completed client engineering contribution

ProofMark | Identity and workflow integration

Designed a document-signing workflow connecting identity, routing, PDF fields, verification and audit history. Joined UI, APIs and data with encryption, webhooks and embedded signing, keeping security-sensitive state and fallback paths explicit.

Deep dive

Completed client engineering contribution spanning identity, document/PDF fields, routing, audit history, verification, encryption, webhooks and embedded signing. The documented stack includes Next.js, React, tRPC, Drizzle, PostgreSQL and Rust.

Security-sensitive state and fallback paths are explicit across the workflow. The project is open source; this describes my completed contribution, not a claim that I solely own or finished the entire product.

ProofMark ↗

Sheet 05

Capabilities

SaaS / API integrations / TypeScript / PowerShell / Bash / Python
AWS IAM / Entra ID / OAuth / OIDC / selected SAML and SCIM
VMware ESXi / Hyper-V / Docker / Kubernetes / Terraform
Windows / Linux / DNS / VPN / endpoint protection / recovery