Hi Elevations team,
I call myself a technomancer. Technology has felt like magic to me since I was a kid, and I still enjoy making complicated systems useful to people. In infrastructure, that often means giving someone an ordinary day: they can sign in, reach the tools they need and trust that someone has thought about what happens when a system fails.
Elevations caught my attention because that work serves people close to home. Your member-owned approach and emphasis on helping people make informed financial decisions give the engineering a clear purpose. Your digital banking services connect everyday account activity with secure messages and member support. Keeping the underlying environment dependable matters to both the member trying to get something done and the employee helping them.
The Senior Cloud Engineer role brings together the responsibilities I like carrying: building the environment, understanding the applications that depend on it and staying involved when something goes wrong. At Front Range Internet Inc., I ran the NOC, handled engineering escalations and was a lead engineer through a company purchase. Later, I held sole systems-engineering responsibility for about a year, with the NOC continuing to provide first-line coverage. Being the escalation point taught me to make the technical investigation and the next step clear to everyone involved.
I also migrated workloads from Hyper-V and VMware ESXi into Docker and Kubernetes, upgraded server and firewall infrastructure, and worked on monitoring and recovery verification. I ran FRII's SOC 1 and SOC 2 audits, connecting technical controls with operating procedures and evidence an auditor could follow. I would bring that habit of making controls part of day-to-day engineering while learning Elevations' particular financial-services requirements with your Information Security team.
Through Technomancy IT, I have kept the application and infrastructure sides of that work connected. I have used Azure in systems jobs and client engagements and implemented Entra ID identity and application integration workflows. Terraform, PowerShell and Python are also part of my systems background. In my own client-operations platform, I built deployment tooling around Git-derived image tags, SQL migrations, deployment records and health checks. A separate backup-inspection workflow checks a checksum, restores into disposable PostgreSQL and checks table counts. I care about being able to explain what was deployed and how recovery can be examined.
The same attention to follow-through helped Excell Services LLC in Wray, a significant client of my practice. I rebuilt legacy servers and employee computers, upgraded the network and helped connect a satellite location with VPN, Windows Server and Active Directory. Investigating the surrounding network costs also secured a one-time $15,000 refund from CenturyLink. Good infrastructure work includes understanding the services the business is paying for, as well as the equipment and access people rely on.
My completed client contribution to ProofMark adds another useful perspective: designing a document-signing workflow that joins identity, document fields, routing, verification and audit history, with explicit handling of security-sensitive states and fallback paths. It is application engineering that helps me ask better questions about the infrastructure and access boundaries a service needs. Across that work and earlier enterprise and managed-services roles, I have enjoyed being the person who can work through a problem with both the technical team and the people affected by it.
I'm based in Milliken and would welcome a conversation with your Broomfield team about the Azure environment, its recovery priorities and the improvements you want this engineer to carry forward. I would be glad to bring hands-on operational ownership, curiosity and clear communication to the systems behind your members' everyday banking.
Chad