Chad Koslovsky

Milliken, Colorado · chad@koslovsky.xyz

View my resume and work: https://automox.koslovsky.xyz

Software Engineer - Agent Team | Automox

Cover letter

Hi Automox team,

I call myself a technomancer. Technology has felt like magic to me since I was a kid, and I still enjoy getting underneath a complicated system and making it useful to someone. Sometimes that means building the application. Sometimes it means being the person who gets called when it stops working. A lot of my career has involved both, which is why your Agent Team caught my attention.

I know the people on the other side of endpoint-management software because I have been one of them. At Everon, I engineered and supported business networks and endpoints for managed-service clients, built diagnostic tooling and handled on-call problems directly with owners and users. Antivirus services were part of that work too. When a tool gives an administrator clear information and a dependable way to act, it changes the whole support conversation. I would enjoy bringing that perspective into the software your team builds.

Through Technomancy IT, my work now connects TypeScript applications, APIs, authentication, infrastructure and client support. I build tenant-aware shared services and authenticated integrations, then stay responsible for how they behave in use. The platform I am building around the practice brings support, CRM, scheduling, billing and infrastructure context together. Its release tooling records image identity and deployment status, checks health and public responses, and includes a separate disposable-database restore-verification workflow. I like having something concrete to check rather than assuming a successful build means a working service.

NuPrice was another sustained example. From 2019 to 2021, I built and operated a client's application connecting marketplace data, pricing rules, accounts, subscriptions, billing and support. I handled the technical operations and customer support as well as development. Following a feature from the interface into the data and then into someone's actual problem is work I am comfortable owning. Your expectation that an engineer can deliver the UI half of a backend feature feels natural to me.

My systems background is not separate from that software work. At FRII, I ran the NOC, migrated workloads from Hyper-V and ESXi into Docker and Kubernetes, and handled production escalations. I worked there for years before taking sole systems-engineering responsibility for about a year after a company purchase. That taught me to understand failure modes, keep changes supportable and make the next step clear to the team. Your move toward the team that builds a service also running it is particularly appealing for that reason.

I am also building Kerf, formerly Weft, with its own TSX compiler and the Warp UI toolkit. It is still in development, but it reflects how much I enjoy understanding the tools I use and trying to make them better. I bring a polyglot background rather than claiming Go or Java are my main production languages, and I would be excited to learn your particular agent and event-service architecture with the team.

I am based in Colorado and work well with remote clients and collaborators. The protected time you give service health and learning says something good about how you want to build. I would love to help make endpoint operations feel less complicated for the people depending on them. That is the kind of practical magic I want to keep working on.

Chad