feat: Create a candidate by dropping in their CV - #257
Conversation
Adding a candidate meant retyping the name and email that the CV already states — createCandidateSchema requires them, and nothing read them off the document. Text extraction already existed (resume-parser) but only ran against candidates that had been created by hand first. Drop a CV on the add-candidate form and the contact fields fill in. The file is held client-side and attached as the résumé only once the record exists, so a bad extraction leaves no candidate and no orphaned upload behind, and the recruiter confirms every value before anything is written. Extraction is deliberately narrow — contact details only, capped at 12k characters. Scoring already reads the full résumé text. Works with any CV, including LinkedIn's "Save to PDF" profile export, which is the supported way to get LinkedIn data in: the Recruiter APIs need a Corporate licence on the customer's side, and scraping breaches LinkedIn's terms. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
Warning Review limit reached
Next review available in: 18 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
🚅 Deployed to the reqcore-pr-257 environment in applirank
|
Allows users to create a new candidate from within the application modal, including optional CV extraction, rather than being limited to searching existing candidates.
1 participant
Adding a candidate meant retyping the name and email that the CV already states — createCandidateSchema requires them, and nothing read them off the document. Text extraction already existed (resume-parser) but only ran against candidates that had been created by hand first.
Drop a CV on the add-candidate form and the contact fields fill in. The file is held client-side and attached as the résumé only once the record exists, so a bad extraction leaves no candidate and no orphaned upload behind, and the recruiter confirms every value before anything is written.
Extraction is deliberately narrow — contact details only, capped at 12k characters. Scoring already reads the full résumé text.
Works with any CV, including LinkedIn's "Save to PDF" profile export, which is the supported way to get LinkedIn data in: the Recruiter APIs need a Corporate licence on the customer's side, and scraping breaches LinkedIn's terms.
Summary
Type of change
Validation
DCO
Signed-off-by) viagit commit -s