Software engineering

Built with an operator’s perspective

I lead a referral-based technical practice, translating client needs into products and systems I also help operate. React and TypeScript interfaces sit alongside APIs, data, infrastructure and support; the work requires understanding how a customer uses the system as well as how it is built.

Application and API authentication work includes OAuth/OIDC, PKCE and token exchange. Tenant-aware shared services connect client-facing products and internal operations while keeping their access boundaries distinct. I bring in specialists where their craft helps the project and make the system and delivery responsibilities clear to contributors.

NuPrice was a long-term client engagement from 2019 to 2021, beginning while I was still at FRII. I built and operated the reseller application and owned its billing, customer support and technical operations.

The application brought marketplace and competitor data into user-defined repricing rules and automated price decisions, with monitoring and analytics alongside accounts, subscriptions, a CMS and embedded support. That sustained responsibility meant following issues from the customer-facing workflow through the application and its operation. The product was acquired; my role was the client’s technical delivery, not ownership of the company.

At Front Range Internet Inc., I ran the NOC and was a lead engineer through a company purchase. Later, after the senior engineer above me left, I took sole systems-engineering responsibility for approximately a year, with the NOC continuing first-line coverage and escalating issues to me. That was one period within my 2015–2020 tenure, not the whole engagement.

I migrated workloads from Hyper-V and VMware ESXi to Docker and Kubernetes, upgraded server and firewall infrastructure, and owned recovery verification, monitoring, escalations and engineering procedures. Terraform and Ansible supported repeatable infrastructure work. I also ran the SOC 1 and SOC 2 audits and worked with the CEO and CIO while keeping the operating environment supportable through change.

Office Evolution’s operational work crossed departments and locations. I built centralized SQL- and MongoDB-backed applications connecting CRM, provisioning, onboarding and service operations so those handoffs were represented in shared systems.

The role combined software with the architecture around it: learning how people needed to work together, translating the handoffs into explicit workflows and supporting the surrounding systems across locations and client environments. I worked with the CEO and CIO as part of that delivery.

At PlumChoice / Everon, I worked as a network and systems engineer across managed-service clients, supporting networks and endpoints and communicating directly with business owners and end users. The work required diagnosing a problem in its business context rather than stopping at a single device.

I used monitoring and diagnostic tooling, built support tools around recurring operational needs, and handled on-call issues. Working across client environments developed the practical troubleshooting and communication I still bring to software delivery and production support.

Antivirus services were part of the managed-services work. The record does not identify a particular antivirus vendor or an endpoint-agent implementation, so I distinguish operating and supporting these environments from writing a commercial agent.

At IBM, I was the infrastructure and systems focal for shared enterprise environments. The work crossed application, infrastructure, vendor and business teams, with incidents and changes requiring coordinated ownership rather than isolated fixes.

I automated audit and backup workflows, managed virtualization test labs and hosted desktop platforms, and supported access, change and escalation work around shared infrastructure. That experience established an operating perspective that complements my later full-stack product work.