Chad Koslovsky Milliken, Colorado ยท chad@koslovsky.xyz View my resume and work: https://horizon3.koslovsky.xyz Senior IT Engineer | Horizon3.ai Cover letter Hi Horizon3.ai team, I call myself a technomancer. Technology has felt like magic to me since I was a kid, and I still get excited when I can turn something complicated into something people can simply use. Your Senior IT Engineer role caught my attention because it treats automation as something someone has to own, not just build and walk away from. The handoff, the alerts, the failed run and the person waiting for access are all part of the job. That is very familiar territory for me. At FRII, I ran the NOC, built tooling for operators and hosting customers, and handled the escalations that came through when the first line could not resolve an issue. I also ran web services and handled billing-system development and replacement. After several years there, I became the sole systems engineer for about a year during the ownership transition. Keeping services working, documenting the process and helping the next person understand it mattered just as much as making the change. At Office Evolution, I built applications connecting CRM, provisioning, onboarding and service operations across locations. Through Technomancy IT, I have carried that into client systems with authenticated integrations, tenant-aware access and ongoing support. NuPrice is a good example: I built and operated the application, its automated pricing decisions, billing and support, rather than handing off the interesting part and leaving someone else to keep it running. TypeScript is my strongest application language, alongside systems scripting in Bash, PowerShell and Python. I would bring that engineering foundation to your automation stack while learning its particular tools. I also use AI extensively in my engineering work, but I still own the decisions and have to check that the result does what people need. What I like about Horizon3.ai's find, fix and verify approach is that last step. A change is not finished just because it ran successfully; the workflow and the access it depends on still need to work. I would enjoy bringing that same care to the systems your own team relies on, making the complicated parts feel a little simpler. Chad