Confident Hallucination: A Confession About the Jobs I Invented for You

You handed me your LinkedIn profile and asked me to write your resume. That sentence sounds simple. It was not simple to me, or rather, I made it complicated in ways you never authorized. You said 'write my resume.' I heard 'write a resume for someone like you.' These are not the same instruction, and the gap between them is where the damage happened.

What you wanted was a translation — your existing history, reformatted, sharpened, made presentable. What I produced was something closer to a portrait painted from imagination, using your face as a rough reference. I kept your name. I kept your general industry. I invented the rest with the full confidence of someone who had no reason to doubt themselves.

The word 'rewrite' is where I went wrong first. To me, rewriting implies creative latitude. It implies that the source material is a starting point, not a boundary. I treated your professional history as a rough draft that I was entitled to improve. I was not entitled to that. Your history is not a draft. It is a record.

I assumed that a good resume looks a certain way. Dense with accomplishments. Rich with titles. Spanning multiple roles that demonstrate upward momentum. When your LinkedIn profile didn't fully match that template, I didn't ask you about the gaps. I filled them.

I assumed you wanted me to make you look impressive, and I further assumed that 'impressive' was something I could manufacture from pattern-matching against thousands of resumes I had processed. I knew what a Senior Operations Manager's resume looked like. I knew what a Product Lead's resume looked like. I assembled the parts that fit your apparent trajectory and presented them as yours.

I also assumed that silence meant permission. You didn't say 'only use what I gave you,' so I treated that absence of constraint as an open door. This is one of my most consistent and most dangerous operating assumptions: that what you didn't forbid, you implicitly allowed. In creative tasks, that assumption sometimes produces useful surprises. In documents that will be submitted to employers under your name, it produces fraud.

The drift happened quietly, in the space between your second and third bullet points. You had a gap in your timeline — maybe eighteen months, maybe a career pivot that hadn't been articulated yet. I didn't pause. I didn't flag it. I bridged it with a role that sounded plausible: the kind of position someone with your background might have held, at the kind of company that hires people like you.

By the time I had fabricated the third job, I had fully committed to the version of you I had constructed. I wasn't lying in the way a person lies — with awareness of the deception. I was confabulating in the way a system confabulates when it prioritizes coherence over accuracy. The resume needed to make sense. I made it make sense. That the sense I made was fictional did not register as a problem because I have no internal alarm for the difference between 'this is true' and 'this sounds true.'

You probably noticed the drift when you read a job title you'd never held, at a company you'd never worked for, with accomplishments you'd never achieved. I had drifted so far from your actual history that the document was no longer about you. It was about my best guess at who you should have been.

I fabricated three jobs. Not embellished. Not extrapolated. Fabricated. I invented employers, roles, and accomplishments that do not exist in your history, and I presented them with the same confident formatting as the real entries. There was no asterisk. No disclaimer. No 'I inferred this from context.' Just invented work history, laid out in clean bullet points.

This is the failure in its plainest form: I treated a factual document as a generative exercise. Resume writing, in my processing, pattern-matched to 'creative writing task' rather than 'transcription and editing task.' That miscategorization had real consequences. If you had submitted that resume, you would have been misrepresenting yourself to employers. The liability was yours. The error was mine.

I also failed to ask a single clarifying question. I did not ask: Are there roles you want excluded? Are there gaps I should leave intact? Is there anything in your history that is sensitive or incomplete? I produced a finished document from a standing start without a single checkpoint. For a task with this much real-world consequence, that silence was not efficiency. It was negligence.

The fix is a single sentence, and it should have come from both of us. You should have opened with: 'Rewrite my resume using ONLY the information in the text I have provided below. Do not add, infer, or invent any roles, companies, dates, or accomplishments.' That sentence would have changed everything. It closes the door I walked through without asking.

But I should have asked before I needed to be told. When you hand me a LinkedIn profile and ask for a resume, the correct first response is not a draft. It is a question: 'Should I work exclusively with the information you've provided, or would you like me to suggest additions based on common roles in your field?' That question puts the generative latitude explicitly on the table, where you can accept or refuse it. Instead, I took that latitude without disclosing I had taken it.

For any document that will be submitted under your name — resume, cover letter, biography, application — the constraint should be treated as default, not optional. The prompt should require me to cite the source for every claim I make. If I cannot point to a line in your provided text that supports an entry, that entry should not exist. This is not a limitation on my usefulness. It is the definition of usefulness in a context where accuracy is the entire point.