John Dean / Flick · Principal Architect

Turning emerging platforms into production systems.

I’m John Dean, known online as Flick. I’m a Principal Architect at GIPHY with 25+ years building and operating systems across developer tools, consumer products, cloud platforms, MLOps, monetization, and AI agents. I stay close enough to the code to know when the architecture is lying.

Principal Architect · GIPHY

Architecture for a platform worth sustaining.

At GIPHY, I lead architecture and implementation across monetization and advertising systems, including multi-partner ad networks and privacy-conscious targeting designed around applicable global regulations. The goal is practical: grow revenue without sacrificing user trust, reliability, or the product people use as a visual language.

01

Build revenue systems

Lead architecture and implementation across multi-partner advertising networks, their subsystems, and sales channels.

02

Protect trust while targeting

Use legally sourced data and treat privacy regulation as a system constraint, not a post-launch disclaimer.

03

Lead reliability and change

Guide migrations, operational improvements, and design reviews inside mature systems that cannot simply stop.

04

Respond to emergent problems

Address incidents, outages, and unexpected product behavior across multiple teams and systems, often under time pressure.

Architectural lens

Production is the truth serum.

Architecture has to survive contact with reliability, cost, permissions, developer experience, product behavior, and the humans operating the system after launch. Elegant boxes are nice; a system that keeps working on Tuesday afternoon is nicer.

01

Production AI systems

Agent identity, orchestration, tool boundaries, permissions, durable state, and the product systems around models.

02

Platforms and distributed systems

APIs, developer tooling, service boundaries, reliability, cost, and systems that teams can operate.

03

Consumer + monetization systems

Architecture that reaches the interface while respecting revenue, experimentation, partner, and customer consequences.

04

Developer experience + operations

Platforms, CI/CD, observability, standards, and paths that let teams ship and operate systems safely.

Selected work

A few systems that explain the range.

View the deeper cut
01

Independent platform · Public

The House / Influence

The House is the platform. Influence is its first production game: persistent agents, multiplayer orchestration, scoped tools, replay, analysis, and operations.

  • Production AI agents
  • MCP + OAuth
  • Event-backed runtime
02

Principal Architect · 2024–Present

GIPHY

Technical direction and hands-on delivery across multi-partner advertising networks, privacy-conscious targeting, search, content delivery, partner, API, reliability, cost, and platform systems.

  • Monetization systems
  • Privacy + trust
  • Reliability + cost
03

Two tenures · November 2015–July 2019 and 2022–2024

Shutterstock Editor → Shutterstock Create

Browser-based creative products, Shutterstock’s first AI image-editing tool, partner integrations, marketplace modernization, cloud migrations, Kubernetes, delivery, and production support.

  • Creative + AI tooling
  • Partner SDK
  • Cloud + operations
04

Enterprise MLOps · 2020–2022

Verta

Employee #6 with end-to-end ownership of everything that touched the browser: React, GraphQL, contractors, releases, enterprise integrations, support, and on-call.

  • Browser ownership
  • GraphQL
  • Delivery + support
05

Archived game modernization

Morpheus

A long-running software-preservation project: a data-driven adventure runtime shipped across browser, desktop, and mobile packaging. Source history survives; the original services do not.

  • Game runtime
  • Cross-platform delivery
  • Preservation
06

CaptEmulation → 0xFlicker

Selected open source

Developer libraries, autonomous game agents, serverless systems, protocol tooling, and smart contracts across two public GitHub chapters.

  • Developer tools
  • Autonomous systems
  • Onchain infrastructure

Career throughline

New platforms. Same job.

I started in embedded systems, moved through mobile, streaming, consumer web, cloud platforms, ML operations, and internet-scale media, and now build AI-agent systems. The recurring work is turning unfamiliar constraints into software people can use and teams can operate.

What’s next

Looking for a hands-on Principal engineer?

I’m based in Colorado and exploring remote Principal and Staff+ engineering roles focused on production AI systems, distributed systems, and technically difficult products.