AI hiring managers are reading for a specific signal, and it is not the one most candidates put on the page. They have read a thousand resumes that say "built ML pipelines using TensorFlow and AWS." They are not looking for that. They are looking for evidence that you can take a model from a notebook to something that earns its keep against a real eval set, on a real budget, in a real product.
That changes what gets weight on your resume. A bullet about a fine-tuning run matters because of the eval delta and the cost - not because you used LoRA. A retrieval pipeline matters because of recall@k on a golden set and p95 latency under load - not because you wired up a vector DB. A research project matters because of the result it landed and where it landed - not because you ran a transformer.
"Hiring managers don't read your skills section. They read your bullets and decide if your skills section is bullshit."
The framework names matter, but only the right ones, and only in context. Listing PyTorch, JAX, vLLM, Triton, Ray, or a specific quantisation library is useful when the bullet around it shows you used it under pressure - shaved 40% off inference cost, kept p95 under 800ms during a launch, replaced a brittle prompt with a fine-tune that improved factuality 18 points on a held-out set. Names without numbers read as a buzzword pile.
Senior roles add one more bar: external signal. A first-author paper at a top venue, a maintained open-source repo with real users, a talk at a serious conference, or a clearly written technical blog. For research roles this is table stakes. For senior engineering roles it is increasingly the tiebreaker between two strong on-paper candidates. If you have it, it goes on page one.
"The candidates who get AI offers are comfortable being a researcher on Tuesday and an engineer on Wednesday. Your resume needs to show both."
The other thing AI hiring managers screen for is range. Pure researchers who cannot deploy get filtered out of product teams. Pure engineers who cannot read a paper get filtered out of model teams. The candidates who get offers are comfortable being a researcher on Tuesday and an engineer on Wednesday - and their resumes show both. One bullet about an eval methodology you designed. One bullet about a production rollout you owned. One about cost or latency you fixed. That is the shape that converts.