IT Analyst (IT-02) · Polar Knowledge Canada
I help small teams, research and field organizations, public-sector groups, and operations-heavy teams turn messy workflows, unreliable technical environments, and scattered information into systems people can actually use.
I work in a remote federal research environment where systems reliability matters, operational constraints are real, and technical fixes have to hold up outside ideal conditions.
My technical judgment comes from an unusual mix: current work as an IT Analyst (IT-02), following a Computing and Data Technician role, with responsibility for computing, data, computer-lab, and network systems at the Canadian High Arctic Research Station — plus years of hands-on experimentation with Linux, home labs, IoT devices, smart-home automation, 3D printing, and practical electronics builds.
As an IT Analyst (IT-02), previously a Computing and Data Technician, at Polar Knowledge Canada, I work in the practical middle ground between research operations, data systems, user support, lab computing, and network reliability at a remote Arctic facility.
Outside work, I have used Linux as a daily driver for nearly a decade and keep sharpening my skills through home labbing, OpenWRT and home networking, virtual machines, DIY smart-home devices, IoT builds, CAD, and 3D printing.
My strongest work is connecting the pieces: understanding the workflow, designing the interface, structuring the data, setting up the network or device layer, prototyping physical parts/enclosures when needed, and leaving the system understandable for the people who rely on it.
I fit best where technical systems, operational reality, and scientific or field-facing environments overlap — especially when the work sits between infrastructure, applications, troubleshooting, and information flow.
Most of my best work sits between infrastructure, applications, users, and operational reality — where the system has to work cleanly in practice, not just on paper.
Clean up messy operational processes by building or improving forms, intake systems, approvals, structured records, and practical business workflows.
Example proof: research intake and scientific database portal work built around structured forms, usable interfaces, workflow testing, and reporting-ready data.
Support Linux systems, lab and workstation environments, network access, remote graphics, and the day-to-day technical reliability work that people depend on.
Example proof: Linux lab configuration work, VirtualGL/ThinLinc/Nvidia troubleshooting, Linux server support for researchers, and hands-on network reliability support in remote operating environments.
Build or support practical small systems that combine sensors, devices, connectivity, light automation, and physical prototyping.
Example proof: IoT prototypes, monitoring-oriented device work, and electronics builds where network, software, and physical design all need to fit together.
Turn raw records, scattered tables, and informal data into usable structures with validation, naming discipline, and future reporting paths.
Deploy and maintain VPS-hosted workflows, automation helpers, and agent-style systems when they solve a concrete operational problem.
Write clear materials, test the workflow, and help non-technical users understand what changed and how to use it well.
The strongest fit is usually one of these four engagement types.
Forms, approvals, intake flows, operational applications, and process cleanup tied to structured data.
Linux systems, workstation/lab environments, network and VPN troubleshooting, and day-to-day technical reliability work.
Technical support where research operations, information structure, reporting needs, and practical computing meet.
Small systems that combine devices, sensors, connectivity, light automation, and physical prototyping.
My strongest work is practical systems, workflow, infrastructure, and technical-operations work where more than one layer needs attention. For large-scale enterprise architecture, advanced production machine learning, or highly specialized network engineering, I contribute most effectively as part of a broader team.
Figure out what is broken or inefficient, clean up the process, test the solution, and make sure the result works for the people who have to live with it.
Tools matter most when they are tied to a real operating problem. This toolkit is grouped the same way I tend to use it in practice.
For forms, portals, intake systems, structured records, workflow cleanup, and practical internal tools.
For Linux systems, lab environments, remote graphics, hosted workflows, and hands-on troubleshooting.
For reliable connectivity, segmentation, VPN access, and operational network support.
For connected-device builds, light automation, monitoring, and the physical details that make prototypes usable.
Thompson Rivers University
Major in Physics; Minor in Computer Science
September 2018 – August 2023
Service-management foundation supporting practical, user-aware IT, operations, and technical support.
Contact
I am most interested in consulting conversations where the need is concrete and the work has to function in the real world. Send a brief description of the problem, the current setup, and what a useful outcome would look like.