Who can certify a result?

Certifying someone else's result requires having your own real K·reer profile — it's never anonymous. When you certify something, your name and profile are publicly linked to that certification, the same as if you signed it.

• Company certification: someone at the company where the result happened (ideally a direct manager) confirms it's real.
• Direct-report certification: someone who reported to that person confirms they managed a team.
• Testimonials: the one exception — a colleague, client, or former manager can leave a testimonial without needing a K·reer account, so a quick recommendation isn't blocked by a signup wall. That's why testimonials are shown differently from a verified certification — labeled "via link," not with the same seal.

What do we do to prevent fake certifications?

No open system is immune to someone trying to game it, but we make it costly and detectable:

• We detect suspicious reciprocal certifications. If two accounts certify each other, that's automatically flagged for review — we don't block the certification (two real colleagues can legitimately certify each other), but it stays visible for the team to check.
• We cap how many different people one account can certify. No genuine certifier vouches for dozens of strangers — a cap makes running a "certification farm" meaningfully more expensive.
• We rate-limit how often someone can respond. An account can't respond to certification requests at a pace no real person would.
• The trust score can never be reached with self-reported data alone. Completing your profile, adding a video, or listing your own certifications helps, but is never enough on its own — at least one real third-party certification is always required.
• Human review, always. None of this auto-suspends or deletes an account — every flagged case is reviewed by a real person on the team before any decision is made.

A concrete example

Ana certifies one of Carlos's results. That same month, Carlos certifies one of Ana's results — without either of them actually having worked where the other claims. The system automatically detects that they certified each other and flags both profiles for review, before either certification counts toward anyone's trust score. It's not blocked in the moment (two real colleagues can also legitimately certify each other), but the case stays visible for the team to review with real context.

What happens if something is confirmed to be fake?

If the team confirms a certification was fabricated, that certification is removed from the result — it stops counting as verified and stops contributing to the score. In more serious cases (a repeated pattern, clear evidence of several accounts certifying each other), the entire public profile can be taken down while it's resolved directly with the person. This is reversible, not a permanent deletion — but while a profile isn't published, it doesn't appear in the directory or show up for anyone.

Every flagged case and how it was resolved is kept on record, not a decision that's forgotten — if the same account generates several cases over time, that's visible to the team the next time it comes up.

How do I report something that looks fake?

Anyone signed in can report a result directly from the public profile, via the 🚩 Report icon next to each result. You don't need to be certain — if something looks suspicious to you, that's enough for the team to take a look.

This keeps evolving

As more people certify results on K·reer, we keep adjusting these protections. If you see something we should handle better, write to us at hola@kreer.app.