What this role’s resume is actually judged on — the language postings use, what a reviewer looks for in the first ten seconds, and the specific way Business Analyst (Consulting) resumes go wrong.
A first pass takes seconds and is looking for three things. If they are not near the top, the rest of the page rarely gets read.
Most resumes fail one bullet at a time. The difference is almost always specificity — a number, a constraint, or a consequence.
Gathered requirements and documented business processes.
Mapped the claims intake process end to end and found 40% of handling time sat in a re-keying step between two systems; the integration cut average handling from 12 minutes to 7.
Terms that recur in real postings for this role. They belong in the bullet that proves them, not in a list at the bottom — our own checker weights requirement coverage at 40% and raw keyword matching at 20%, and most serious systems make a similar trade.
A keyword you cannot defend in an interview is worse than a missing one. How the format checks work.
Requirements documents and process maps are inputs. What a hiring manager wants is the inefficiency you found and what it was worth. If a bullet ends at 'documented', it stops one sentence short of the point.
Expect a data-heavy case: reading an exhibit correctly, doing the arithmetic without a calculator, and saying what the number means rather than only what it is.
Recommendations with no evidence they landed
Industry breadth in place of depth
Supporting-role language throughout
Listing technologies you have touched once
A resume that reads identically to a mid-level one
Abstraction with no anchor
Generic resume advice only goes so far — what matters is whether this resume covers this posting. Paste both and get requirement-by-requirement coverage, the keywords you are missing, and the format problems a parser will hit. The first check is free.