Keeping generated profiles faithful to experience.
Make generated writing accountable to its source.
Where this work fits
A person’s experience can suit an opening without that connection being obvious in a general profile. I worked on making the introduction and experience descriptions more relevant to the role, while keeping the original career history intact.
I worked on prompts and checks that preserved career facts in generated profile content. Job titles and figures needed to remain faithful to the source, and a requirement in the opening could not become a claim about the candidate without supporting experience.
Connect a generated claim to its source
Better wording. Same facts.
I led 20 engineers for ten years.
No source for the team size or duration.I build backend APIs 01 and background jobs 02 for inventory and product data.
A useful rewrite still has to be true.
The model could borrow a skill from the job description that the candidate had never claimed. Checks had to preserve titles, figures, and supporting experience. There was also a waiting problem: I used priority queues and concurrency control so a profile being opened could take the next available generation slot.
The skills behind the work
- Grounding
- Check that generated claims are supported by the source information.
- Validation
- Reject invalid or unsupported input before it affects the rest of the application.
- Prompt engineering
- Refine model instructions using observed behavior and failure cases.
The profile experiment showed more reviewed candidates progressing to a conversation. The work improved how experience was presented and tested that change against what people did next.