How LinkedIn built domain-adapted EON foundation models to power Hiring Assistant candidate matching
LinkedIn's earlier fine-tuned domain-specific model required significant effort to add new features or generalize to new applications, because representative high-quality training data had to be regenerated and the model retrained for each change. Proprietary GPT-4-class models also posed latency and cost concerns.
In testing, LinkedIn's EON-8B model is 75x cheaper than GPT-4 and 6x cheaper than GPT-4o, and significantly improved candidate-job-requirements matching accuracy in Hiring Assistant, outperforming GPT-4o mini by an absolute 4% and Llama-3-8B-instruct by an absolute 30%.
Prompt simplification strategies also reduced prompt size by 30%.
Show all 7 reported metrics
Frequently asked questions
What did this team achieve with this AI workflow?
In testing, LinkedIn's EON-8B model is 75x cheaper than GPT-4 and 6x cheaper than GPT-4o, and significantly improved candidate-job-requirements matching accuracy in Hiring Assistant, outperforming GPT-4o mini by an ab…
What tools did this team use?
Hiring Assistant, EON, RAG, RLHF, DPO, Llama, Mixtral, Mistral, Kubernetes, DeepSpeed.
What results were reported?
cost efficiency vs GPT-4: 75x; cost efficiency vs GPT-4o: 6x; Prompt size reduction: 30%; LLM calls from evaluation agent: Nearly 90% (source-reported, not independently verified).
How is this recruiting AI workflow structured?
Recruiter query intake → Orchestration layer decomposes query → Evaluation agent processes candidate data → Match output with explanation → Recruiter approves matching criteria.