Most comparisons of recruitment software are written for companies hiring in the US or Western Europe. If your hiring happens in Turkey, several of the assumptions behind those comparisons quietly stop holding — not because the products are bad, but because the market underneath them is different.
This is what actually changes, and what to check before you sign anything.
Where candidates actually come from
In most markets, a job board integration is a convenience. In Turkey it is closer to a precondition.
Kariyer.net holds a dominant share of white-collar applications, with Secretcv and LinkedIn behind it, and the practical consequence is that a system which cannot receive applications from those sources leaves you re-entering candidates by hand. That work does not show up in any pricing page, but it is the single largest source of friction teams report after adopting a global platform here.
Two things are worth separating when a vendor says "we integrate":
Posting out means your opening appears on the board. Useful, and most platforms manage it through a generic feed.
Pulling in means applications arrive in your system with the candidate's CV, contact details and answers attached. This is the one that saves the work, and it is the one that is frequently missing or handled by a CSV export someone runs on Fridays.
Ask which of the two is on offer, and ask to see it working on a live account rather than in a slide.
KVKK is not GDPR with different initials
Turkey's data protection law, KVKK, is close enough to GDPR in shape that vendors often answer questions about it by pointing at their GDPR page. The overlap is real, but three differences matter for a hiring system specifically.
Explicit consent has a narrower role. Under KVKK, processing personal data generally requires explicit consent unless one of the enumerated legal grounds applies. Recruitment data is usually processed under a legitimate-interest or contract-related ground, but candidate consent flows still need to be collected and stored as evidence, and your system has to be able to produce that record per candidate.
Retention has to be decided and applied. Keeping every CV forever is the default behaviour of most systems and the wrong answer legally. You need a retention period you can defend, and a mechanism that actually deletes when it expires rather than hiding the record.
Cross-border transfer has its own rules. If the platform stores data outside Turkey, the transfer needs a lawful basis. This is not a reason to reject foreign platforms, but it is a question your legal team will ask, and "the vendor is SOC 2 certified" is not an answer to it.
A useful test: ask the vendor to describe how a candidate's deletion request is executed end to end, including backups. The quality of that answer tells you more than the compliance page does.
Turkish-language CVs
Parsing a CV is harder in Turkish than in English, and the difference is structural rather than a matter of effort.
Turkish is agglutinative: a single root takes a chain of suffixes where English would use separate words, so the same job title appears in a dozen inflected forms. Matching on exact strings fails quietly — it does not throw an error, it just returns fewer candidates than it should.
Casing has a specific trap. Turkish has a dotted and a dotless i, and the uppercase of "i" is "İ" rather than "I". Any system that lowercases text with invariant rules will turn "İSTANBUL" into something that no longer matches "istanbul". This bug is common, invisible, and costs real matches.
Then there are the fields that only exist here — military service status, for example — and education institutions whose names carry no signal unless the system knows the local landscape.
If CV screening is part of why you are buying, test it with your own CVs, in Turkish, before you decide. A demo on an English sample tells you nothing about this.
Global platform or local one
There is no universal answer, but the trade is consistent.
Global platforms give you maturity, integration ecosystems, and a product that will still exist in five years. You pay for that in currency exposure, in job-board integrations that treat Turkey as an edge case, and in support that operates in a different timezone with limited context on local hiring practice.
Local platforms give you the board integrations, KVKK handled as a first-class concern rather than a mapping exercise, Turkish-language handling built in, and billing in lira. You give up some ecosystem depth and you take on more vendor risk.
The honest version of this decision usually comes down to where your hiring volume is. If most of your hiring happens in Turkey, the local advantages compound weekly and the global advantages are things you read about rather than use. If Turkey is one office among many and your reporting has to consolidate globally, the calculation flips.
Questions worth asking before you commit
- Does the system pull applications in from Kariyer.net and Secretcv, or only post out?
- Can you show a candidate deletion executed end to end, including what happens to backups?
- Where is the data stored, and what is the lawful basis for the transfer if it leaves Turkey?
- What happens to CV parsing accuracy on Turkish-language CVs — tested on ours, not on samples?
- Is the price in lira, and if not, what happens at renewal when the exchange rate has moved?
- What does support look like in our working hours, and does it understand local hiring practice?
None of these are exotic. They are simply the questions that a comparison written for another market will not think to ask, and each one of them turns into monthly friction if the answer turns out to be the wrong one after you have migrated.
Jobbar.AI is a Turkish recruitment platform, so we have an interest here. The questions above are the ones we would ask of any vendor including ourselves — the answers are worth demanding in writing rather than taking from a blog post.