About Me

Interaction Designer · Digital Content & Web

Interaction Designer and front-end web developer at Kubik, a global experiential agency. Five years building CMS-driven content platforms, event websites, and interactive experiences for international brands, from concept through deployment, in close coordination with account, production, and client stakeholders. Based in Waterloo, Ontario.

The scope at Kubik spans Sanity, Contentful, and Strapi CMS platforms, each managing content for different contexts, from national digital signage networks to conference websites serving hundreds of attendees. Work is consistently end-to-end: content strategy, UX, HTML/CSS/JavaScript development, performance analytics, and post-deployment reporting.

Most projects involve coordinating content across multiple stakeholders with distinct requirements, moving quickly between platforms, and maintaining clear documentation so everyone stays aligned.

Outside of work: self-taught guitarist, record collector, concert-goer, and co-op gamer. Reads more nonfiction history than is probably reasonable, particularly stories that didn't make the official record: marginalized histories, cultural edge cases, and the gaps between what happened and what got written down. Museums, markets, and a Magic: The Gathering deck that loses gracefully.


2020, Intern

Kubik

Joined Kubik to help a physical-build agency move digital during COVID lockdowns. Built interactive web apps and managed content for virtual conference and dealership environments.

2021, Junior

Kubik

Designed and managed event websites for Parker Hannifin conferences. Built CMS-driven interactive installations for Michelin in Contentful.

2022 – Present

Kubik

End-to-end ownership of CMS platforms, content delivery pipelines, engagement analytics, and client-facing reporting across concurrent engagements.

Before Kubik, completed interaction design studies at Sheridan College with a focus on web interfaces, accessibility principles, and content systems. The internship was the bridge: a part-time hire to help a physical-build agency establish its digital presence when physical events had stopped entirely.

Five years later, the work spans CMS platform management, website development, analytics reporting, and multi-channel content delivery. The case studies on this site are all from 2026, a cross-section from a much larger body of ongoing client work.


Outside of the case studies on this site, a significant portion of the work involves managing content systems that run quietly in the background: CMS platforms that enable non-technical teams to update content, analytics pipelines that convert engagement data into client-facing reports, and documentation that keeps distributed teams working from the same information.

The goal is always the same: a system where the right people can publish the right content at the right time, with reporting that demonstrates why it mattered. The interactive experience is the surface; the content infrastructure is what makes it repeatable.

CMS platform management

Sanity, Contentful, and Strapi. Editorial workflows, content architecture, and remote publishing pipelines.

Analytics & reporting

Engagement tracking, footfall data, and structured post-event performance reports for client stakeholders.

Web standards & accessibility

HTML/CSS/JavaScript development grounded in Interaction Design principles and mobile-first responsiveness.

Cross-team coordination

Working across account, production, and client teams to align on content requirements, timelines, and delivery.

Most content systems work is ongoing and client-confidential. The pattern: CMS platforms and analytics pipelines built for repeatable deployment across multi-show, multi-market rollouts, structured so a non-technical team can update content and read their own data without opening a code editor.

During the slower summer periods between trade show seasons, the work shifts to the pitch team. Kubik competes for Fortune 500 experiential contracts through competitive RFP responses and speculative proposals, with briefs from brands including BAE Systems and CDK Global.

This is where the "what if" work lives. What if the booth was also a data visualization? What if the touchscreen wasn't a touchscreen? What if the physical and digital environments shared a coherent logic? Pitch contributions span concept development, interaction design, rough prototypes, and the technical narrative of how it would actually be built.

Interpreting the brief

Identifying the interaction opportunity inside the client ask.

Experience flows

What a visitor does, in what sequence, and why.

Concept mocks

Key screens and moments at fidelity appropriate to the stage.

Technical narrative

How it would actually be built, written for a non-technical audience.

Most pitch artifacts are confidential. The sanitized version: the work involves Fortune 500 briefs, experiential environments, and tight deadlines. Several concepts pitched in one year have become the live projects of the next.

AI shows up at every stage of the work, not as a novelty, but as a junior collaborator. It only gets used for tasks already within capability, so mistakes get caught and corrected instead of silently shipped. The model drafts; the human decides.

In practice, that means using AI to generate lifelike people, lighting, and technology interactions inside 3D booth renders during RFP pitches. It means having an AI challenge assumptions on client briefs before committing to a direction. It means Claude Code as a daily coding and debugging partner, Figma MCP transferring designs into responsive code, and provisioning SharePoint sites and Cloudflare deployments through conversational interfaces rather than admin portals. Asana and Notion get the same treatment: AI talks to the planning tools so the planning tools stay current.

As someone with ADHD, AI has been a game changer for digital organization. An Obsidian-based LLM wiki manages project planning, links context across everything in progress, and keeps priorities visible when working memory alone cannot. The productivity gain is real and personal. Not a talking point, a daily dependency.

Junior collaborator, not autopilot

Only augments tasks already understood. Every output gets reviewed, guided, and corrected where needed.

Every stage of the workflow

From RFP concept renders and brief analysis to coding, deployment pipelines, and analytics reporting.

Environmental responsibility

Genuinely concerned about data centre impact. Runs models locally when feasible: ComfyUI, Ollama, local TTS.

Internal education

Champions AI at Kubik where it adds value. Cautions where it doesn't. Educates colleagues on practical use and realistic limits.

The AI landscape changes weekly. Actively tracks new tools and models (GitHub trending, open-source releases, new MCP integrations) and evaluates what's worth adopting versus what's hype. The excitement about what's possible is genuine; so is the skepticism about what's oversold.