Architecture Decision Record
Status
accepted
Context
The resume page needed a career history section. The standard approach is employer name, role title, dates, bullet points. I chose to remove employer names and role titles entirely, replacing them with year ranges and narrative descriptions of the work done.
Rationale
Two reasons. First, privacy — I work with enterprise clients and I'm not in a position to publicly associate my observations about AI tooling with my employer or their clients. Second, and more important: employer names are credibility signals that substitute for describing the actual work. Listing a well-known company name gets attention. Describing what you built, what problems you solved, and what you learned forces the work to stand on its own. That's a harder standard to meet but a more honest one. Recruiters who want the full employment history can follow the LinkedIn link — that's the right place for it.
Trade-offs
Employer names do carry weight in hiring contexts. A senior role at a recognisable company signals something to a recruiter quickly. Removing that signal means the writing has to do more work. The year-based narrative only works if the descriptions are specific enough to be credible on their own. If they're vague, the resume looks weaker than a conventional one. The bet is that specificity about the work is more valuable than name recognition of the employer.

The standard resume format puts the employer name first. There's a reason for that — it's a fast credibility signal. Recognisable company, senior role, dates align — the recruiter moves on.

I removed the employer names deliberately.

Part of it is practical. I work in enterprise CCM and I'm not comfortable publicly associating observations about AI tooling with my current employer or the clients I work with. That constraint exists and I'm not pretending it doesn't.

But even without that constraint, I'd have considered this. A resume that leads with employer names is asking you to judge the work by the brand. A resume that leads with what was actually done is asking you to judge the work by the work.

The year-based timeline forces more specific writing. "2016–2021: built and maintained high-volume document composition pipelines for regulated communications, led migrations from print to multi-channel digital output" is more informative than "IT Analyst at [company name]" even though the latter would carry more immediate weight in a hiring context.

The LinkedIn link at the top of the page handles recruiters who need the full picture. The resume page here is for context, not job applications.

← Is it worth building a portfolio nobody reads?
What I learned about AI-assisted development by bu… →