In German one job has several names, and a search only knows the one you typed
In English a tax clerk is a tax clerk. In German the same job is a Steuerfachangestellte or a Steuerfachangestellter depending on who holds it, the job ad writes Steuerfachangestellte (m/w/d), and the international firm down the road lists the role in English. That is one job. To a title filter it is four different strings, and the filter returns the one you typed.
Nothing warns you. The search comes back with a believable number of people and you work that list. You never learn that everyone who writes the other form was left out. The miss is not random either. Search the masculine form alone and you have removed the women who use the feminine one, which is a coverage problem and a fairness problem at once.
Location repeats the pattern. München and Munich are different strings to a filter that matches exactly. Someone who lives in a town in the surrounding Landkreis may list the town, the metro or the region, and a city-only search keeps some of them and loses the rest.
Build Boolean and X-ray search strings writes the strings for you to paste. This play runs the search and shows you the size of the gap.
What you get back
The title set as it was searched and the location list, so you can reuse both. The count for your original title beside the count for the full set, per database. Then the pool itself: de-duplicated, scored on dated work history with the reason on every row, with the LinkedIn profile and a personal email for the people who passed. The file is plain UTF-8, so the umlauts survive.
Variations worth knowing
Add demand context. The German federal job board can be read for open roles with the same title in the same region. It lists jobs, not candidates, and shows which employers are hiring from this pool.
X-ray what the databases miss. A site:linkedin.com/in web search on the German title forms, with
country and language set to Germany. It is charged per search even when it finds nothing, and the hits
are leads to verify.
Austria and Switzerland. Same method, different titles. Say which country you are searching.
Where this goes wrong
No Xing. Hyreflow has no Xing access. People who keep a profile only there are missing from the pool.
A stem in the wrong database. One database matches a stem and the others return nothing on it, silently. A zero beside hundreds elsewhere is a query fault.
The radius that measures the employer. One database's radius filter runs from the company's head office, not the person, so the town list is used.
A tool nearly everyone uses. Where a whole profession works in one product, naming it says little and leaving it off says less. Those profiles are tiered as likely and confirmed on the call.
