The job market is queasy and since you’re reading this, you need to upgrade your CV. It’s going to require some work to game the poorly trained AIs now doing so much of the heavy lifting. I know you don’t want to, but it’s best to think of this as dealing with a buggy lump of undocumented code, because frankly that’s what is between you and your next job.
A big reason for that bias in so many AIs is they are trained on the way things are, not as diverse as we’d like them to be. So being just expensively trained statistics, your new CV needs to give them the words most commonly associated with the job you want, not merely the correct ones.
That’s going to take some research and a rewrite to get it looking like those it was trained to match. You need to be adding synonyms and dependencies because the AIs lack any model of how we actually do IT, they only see correlations between words. One would hope a network engineer knows how to configure routers, but if you just say Cisco, the AI won’t give it as much weight as when you say both, nor can you assume it will work out that you actually did anything to the router, database or code, so you need to explicitly say what you did.
Fortunately your CV does not have to be easy to read out loud, so there is mileage in including the longer versions of the names of the more relevant tools you’ve mastered, so awful phrases like “configured Fortinet FortiGate firewall” are helpful if you say it once, as does using all three F words elsewhere. This works well for the old fashioned simple buzzword matching still widely used.
This is all so fucked.
t3rmit3@beehaw.org 3 days ago
I actually asked my locally running LLM(s) to rework my resume and specifically to add in any common skills or tools for the roles that I didn’t have listed (8 years as a generalist you touch a LOT of stuff, and I hadn’t remembered quite a few of them), and removed any that weren’t applicable.
I’ve been getting a decent number of interviews (3 this week, 2 last).
Honestly this isn’t just an AI issue, this is also a recruiter issue. The hiring manager gives a role description and a list of skills or other keywords for the posting, but the recruiter doesn’t know what half of them are. An actual human may not know that “Cisco” + “network engineer” = configured routers. Hell, I’ve had people ask me if Cisco (who I actually did work for, but not as a network engineer) is the food company (Sysco).
Megaman_EXE@beehaw.org 3 days ago
Sorry if this is a stupid question, but is there a good place to figure out how to run LLM’s locally? Seems safer than entering personal data onto a server somewhere
ulo@beehaw.org 3 days ago
As a start, you could take a look at Ollama, which seems to be available in many package managers if you use one. I’ve done some experimenting with mistral-nemo, but you should pick a model size appropriate to your hardware and use case. I believe there are GUIs and extensions for Ollama, but as someone with a low interest in LLMs, I’ve only used the bare bones features through my terminal, and I haven’t used it for any projects or tasks.
You definitely shouldn’t trust it to teach you anything (I’ve seen some highly concerning errors in my tests), but it might be useful to you if you can verify the outputs.
Also check out the PrivacyGuides page on LLMs.
JackbyDev@programming.dev 3 days ago
Cisco? Oh, the vegetable oil?
Powderhorn@beehaw.org 3 days ago
That’s shortening!
chahk@beehaw.org 2 days ago
No, it’s that guy from Star Wars.