
There's a moment in writing I've always paid attention to.
When something looks finished, but you know it's not. When the sentence works, technically, but doesn't quite carry the weight it should. And you sit with it a little longer, change one word, and suddenly it holds.
That instinct has shaped how I approach this work.
Most recently, I was a Senior Content Designer at Meta working on AI-driven experiences across Facebook Reels. Before that, I spent 4+ years at PayPal and Venmo designing for payments, crypto, and onboarding—trust-heavy systems where language has to earn confidence quickly and clearly.
Over time, my work shifted from writing individual strings to designing the systems behind them — how language scales, how AI interprets intent, and how products communicate uncertainty, trust, and action at massive scale.
I still care deeply about good writing. Tone. Rhythm. The difference between something technically correct and something that actually feels human. But increasingly, I'm interested in the architecture underneath it all: the workflows, principles, and decision-making systems that shape communication before a single sentence is ever written.
AI didn't replace the work I do. It raised the bar for what content designers need to be—less copywriter, more systems thinker. That's where I've been heading anyway.
Content designers are spending less time writing every individual string, and more time designing the systems, principles, and AI workflows behind them.
But lately, I've been thinking about how much this work is changing.
Are any of us truly writing anymore? It's a question I've been sitting with.
What used to feel like a linear process, choosing a word, replacing it, feeling the weight of it, now feels more like orchestration. We're shaping language through systems, structuring chaos into something usable, scalable, and coherent.
The instinct is still the same: finding the wording that helps someone trust, understand, act, or feel something clearly.
As AI takes on more of the surface-level execution, the value of content design shifts into orchestration. Less about crafting a single sentence. More about designing the system that produces it: how intent is defined, how context flows, and how meaning stays consistent across an experience.
I spend less time polishing language in isolation and more time designing the conditions around it. I think about how content is generated, how it adapts, and how it holds up across different states, surfaces, and edge cases.
My focus is on building shared understanding. Guiding decisions. Helping teams align on what users actually need to know, not just what we want to say.
Clarity is no longer just a writing problem.
It is an orchestration problem.
And that is the work I am most interested in now. Not just writing what shows up, but designing how meaning is created, governed, and scaled.
Ready to see the work?
The proof is in the projects.