How to Describe a Job You Hated Without It Showing

Almost everyone has one: the job that was badly managed, badly paid, or just wrong for you. The problem isn't that you had it. The problem is that when you try to write about it on your CV, either the resentment leaks through, or you swing the other way and write something so vague it looks like you're hiding something.

Neither works. A recruiter reading your CV doesn't need to know the job was miserable. They need to know what you did there, and whether it's relevant to the role they're hiring for. Those are separate questions, and separating them is the whole trick.

Strip the emotion, keep the facts

Go back to what actually happened, not how it felt. "My manager never gave feedback and the team was constantly reshuffled" becomes, on the page, "Operated with a high degree of autonomy across shifting team structures." That's not spin — it's the same event, described from the outside rather than the inside.

This isn't about disguising a bad job as a good one. It's about writing your CV the way you'd describe the job to someone who never worked there and doesn't care about the politics — just what got done.

Find the parts that were real, even if small

Even a genuinely bad job usually has something in it worth naming: a process you improved, a task you took on that wasn't in your job description, a period you covered for someone. You're not required to represent the whole job equally. You're allowed to lead with the part that's useful and let the rest sit quietly underneath.

• A short stint can be described by its output, not its duration — what shipped, what was fixed, what was handled
• Bad management often means you did more unsupervised than your title suggests — that's worth stating plainly
• If the role taught you what you don't want next, that's a legitimate answer in an interview, just not on the CV itself

The CV doesn't need your opinion of the job. It needs a plain account of what you did in it.

Watch for the tells that give it away

Bitterness shows up in specific patterns: unusually short bullet points for a role that lasted over a year, a job title with no description at all, or language that's oddly defensive ("despite limited support..."). Recruiters read hundreds of CVs and recognise a gap in enthusiasm even when they can't name it. The fix is simple — treat the bad job with the same neutral, achievement-first structure as every other role. Same verbs, same format, same level of detail.

Save the honest version for the interview

If you're asked directly why you left, you don't have to pretend it was fine. A calm, brief, forward-looking answer works far better than a diplomatic non-answer: what wasn't working, what you learned about what you need from a role, and what you're looking for now. That's a different conversation from the CV, and it's one you're allowed to have honestly, without turning it into a complaint.

The CV's job is to get you the interview. The interview is where nuance and tone belong — not the other way round.

FixMyCV reads the job description alongside your existing CV, flags where a role's wording sounds thinner or more defensive than the rest, and rewrites it in plain, achievement-led terms — without inventing anything you didn't actually do.