ApplyHonest

Role guides

Data analyst requirements, with the quote you would need

Data analyst postings mix a tool list with a business task: pull a number, explain it, and say what changed. The tool alone is a weak quote. “Used SQL” does not show that you changed a decision.

Examples on this page are fictional composites, not customers and not testimonials.

Often required

Often preferred, and easy to fake

What a citation looks like

SQL reporting

“Built a weekly SQL extract of refund reasons for the billing team.”

The sentence names SQL, the cadence, and the user. That is enough to cite. It does not prove Tableau.

Python

“No sentence.”

If Python is absent, the row stays unsupported. Taking a course without a work bullet is still a gap until you write the work you did.

The gap people paper over

The usual invented line is a dashboard tool or a percentage lift. If the resume says you exported a CSV, do not upgrade that to a warehouse migration.

Questions

Does “proficient in SQL” on a skills line count?

It can be cited, and it is weaker than a bullet that shows a question you answered. ApplyHonest will not turn the skills line into a story.

Should I list every library?

List libraries you used on a task you can describe. A keyword block that copies the posting is how unsupported tools sneak in.

Related: Data scientist, Business analyst

Check your resume against a real posting