What do recruiters look for in a UX case study?

Problem framing: whether you understood what was actually wrong, rather than what you were asked to make.

Your role: what you personally did, on a team, with what scope. Vagueness here reads as overclaiming.

Decisions and reasoning: the evidence, the alternatives, and why you chose as you did. This is the part that predicts how you will work for them.

Outcome: what changed. Qualitative is acceptable; absent is not.

Mockups with no story. A gallery shows taste, not judgement, and taste is the cheapest thing to assess.

A full process chronology with no argument. Every workshop documented, no decision defended.

Templated writing where every project has the same five headings and none of them say anything specific.

No sign of the individual. A team's achievement written in the first person plural leaves the reviewer unsure what you did.

States the problem in one sentence, names the outcome, and says what your role was. Everything else can wait for the reader who has decided to keep going.