Chad Koslovsky Milliken, Colorado · chad@koslovsky.xyz View my resume and work: https://openapproach.koslovsky.xyz Senior Systems Engineer (L5) – Colorado | Open Approach Cover letter Hi Open Approach team, I call myself a technomancer. Technology has felt like magic to me since I was a kid, and I still love figuring out how it works. These days, a lot of that magic is making a complicated system feel simple for the person who depends on it. Your Senior Systems Engineer role caught my attention because you want someone who can design the solution, build it and stay accountable to the client. I liked reading how you brought Champlain Valley Equipment’s separate locations together without making employees relearn their working day. That is the kind of practical engineering I care about: understand the business first, then make the technology fit. FRII is where much of that judgment was tested. I worked there for years before the company purchase, ran the NOC and was a lead engineer through the transition. When the senior engineer above me left, I was trusted with sole systems-engineering responsibility for about a year. The NOC handled first-line calls, and the problems they couldn’t resolve came to me. Alongside that responsibility, I migrated workloads from Hyper-V and ESXi into Docker and Kubernetes, made smaller server and firewall upgrades, and ran our SOC 1 and SOC 2 audits. Sometimes keeping things running meant repairing aging server hardware when replacement wasn’t an option. Through Technomancy IT, I have also been the person a business calls for the whole problem. For Excell in Wray, I rebuilt legacy servers and employee computers, upgraded the network, and implemented Windows Server, Active Directory and VPN connectivity for corporate users and a satellite location. I also found wasted carrier costs and helped recover $15,000. The job wasn’t just installing newer equipment. It was understanding what people needed, making the changes and being there afterward. Everon gave me hands-on MSP experience across client networks and endpoints; IBM taught me the discipline of shared infrastructure, change coordination and working across teams. I’m comfortable moving between that enterprise discipline and a conversation with a business owner who just needs things to work. AWS is my more hands-on cloud platform, and I have over five years of Azure work across client engagements, along with Microsoft systems setup and support. I’ve always taught myself by building, breaking things down and following the problem until I understand it. AI now extends that habit, but it doesn’t replace the judgment or responsibility. I still want to know why a change works and what happens if it doesn’t. I’m based in Milliken, and I’d love to bring that curiosity and ownership to your Fort Collins team. Making the difficult parts work quietly in the background is still my favorite kind of magic. Chad