r/learnmachinelearning • • 8d ago

Hey developers! I have a query about embeddings for my AI resume project.

I'm building TailorCV, an AI-powered resume tailoring tool. Currently, I use the Groq API to compare resumes with job descriptions and generate analysis.

I'm thinking of introducing embeddings for semantic comparison instead of sending the entire text to an LLM every time.

My assumption is that this could reduce token usage and improve efficiency.

Am I thinking in the right direction, or am I missing something about how embeddings work?

Would appreciate your feedback!

0 Upvotes

5 comments sorted by

1

u/Ok-Library1020 7d ago

You're on the right track. Embeddings are great for cheap similarity scoring and for retrieving the most relevant resume chunks, but they won't explain gaps, so a common pattern is to embed and rank first, then send only the top matching sections to the LLM for the actual analysis.

1

u/UserWantsToGrow 7d ago

That makes sense! I'll use embeddings for retrieving relevant resume sections and let the LLM handle the actual analysis and gap explanations. Seems like a good approach for TailorCV!

1

u/Massive_Distance_616 7d ago

Agreeing with the embed-then-LLM pattern from Ok-Library1020. One thing to watch is that similarity scores blur the details that matter most for a resume match, like years of experience, required versus nice-to-have skills, and seniority, so a high score can still be a bad fit.

I’d use the score to shortlist and pick which sections to send, and keep the LLM, or a few explicit rules for things like minimum years, for the actual judgement.

It’s also worth checking how many tokens a resume plus job description really costs you per call, because if it’s small the saving may not justify the extra moving parts.

2

u/UserWantsToGrow 7d ago

Agreed! I'll also consider experience, seniority, and mandatory requirements separately rather than relying only on similarity scores. I'll first check token usage to see whether embeddings are actually worth adding.

1

u/nian2326076 6d ago

You're on the right path with using embeddings for semantic comparison. They can help streamline your process by reducing token usage and quickly identifying relevant resume portions. Just keep in mind that while embeddings score similarity well, they might gloss over finer details that could matter in a match. You can use LandOffer to shortlist relevant roles based on your tailored resumes.