Cara Lamason
 
TXT
readme.txt
case_studies
About Cara
C
Cara Lamason
STAFF PRODUCT DESIGNER · VERSION 6.0
CurrentlyMeta, AI Search
Looking forPrincipal design roles
SpecialityAI architecture · systems design · high output
Status● Open to opportunities
Case Studies
cara_lamason / case_studies
Favorites
About Cara
Case Studies
Strengths
Process
Connect
Devices
Macintosh HD
NDA Vault
RTF
case_01_intent_search.rtf
RTF
case_02_quality_agent.rtf
RTF
case_03_llm_eval_infra.rtf
NDA
more_work_NDA.rtf
4 items · Double-click to open
strengths.txt
||||||

strengths.txt

Designs AI systems, not just AI features
Architected an intent classification framework (5 intents × 3 contextual lenses × 7 user signals) that dynamically assembles search results for 3B+ users — a composable, systems-level approach that mirrors how LLM products need to be designed: adaptive, signal-aware, built for variance.
Built LLM judge prompts for automated search quality evaluation across 3 workstreams → 16% improvement in issue detection, replacing manual review and demonstrating hands-on fluency with how language models fail.
Operates at the intersection of AI strategy and execution
Contributed to CEO-level deck on AI assistant entry points; authored Search's AI mode strategy (entry points, pathing, cross-surface discovery) — reviewed at VP level.
Led AI 2.0 launch design including full implementation plan and UI variants specifically engineered to mitigate engagement regressions — rare ability to think about AI rollout risk, not just AI potential.
Builds infrastructure others scale from
Created an autonomous AI agent running 24/7 that detects UI bugs, generates code diffs, and conducts internal research — 48+ findings, now scaling org-wide. A principal-level move: solve your team's problem by building a tool the whole org adopts.
Designed a unified component library averaging 3,200 insertions/week across 11 teams; intent taxonomy adopted org-wide.
Drives measurable outcomes at principal scope
+75% global pivot volume · +9.65% content search DAP · +5.9% global search success · +4.6% ad score · 2× private shares — consistent pattern of shipping and moving numbers, not just shipping.
Redesigned a core content discovery experience that performed so well the CEO debuted it publicly; became an app-wide priority for 2025.
Earns trust at the top, builds it across orgs
Secured VP roadmap buy-in by connecting design decisions to company-level priorities. Elevated a P2 initiative to P0/P1 through a cross-functional brief — changed the roadmap through written clarity, not just influence.
V-team design lead across 5+ designers and ~125 projects, aligning 5+ PMs, 4+ eng teams, research, and content design. Team exceeded DAU goals: 6.23% vs. 4.8% target.
Mentors toward promotion, not just performance
Mentored IC5 → IC6 (promoted); developed another IC5 to "greatly exceeds" rating — a consistent pattern that signals genuine investment in others' growth. Table stakes for IC7.
process.txt
||||||

my_design_process.txt

01/
Classify before I wireframe
Every complex problem starts with a framework, not a sketch. I map user intent, behavior patterns, and edge cases into a taxonomy first — so I'm designing for the underlying structure, not the surface.
02/
Design the architecture, not just the experience
I think in systems. Components should compose, patterns should transfer, signals should recombine. I'm designing for the ten teams that will extend this work, not just the one that ships it first.
03/
Evaluate with infrastructure
I build tools to measure my own work — LLM judge prompts, quality rubrics, variant frameworks. Evaluation isn't a phase at the end; it's designed in from the start.
04/
Write to align
Briefs, strategy docs, and executive narratives are design tools. If I can't articulate why a decision matters to the business, I haven't finished the design thinking yet.
05/
Run two tracks
A production track (fast, constrained, ready to ship) and an exploration track (concept work, future-state thinking) run in parallel. Teams shouldn't have to choose between moving fast and thinking big.
06/
Leave infrastructure behind
What does this unlock for the next team? Component libraries, evaluation pipelines, autonomous tooling, briefs that shift roadmaps — good design multiplies beyond its original scope.
New Message
Send
Attach
Photo
To:🏢 ai-company-of-your-dreams.com ×
From:cara.lamason@gmail.com
Subject:Re: Principal Design Role — Let's talk

Hey 👋

I'm a Staff Product Designer (IC6) currently at Meta — where NDA keeps me from showing final screens, but not from showing you how I think.

I'm looking for a Principal role (IC7+) where design is a genuine strategic lever. Especially excited about teams building at the intersection of AI and human experience — where the design problems are genuinely unsolved.

I'd love to chat. Even a 20-minute conversation would be worth your time.

— Cara
cara.lamason@gmail.com · /in/cara-lamason

case_study.rtf
more_work_NDA.rtf
🔒
Protected Content
This file contains additional case studies covered by active NDAs. Available upon request.
Request Access
About Cara
Case Studies
strengths.txt
process.txt
New Message
Trash