Principal Experience Architect

Responsibilities

• Ecosystem and information architecture
• Own and evolve the end-to-end product interaction model and related information architecture across Khan Academy's products—navigation systems, permission and role models, and the vocabulary we use to describe things. Ensure new features extend this architecture rather than fragment it.
• Cross-product experience design: Map and design the journeys that span multiple products and user roles (student, teacher, parent, district admin), identifying where handoffs break down, where mental models conflict, and where consolidation or simplification would meaningfully improve the experience.
• Systems thinking and pattern-setting
• Build and maintain the artifacts that make the ecosystem legible to the rest of the org—experience maps, service blueprints, experience architecture diagrams, and design patterns—so that product teams can make locally good decisions that also add up to a coherent whole.
• Strategic advisory and design leadership
• Act as a senior voice on the
• Design Leadership Team, weighing in on major product decisions with an eye toward long-term coherence and scalability.
• Partner with design managers, PMs and technical architects to ensure architectural decisions are grounded in real user and district needs.
• Governance without gatekeeping

Languages