Set direction
Turn an ambiguous goal into boundaries, sequencing, standards, and decisions a team can build against.
About
I’m John Dean, known online as Flick.
I’m a Principal Architect at GIPHY and a hands-on systems engineer. I turn emerging platforms into production systems that teams can ship, operate, and improve.
The throughline is production engineering.
I began in developer tools at Metrowerks and continued through Motorola, Freescale, Nokia, Accenture, and Time Warner Cable—often through acquisitions, spin-offs, technology transfers, or client relationships rather than conventional job changes.
I later spent two substantial chapters at Shutterstock. Between them, I left deliberately to work in games at Sandbox VR and enterprise MLOps at Verta. I returned after the PicMonkey acquisition, helped deliver Shutterstock Create and Shutterstock’s first AI image-editing tool, and moved to GIPHY as a Principal Architect in 2024.
Principal-level problems rarely respect a repository boundary. I work across product, frontend, backend, APIs, infrastructure, and operations, and I stay close enough to critical code paths to test whether the design is honest.
My AI work is applied systems engineering, not model research: agent orchestration, tool use, identity and access, durable state, product surfaces, evaluation artifacts, deployment, and the runtime around the model.
Career arc
Several generations of computing, one engineering practice.
- 01
Developer tools + embedded
Metrowerks, Motorola, Freescale, and Nokia: IDEs, SDKs, CI, automated testing, native toolchains, and constrained hardware.
- 02
Television + mobile
Accenture and Time Warner Cable: embedded HTML5 television products, native iOS systems, performance work, releases, and beta support.
- 03
Creative + multiplayer products
Two Shutterstock chapters around browser creative tools, with Sandbox VR in between for games, scheduling, payments, and live operations.
- 04
MLOps + internet-scale media
Product and frontend leadership at Verta, followed by Principal architecture across GIPHY’s consumer, monetization, partner, and platform systems.
- 05
Independent systems
Open-source, onchain infrastructure, and The House: current hands-on work across identity, permissions, agents, multiplayer runtime, and operations.
How I lead
Make the direction clear. Keep the feedback loop honest.
Review the real system
Challenge hidden assumptions in designs and validate critical paths in code when that is the fastest route to truth.
Own the operating consequences
Treat reliability, migrations, observability, incident learning, delivery, and cost as inputs rather than cleanup.
Make other engineers faster
Mentor, unblock, and create useful paved roads without becoming a human approval queue.