AI Resume Analyzer

Get AI-powered feedback to improve your resume

Resume score

Solid engineering background, but most bullets describe duties rather than outcomes. Add numbers to your top three achievements and this moves into strong territory.

Why this score: Real engineering scope, but only two of eleven bullets carry a metric, so the impact is asserted rather than shown.

Your resume

sample-resume.pdf

612 words, 2 pages

Analyse another resume

Section breakdown

  • Contact
    Pass92

    Email, phone and GitHub are all present and parse cleanly.

  • Summary
    Poor45

    Opens with 'hardworking team player' — generic, says nothing specific.

  • Experience
    Needs work70

    Good scope of work, but only two of eleven bullets carry a metric.

  • Education
    Pass85

    Degree, institution and expected graduation are clear.

  • Skills
    Pass76

    Specific and current; consider grouping by domain rather than one list.

  • Formatting
    Needs work64

    Contact details sit in the header, which some ATS parsers drop.

AI feedback

Keyword match

In your resume

  • TypeScript
  • React
  • Node.js
  • PostgreSQL
  • REST APIs
  • Git

Not found

  • Kubernetes
  • CI/CD
  • GraphQL
  • AWS
Matched 6/10 keywords60%

Few job descriptions list only things one person has done, so a full match is rare and not the goal. Add the missing terms that genuinely describe your experience — not ones you couldn't discuss in an interview.

Suggested bullet rewrites

Square brackets mark numbers only you know — replace them with your real figures before using these.

  • Original

    Responsible for maintaining the booking service.

    Improved

    Maintained a booking service handling [X] requests/day, cutting p95 latency from [X]ms to [X]ms.

    Why: Turns a duty into an outcome, and names the service it happened to.

  • Original

    Worked on the team that built the new admin dashboard.

    Improved

    Built [X] screens of the admin dashboard in React and TypeScript, used daily by [X] internal staff.

    Why: Names your specific contribution and the stack instead of the team's.

  • Original

    Helped improve database performance.

    Improved

    Added covering indexes to the three slowest queries, reducing average report load from [X]s to [X]s.

    Why: States what you actually changed, and ties it to the queries it affected.

Things to fix

  • Nine-month gap between the 2024 and 2025 roles — account for it in one line in your summary so a reader is not left guessing.
  • Two spelling errors in the experience section ('recieved', 'managment') — proofread it end to end before you send it.