Skip to content
    Gradr case study

    Interactive demo

    Gradr in action

    A walkthrough of how Gradr scores a resume, grades an interview answer and turns both into career insights. Every panel below runs on sample data so you can explore the feedback loop without an account.

    AIReact

    Rubric-based scoring on a real bullet point

    Resume bullet

    Worked on a finance app and helped improve the user experience for users.

    54ATS score
    Parseability92

    Clean single-column layout, no tables.

    Section structure80

    Missing a dedicated Projects section.

    Keyword coverage41

    6 of 14 target-role keywords present.

    Impact language28

    No measurable outcome in this bullet.

    Rubric findings

    • Quantified outcome“helped improve” has no number attached, so a reviewer cannot judge the size of the work.
    • Ownership“Worked on” hides what you personally built. Name the component you owned.
    • RelevanceDomain matches the target role — keep the project, rewrite the line.

    Suggested rewrite

    Built the expense-capture flow for a personal finance app in React, cutting the time to log a transaction from ~30s to under 10s and lifting weekly logging retention.

    Sample data, not a live account. The scores, findings and trends shown here illustrate how the rubric-based scoring and analytics behave inside Gradr — no real resumes or interview transcripts are used on this page.