Farhad spent almost eight years at LinkedIn Talent Solutions, most recently as Enterprise Account Director. He has a software engineering background and works on the technology and product side of HeyHuma.
LinkedInWe worked there with founders, sales leaders and hiring managers who usually knew perfectly well who they wanted to reach.
The hard part came after that. Who really fits? How do you show up in a way that is relevant? And who has time to run it properly?
So we started HeyHuma.
We combine our LinkedIn experience, our own technology and a team that does the work. We map the market, select the right people, run campaigns and follow up on replies.
You talk to the people who are interested.
At LinkedIn we kept seeing the same thing: the more relevant the story is to the candidate, the better the result.
So personalisation here goes further than a name in a message.
For each candidate we look at experience, background and how they might connect to the role. We use that for the first contact and for the personal careers page that follows.
On that page an employer can tell their story in a way that suits the candidate. For one person the emphasis is on the team and what the role involves. For another, responsibility, room to grow or the type of organisation matters more.
That gives every candidate enough context to understand why we approached them in particular, and why a conversation could be interesting.
By now that principle runs through the whole way we built HeyHuma.
Behind HeyHuma sits technology we build ourselves.
It helps us map markets, assess candidates on substance and find signals that an ordinary search misses easily.
The technology supports the work. Our team stays responsible for the selection, the campaign and the follow-up.
Cookies op HeyHuma
We gebruiken cookies om onze website goed te laten werken en inzicht te krijgen in het gebruik ervan. Cookiebeleid
{{ t.hero.p1 }}
{{ t.hero.p2 }}
{{ t.hero.p3 }}
{{ t.hero.p4 }}
{{ t.hero.p5 }}
{{ t.personalisatie.p1 }}
{{ t.personalisatie.p2 }}
{{ t.personalisatie.p3 }}
{{ t.personalisatie.p4 }}
{{ t.personalisatie.p5 }}
{{ t.personalisatie.p6 }}
{{ t.tech.p1 }}
{{ t.tech.p2 }}
{{ t.tech.p3 }}