Why Your Environmental Consultant CV Isn't Getting Interviews
Five years in. Real projects behind you. Still getting nothing back.
That gap, between the work you have actually done and the interviews you are actually getting, is not usually a skills gap. It is a visibility gap. The experience is there. The CV is not proving it exists.
This is a different problem to the one graduate CVs have. A graduate CV usually has too little to draw on. A mid-career environmental consultant's CV usually has plenty to draw on and still fails to show it, because the wrong things get foregrounded, and the right things get buried in language that reads as junior.
The tell that ages a CV by five years
There is one word that does more damage to a mid-career environmental CV than any other: "supported."
Supported the EIA process. Supported the ecology team. Supported delivery of the assessment. Every one of those sentences could have been written by someone six months into their first job or someone six years into a career leading chapters. The reader cannot tell which, and when they cannot tell, they assume the more junior reading, because that is the safer assumption for them to make.
At three to eight years, the reader is not checking whether you were present on a project. They are checking whether you owned a piece of it. Authored an EIA chapter, not supported the EIA. Led a survey programme, not assisted with surveys. Advised a client directly, not liaised with the client team. The difference between those pairs of phrases is the difference between a CV that reads as still developing and one that reads as already capable of running things.
What the reader is actually checking for at this stage
A junior CV gets checked for potential. A mid-career CV gets checked for delivery. That is the single biggest shift in what "good" looks like, and most consultants keep writing the CV that worked for their first job for years after it has stopped being the right document.
Specifically, a reader at this stage is looking for four things. Named project types you have delivered end to end, not just touched. Direct regulatory or client-facing experience, since that signals you can be put in front of people without supervision. Chartership status or active progress toward it, since a professional body's own assessment of your seniority is a signal the reader does not have to make themselves. And scale, whether that is project value, site size, or the complexity of the consenting route, since scale is one of the few objective proxies for seniority a CV can offer.
Chartership is doing more work on your CV than you think
CIEEM (the Chartered Institute of Ecology and Environmental Management) offers Chartered Ecologist status, assessed against active practice, ongoing CPD, and self-assessed competence at "Proficient" or "Authoritative" level on the institute's own competency framework, not a fixed number of years. Chartered Environmentalist status, available through CIEEM, IEMA and several other bodies under the Society for the Environment, is aimed explicitly at practitioners "leading teams, advising governments and working as hands-on practitioners." IEMA, distinct from CIEEM and focused on EIA and environmental management rather than ecology specifically, runs its own path to CEnv.
None of this is a suggestion to chase letters after your name for their own sake. It is a note on what those letters do for a reader scanning a CV in under a minute: they answer the seniority question instantly, without the reader having to infer it from your project list. If you are chartered, or actively working toward it, that status needs to sit near the top of the CV, not buried in a professional memberships line at the bottom. If you are not yet chartered, the CV needs to do that seniority-signalling work some other way, through named project ownership and named regulatory engagement, because the shortcut isn't available to you yet.
The evidence that actually proves seniority
Take a real, common piece of mid-career experience: contributing to an Environmental Statement chapter on a nationally significant project.
Weak, reads as junior regardless of actual seniority: "Supported the preparation of environmental statement chapters for a major infrastructure project."
This tells the reader nothing about scope, ownership, or the complexity of the consenting route. It could describe six months of formatting tables or eighteen months of leading a discipline chapter.
Stronger, proves ownership: "Authored the marine ecology and coastal processes chapter of the Environmental Statement for a Development Consent Order application, including direct engagement with the Marine Management Organisation and Natural England on mitigation requirements."
The second version names the document type, the consenting route, the specific regulators, and the specific piece of authorship. A reader does not need to ask a follow-up question to know what this person is capable of doing again.
The pattern generalises past EIA. Wherever your CV currently says "supported," "assisted," or "involved in," ask whether a more specific verb, one that names what you actually owned, would be true. If it would, use it. If it would not, that is useful information too: it tells you where the real gap in your experience sits, rather than papering over it with vaguer language.
What this is not
This is not a licence to inflate your role on a project you genuinely supported rather than led. Claiming authorship of a chapter you did not write, or naming a regulatory relationship you did not personally hold, is a fast way to fail an interview the moment someone asks a specific follow-up question. The fix here is precision about what actually happened, not embellishment of what didn't.
It is also not a claim that mid-career consultants are being formally screened out by any single mechanical filter. It is an observation, from a project-resourcing vantage point rather than a formal hiring one, of a consistent pattern: CVs that read as junior get treated as junior, whatever the reality of the work behind them, because the reader has no other information to go on in the time they actually spend reading.
Mid-career environmental CV checklist
Search your CV for "supported," "assisted," and "involved in." Replace each with the specific verb for what you actually did, where that is true.
Name the consenting route or project type explicitly (Development Consent Order, EIA Regulations, marine licence) rather than describing the project only in general terms.
Name the specific regulator or client body you engaged with directly, not just "the regulator" or "the client."
Put chartership status, or active progress toward it, near the top of the CV, not in a memberships line at the end.
Check that project scale, value, site size, or consenting complexity is visible somewhere in the description, since scale is one of the few objective seniority signals a CV can carry.
Never claim ownership of work you did not personally lead. Precision, not inflation, is the fix.
FAQ
Why isn't my environmental consultant CV getting interviews despite years of real project experience?
Most commonly, the CV describes the work using language that reads as junior, "supported," "assisted," "involved in", regardless of how senior the actual role was. A reader scanning quickly assumes the more junior reading unless the CV proves otherwise with named ownership, named regulators, and named project scale.
Does chartership (CEcol, CEnv) actually make a difference to interview rates?
It doesn't guarantee anything, but it does remove work from the reader. Chartership status is a professional body's own assessment of your seniority, so a reader can register it instantly rather than having to infer seniority from a project list. If you're chartered or close to it, that status should be visible near the top of your CV, not buried at the bottom.
What's the difference between CIEEM and IEMA chartership?
CIEEM (Chartered Institute of Ecology and Environmental Management) is ecology-focused and offers Chartered Ecologist and Chartered Environmentalist routes. IEMA (Institute of Environmental Management and Assessment) is focused on EIA and environmental management and offers its own path to Chartered Environmentalist. They are separate bodies assessing different scopes of practice, and a CV should be precise about which one applies.
How do I describe project work without exaggerating my actual role?
Name exactly what you did, not what the project achieved. "Authored the marine ecology chapter" is precise if you wrote it. "Contributed to the marine ecology chapter" is precise if you contributed without leading it. The fix for a junior-sounding CV is specificity about real ownership, never inflation of a role you didn't hold.
Is it worth naming the specific regulator or client I worked with?
Yes, where you can do so accurately and without breaching confidentiality. Naming a specific regulatory body signals a level of direct responsibility that a generic reference to "the regulator" does not.
At what career stage should my CV language actually change?
There's no fixed year count, since it depends on the seniority of the work itself, not tenure. The more useful test is whether you have started owning discrete pieces of delivery, authoring documents, leading engagement, running a survey programme, rather than contributing to work led by someone else. Once that's true, the CV language needs to catch up to it.
Real delivery, described like it was potential rather than proof. That's the gap between the work and the interviews.
Run your CV through the free Technical Invisibility assessment. Three minutes, no cost, and it will show you exactly where the language is underselling the seniority of what you've actually done.