ABOUT • KHADIJAT (KAH-DEE-JAT) AMOO
I design the decisions, not just the screens.
I'm KD — a product designer in New York working at the intersection of AI experiences, design systems, and behavioral UX. At Amazon I spent three years inside the Shopping Design Org, turning ambiguous, high-traffic problems into patterns that hold up across millions of customers and nine-plus marketplaces.
I studied Computational Media at Georgia Tech — software, cognitive psychology, and human-computer interaction in one degree — which is why I tend to reach for a prototype and a test plan before a mood board.
Former Amazon Designer
Georgia Tech Alum
My philosophy
Design is a liability until it solves a market friction.
Interfaces are overhead. The best products minimize the distance between a user's intent and their outcome. I prioritize architectural clarity over ornament — every pixel earns its place through utility, or it doesn't ship.
Evidence scales better than intuition.
Taste is non-negotiable; direction is not opinion. I build feedback loops in early, using rapid prototypes to invalidate the wrong ideas before engineering picks them up. We design for clarity, but we build for resilience.
Systems are for humans, not for documentation.
A design system is only as good as its adoption. I build tooling that lets engineers move faster without giving up quality — components flexible enough for the edges, rigid enough to hold the brand together.
Ambiguity is the assignment, not the problem.
Difficult product decisions aren't decided by a Figma file. They're decided in the room, where taste, evidence, and business context meet. The design work is often the last mile of a much longer argument.
My design process
Frame the problem before touching a canvas
- I start by writing — a one-pager that states the friction, the customer signal behind it, and what success would actually look like in the data.
- I map the existing experience end-to-end (including the edges everyone avoids) so scope is a decision, not a surprise.
- I pressure-test the framing with product, engineering, and research before committing to a direction.
Fewer meetings, tighter loops
- Weekly design reviews with a standing agenda: what changed, what's blocked, what decision I need from the room.
- Async-first by default — Loom walkthroughs and annotated Figma frames so stakeholders can respond on their own time.
- Working sessions over presentations. I'd rather sketch with two engineers for 30 minutes than present to twelve people for an hour.
Critique is a routing problem
- I separate feedback into three buckets: direction, execution, and preference — and I say out loud which one I'm asking for.
- Every note gets logged with a decision and a rationale, so the same debate doesn't reopen three sprints later.
- Disagreement gets resolved with evidence: a prototype, a usability session, or an experiment — not seniority.
AI as an accelerant, never the author
- Synthesis: clustering research transcripts and review data to surface themes faster, then verifying every theme against the raw source.
- Divergence: generating breadth of concepts and edge-case copy in minutes so the exploration budget goes to judgment, not production.
- Prototyping: building interactive, testable prototypes in code so research participants react to behavior instead of static screens.
- Guardrails: no customer PII in prompts, and no AI output ships without a human accountable for it.
Tools I use
- Figma
- FigJam
- Framer
- Adobe Creative Suite
- HTML/CSS
- React
- Lovable
- Cursor
- UserTesting
- Dovetail
- A/B/n testing
- Usability labs
- ChatGPT
- Claude
- Midjourney
Mini resume
Download full resume ⤓- Led the redesign of Amazon's AI-powered review highlights, improving clarity of sentiment signals and reducing decision friction in high-traffic shopping flows.
- Audited and standardized 20+ fragmented star-rating patterns into a progressive disclosure framework and reusable tokens adopted across PDP, Search, Books, and Devices.
- Launched Homepage components across 9+ international marketplaces, solving RTL, character-length, and regional content edge cases in a configurable system.
- Defined Homepage accessibility standards and resolved a VoiceOver focus-order bug, delivering a WCAG-compliant fix adopted as a company-wide standard.
- Led a student team migrating Georgia Tech's IT website to a modern CMS, improving information architecture, accessibility compliance, and interactivity.
- Built monthly Google Analytics and Tableau dashboards for OIT leadership across three semesters.
- Designed an end-to-end "Split-the-Bill" collaborative payment experience for Amazon Checkout through structured research and high-fidelity prototyping.
- Facilitated a gamified FigJam stakeholder workshop that surfaced recipient-side UX gaps and shaped the final interaction model.
- Designed mobile user education flows for multi-store grocery navigation, simplifying complex store-switching decision points.
- Built Georgia Tech's internal design system from zero to one — component library, documentation site, and interactive tools still in active use across OIT.
Interdisciplinary program spanning software development, user-centered design, and cognitive psychology (HCI). Graduated with honors.
Contact
Have a hard problem that doesn't fit neatly in a brief?
I'm open to product design roles, systems work, and consulting engagements. Tell me what's stuck and I'll tell you honestly whether I'm the right person for it.
