New in myKaria: Company Research That Reads the Room

myKaria has always tailored your CV and cover letter to the job description. That works — right up until the job description is useless.

The problem we kept hitting

Lately, more and more JDs are vague on purpose. Companies have learned that when they list exact skills, every applicant mirrors them back perfectly, and the posting stops filtering anyone. So the real requirements move off the page. The CV that matches the JD word-for-word can still miss the mark completely, because the mark was never on the page.

We realized tailoring to the JD wasn’t enough. We needed to tailor to the company.

What we built

Company research now runs as part of creating a new application. When you opt in, myKaria researches the company across three angles and feeds what it finds straight into your documents:

• The real tech stack. What the company and team actually use — frameworks, infrastructure, tools — pulled from high-signal sources, not just the JD’s buzzwords. This flows into the skill matching, so your CV highlights the technologies this company genuinely runs.
• Culture and tone. How the team communicates and makes decisions. This shapes the voice of your CV and cover letter, so a seed-stage startup and a 20-year-old enterprise get different documents — the right different.
• Recent achievements. Launches, funding, product milestones. These flow into your cover letter’s opening, so you reference something concrete and timely instead of generic enthusiasm.

You stay in control

This is your application, so you decide when research runs:

• An "Include company research" checkbox in the application wizard. Turn it on or off per application.
• A research results view on your documents page. After generation, you can open exactly what myKaria found — the company profile, the tech stack, the recent achievements — and see precisely what shaped your documents. No black box.
• A retry path. If research didn’t complete the first time, you can re-run it when you regenerate documents. myKaria also saves a snapshot of the research with each application, so regenerating later uses the same data.

If research can’t run — no API key, a scrape times out, the search comes back empty — your application is created exactly as before, JD-only, with zero added friction. Research enriches; it never blocks.

Why this fits how we build

Company research extends what myKaria already did, it doesn’t replace it. The skill matcher (which separates "explicitly required" from "partial match") now also sees "technologies the company uses for this role." The honesty rule is untouched: research helps you surface the real parts of your experience that align with the company. It does not invent skills or fake a profile.

And because research is shared across users, the first person to apply to a company pays the lookup cost once. Everyone after gets it instantly from cache.

Where it lives

The feature is rolling out with our next release. It’s available on paid tiers (admins control access per tier), and the research data is manageable from the admin panel — re-run or clear a company’s cached research on demand.

Try it on your next application

The next time you start an application, turn on company research and open the results. See what myKaria found about the company you’re targeting — then decide how you want to use it.

Because matching the company beats matching the description. Every time.