AI-product failure modes to recognize

A generic QA person triages crashes and 500s. Cursor's product breaks in ways that don't throw an exception at all: the diff is just wrong, the context was stale, the model quietly got worse. Naming these classes on sight marks you as a power user who debugs like an engineer.

Expect interview questions on how an AI code editor fails. A memorized taxonomy isn't enough. You need to map a vague report onto a failure class fast, because that class points at the right logs and the right team.