Stop Matching the Job Description. Match the Company.
A few weeks ago I read a thread that stuck with me. Recruiters and hiring managers were comparing notes, and a pattern showed up again and again: companies are writing deliberately vague job descriptions.
The JD is a decoy now
Not because they’re lazy. Because everyone now tailors their CV to match every keyword in the posting, perfectly. When every applicant looks like a 100% match on paper, the JD stops being a useful filter. So companies stopped putting the real requirements in it.
The result is a weird game. You optimize your CV against a description that was written to be un-optimizable. You spend an hour tuning bullet points to hit "collaborative," "data-driven," "cross-functional" — words that tell you nothing about what the job actually needs.
The real bar isn’t in the JD
Here’s what the thread made clear. When a JD is vague, the hiring manager isn’t comparing you to the posting. They’re comparing you to the best person already on the team.
The question isn’t "did this candidate match our keywords." It’s "would this candidate fit in next to Sarah, who already does this job brilliantly?" Sarah’s profile — her stack, her way of working, the wins she’s shipped — is the silent acceptance bar. And it’s nowhere in the job description.
That bar is made of things a posting never says out loud:
- the actual technologies the team runs day to day (not the buzzwords in the ad)
- the way the team communicates and makes decisions (the "culture" nobody writes down)
- the recent wins the company is proud of, and the direction it’s clearly heading
If you only read the JD, you’re aiming at a target that was moved on purpose.
Most tools make this worse
Every AI resume builder I’ve seen operates on the old assumption: scrape the JD, match the keywords, ship the CV. That assumption is now broken. A tool that perfectly matches a vague decoy description just produces a more polished version of the wrong application.
Worse, it reinforces the exact behavior that trained companies to write vague JDs in the first place.
What aiming at the company actually looks like
To hit the real bar, you have to research the company the way the hiring manager already knows it:
- Find the actual stack. What does this team really run — the frameworks, the infra, the tools — not just what the ad named? A role posted as "backend engineer" might live in a Kubernetes + PostgreSQL + Go shop, or a serverless + DynamoDB + TypeScript one. Those are different applications.
- Read the culture, not the values page. The polished "our values" section is PR. The real signal is in how the team talks, what they celebrate, what former employees say. Tone matters: a seed-stage startup and a 20-year-old enterprise want different voices in a cover letter.
- Use the recent wins. A cover letter that references a real, recent company achievement — a launch, a funding round, a product milestone — reads completely differently from generic enthusiasm. It says "I already understand where you’re going."
Do this for every application and you stop matching a decoy. You start matching the bar that actually gets people hired.
How myKaria does this now
This is the part I’m most excited about. We built company research directly into the application flow. When you start a new application, myKaria can research the company — its tech stack, its culture and tone, and its recent achievements — and tune your CV and cover letter to what the company actually runs and values, not just what the JD listed.
It shows you exactly what it found, too. No black box. You see the company profile, the tech stack, and the achievements it used — and you decide.
One rule stays: research helps you surface the parts of your real experience that align with the company. It doesn’t invent a top-performer persona. The honesty rule still holds — no fabrication, no faking a profile you don’t have.
The bottom line
The job description was never the whole story. It’s just the part companies let everyone see. The bar that actually matters is the company itself — its stack, its culture, its trajectory.
Stop matching the description. Match the company.
Because the goal was never to beat the keyword filter. It was to get the job, and keep it.