Early accessEarly access is open. Try a free AI mock interview, no card needed. Try it free →
Skip to content
[ AI resume review · Coming soon ]

Your resume, marked up line by line.

Upload your resume and get a PDF back in about two minutes: a score, your pages marked up the way a hiring manager reads them, and rewrites you can paste straight in.

Coming soonSee a sample report
PDF in about two minutesLine-by-line markupOptional job fit
01 · Sample report

The full report, page by page.

Swipe through all 6 pages for a sample resume, reviewed against a sample job. The candidate is fictional.

alex-rivera-resume-review.pdf
Page 1 / 6
[ Resume review ]Tuesday, October 6 2026

Resume review:
Alex Rivera

Good engineer, undersold. Four years in payments, and the two strongest things you have sit under a duty bullet and on page two: a monolith migration that cut p95 latency from 900ms to 240ms, and an open-source ledger library with 1.2k GitHub stars. Above them are six bullets describing duties: responsible for, worked on, participated in. A recruiter skimming for thirty seconds meets the duties first and never reaches the evidence. Against the Senior Payments Platform job you sent, the domain fit is strong and the ownership evidence is thin. Almost everything here is cutting and reordering, plus a handful of numbers only you have.

6.5
Overall score
out of 10, for Senior backend
Software Engineer II
Current role
Acme Pay, since 2024
4 yrs
Experience
all of it in payments
4
Critical issues
about two hours of work
How to read this. The next two pages are your own resume with marks on the page and notes in the margin; that is where the line-by-line detail lives. The written review after it explains the four things that matter most, checks you against the job, answers your two questions and ends with what to do first.
techinview.devResume review · 1 / 6techinview.dev/resume-review
ALEX RIVERA
SOFTWARE ENGINEER II | BACKEND + PAYMENTS
Austin, TX (Hybrid) • alex.rivera@example.com • +1 512 555 0142
linkedin.com/in/alexrivera • github.com/alexrivera • alexrivera.dev
PROFESSIONAL SUMMARY

Software Engineer with 5+ years of experience building scalable, high-performance web applications and distributed backend systems. Passionate about clean code, system design and learning new technologies. Proven track record of delivering features end to end in fast-paced Agile teams and collaborating with cross-functional stakeholders.

SKILLS
Languages: Java, Python, TypeScript, JavaScript, Go, SQL, HTML5, CSS3, Bash
Backend: Spring Boot, Node.js, Express.js, Django, REST APIs, GraphQL, gRPC, Microservices
Frontend: React.js, Next.js, Redux, Tailwind CSS, jQuery, Bootstrap
Data & Infra: PostgreSQL, MySQL, Redis, Kafka, RabbitMQ, AWS (EC2, S3, Lambda, RDS), Docker, Kubernetes
Tools & Practices: Git, GitHub Actions, Jenkins, Jira, Confluence, Postman, VS Code, Agile/Scrum, TDD
PROFESSIONAL EXPERIENCE
Acme Pay | Software Engineer II
January 2024 – Present | Austin, TX
  • Checkout Service: Responsible for the checkout service used by customers across web and mobile, working closely with product and QA to deliver new payment features every sprint.
  • Payments Re-platforming (0-to-1): Migrated payments from a Java monolith to event-driven microservices on Kafka, cutting p95 checkout latency from 900ms to 240ms and ending weekly release freezes.
  • Fraud Rules Engine: Worked on various features for the fraud rules engine across the frontend and backend, including rule configuration screens and APIs.
  • Idempotent Retries: Designed idempotency keys and retry logic for card authorizations, reducing duplicate charges by 93.7% and related support tickets by 41%.
  • Mentored 3 new hires through onboarding and their first on-call rotation; ran the team's weekly code review sync.
  • Participated in sprint planning, retrospectives and code reviews as part of a cross-functional Agile team.
Awards: Spot Award, Q3 2024 (Re-platforming) | Winner, Acme Pay Hack Week 2024
Acme Pay | Software Engineer I
July 2022 – December 2023 | Austin, TX
  • Refunds Dashboard: Built an internal refunds dashboard in React and Spring Boot used by the support team to issue and track refunds.
  • Payouts Module: Wrote unit and integration tests, raising code coverage of the payouts module from 48% to 85%.
  • Legacy Services: Fixed bugs and improved performance of legacy billing services written in Java 8.
  • On-call: Participated in a 1-in-6 on-call rotation for the payment authorization APIs.
Brightwave Labs | Software Engineering Intern
May 2021 – August 2021 | Remote
  • Built a Python ETL job that loaded merchant transactions into PostgreSQL for the analytics team.
  • Created REST endpoints in Flask for an internal reporting tool used by the finance team.
Started 2022: that's four. Say four.
Adjectives, no evidence. Name the migration instead.
~45 skills. Keep the 12 you'd defend in an interview.
Dated. Cut jQuery and Bootstrap.
Duty, not result. How many payments a day?
Best line on the page. Make it bullet one.
Says nothing. What did the engine catch?
93.7% reads as invented. Say 94%.
Senior signal. Add time to solo on-call.
Which bugs? How much faster? Or cut it.
techinview.devResume review · 2 / 6techinview.dev/resume-review
NOTABLE SIDE PROJECTS
  • Ledgerline (Go, PostgreSQL | 2023): Open-source double-entry ledger library with idempotent posting and multi-currency support; 1.2k GitHub stars and 30+ contributors. GitHub
  • Personal Portfolio Website (React, Tailwind, Vercel | 2022): My personal site with a blog, dark mode and a contact form. Website
  • Weather App (JavaScript, OpenWeather API | 2021): Fetches and displays a 7-day forecast for any city.
EDUCATION
B.S. Computer Science | State University, Austin, TX | GPA 3.4 | 2022
Relevant Coursework: Data Structures, Algorithms, Operating Systems, Databases, Computer Networks, Software Engineering
ACHIEVEMENTS & CERTIFICATIONS
  • AWS Certified Cloud Practitioner (2023)
  • Winner, Acme Pay Hack Week 2024
  • Dean's List, State University (2019, 2020)
  • 2nd Place, HackTX 2020 (fintech track)
INTERESTS
Hiking, photography, chess, travel, cooking
Page two at four years. It all fits on page one.
1.2k stars in your domain. Move it under Experience.
Everyone has one. Cut.
Tutorial project. Cut.
Drop coursework after your first job.
Four items, two from college. Keep one.
Entry-level. Keep only if the job asks for it.
Already in Awards on page one. Listed twice.
Space you need for evidence. Cut.
Overall: a good payments engineer, undersold. Four fixes: (1) give every Acme Pay bullet a result and round the decimals, (2) lead with the migration and move Ledgerline to page one, (3) cut to one page, (4) settle the years and halve the skills. Target: a real number in the top half of page one.
techinview.devResume review · 3 / 6techinview.dev/resume-review

I.The thirty-second read

1. Your best evidence is below the fold

The migration sits under a duty bullet, and Ledgerline is on page two. A screener reading the top third learns your stack and that you were responsible for checkout. That is all they keep.

  • •Make the migration bullet one of the Acme Pay role.
  • •Move Ledgerline directly under Experience, on page one.
  • •Target: one real number in the top half of the page.
2. Six of ten bullets are duties

Responsible for, worked on, participated in. These describe what anyone in your seat would do. They have no scope and no result, so they read as a job description rather than a record.

  • •The migration bullet is your template: an owning verb, then a before and after.
  • •No exact number? An honest range beats no number at all.
The pattern to apply everywhere: verb, scope, mechanism, result.

II.Fit for Senior Payments Platform

3. Domain fit is strong, ownership is thin

You have the payments depth this job wants. What it asks for most, owning services end to end, the resume leaves the reader to assume.

The job asks forYour resume
Payments domainStrong. Checkout, refunds and a ledger library.
Owning services end to endWeak. “Responsible for” with no scale or outcome.
Reliability and idempotencyStrong. Idempotency keys and retries, with numbers.
MentoringPresent. Add time to independent on-call.
Design docsMissing. Add one if you wrote the migration doc.
techinview.devResume review · 4 / 6techinview.dev/resume-review

III.Bullets

4. The current role
Before

Checkout Service: Responsible for the checkout service used by customers across web and mobile, working closely with product and QA to deliver new payment features every sprint.

After

Checkout Service: Owned the checkout service handling [N] payments a day across web and mobile, raising payment success from [X]% to [Y]%.

Why: “Responsible for” describes a job. Scale and an outcome are what make a backend bullet read as Senior. The numbers are yours, not mine to invent.

Before

Payments Re-platforming (0-to-1): Migrated payments from a Java monolith to event-driven microservices on Kafka, cutting p95 checkout latency from 900ms to 240ms and ending weekly release freezes.

After

Payments Re-platforming (0-to-1): Led the move from a Java monolith to [N] Kafka-based services, cutting p95 checkout latency from 900ms to 240ms and ending weekly release freezes.

Why: Your strongest line, moved to position one. Say “Led” only if you did; “Drove” is honest if you shared it.

5. People work and the side project
Before

Mentored 3 new hires through onboarding and their first on-call rotation; ran the team’s weekly code review sync.

After

Mentored 3 new hires to their first solo on-call rotation within [N] weeks.

Why: Time to independence is the number engineering managers track. It turns a nice line into evidence of leverage.

Before

Ledgerline (Go, PostgreSQL | 2023): Open-source double-entry ledger library with idempotent posting and multi-currency support; 1.2k GitHub stars and 30+ contributors.

After

Ledgerline: open-source double-entry ledger library in Go, with 1.2k GitHub stars and 30+ contributors, adopted by [N] teams in production.

Why: It proves payments depth outside your day job. It belongs on page one, under Experience.

techinview.devResume review · 5 / 6techinview.dev/resume-review

IV.Your questions

6. “Should my resume be one page?”

Yes, at four years. Two pages tells a reader you didn't choose. Everything on your page two except Ledgerline and education can go, and both of those fit on page one once the duty bullets are rewritten.

7. “Is a GitHub project worth listing?”

This one is, and it is underplayed. A ledger library with 1.2k stars is direct evidence for a payments role. Projects without traction, like the weather app, cost you space and credibility. Keep the one that has users.

Do this first

  1. P1Give every Acme Pay bullet a result. Use the rewrites in section III. Three need numbers from your dashboards.
  2. P2Reorder. The migration becomes bullet one, and Ledgerline moves onto page one under Experience.
  3. P3Cut to one page. Delete the portfolio site, the weather app, coursework and interests.
  4. P4Fix the small trust leaks. Change 5+ years to four, round 93.7% to 94%, halve the skills, list the Hack Week win once, and keep the AWS cert only if the job asks.
Three of these need numbers only you have. When you've made the edits, upload the new version for a second pass at techinview.dev/resume-review, then practice the Senior payments interview at techinview.dev.
techinview.devResume review · 6 / 6techinview.dev/resume-review
02 · What's in the report

Five parts, five or six pages.

/01

The verdict

One page: a score out of 10, the honest summary, and four numbers. Score, current role, experience and how many critical issues.

/02

Your resume, marked up

Your own pages with circles, underlines and strike-throughs, and a short note in the margin beside the line it is about.

/03

The written review

What a screener takes away in thirty seconds, the biggest theme on your resume, and before and after rewrites. Numbers only you know are left as [N].

/04

Fit and your questions

Add a job description and get checked against what it asks for. Add questions and each one gets a straight answer.

/05

Do this first

Three to five fixes ranked by impact per hour of your time, so you know where to start tonight.

03 · How it works

Upload, wait a few minutes, download.

  1. 01

    Upload your PDF

    Up to 3 pages. It has to be a text PDF exported from Docs, Word or LaTeX, not a scan.

  2. 02

    Add a job and your questions

    Both optional. Paste a job description to be checked against it, and ask anything you want answered, like one page or two.

  3. 03

    Download the report

    About two minutes later the PDF is ready. It stays in your account until you delete it.

04 · Pricing

Pay per review.

Buy one review, or three so you can review, fix and review again. Credits never expire.

1 Review
$6
  • One full PDF report
  • Line-by-line markup and rewrites
  • Optional job fit page
Coming soon
3 ReviewsBest Value · −11%
$16$18
  • $5.33 per review
  • 3 full PDF reports
  • Line-by-line markup and rewrites
  • Review again after each fix
Coming soon
Launching soon · One-time packs · No recurring billing · Failed reviews are refunded
05 · FAQ

Before you upload.

What happens to my resume file?+

We read it, write the review and throw the file away. We never save the original upload. The report does include your marked-up pages, so it holds your resume's content. You can delete a report at any time and it is removed from storage.

How is this different from pasting my resume into ChatGPT?+

A chat window gives you general advice in a paragraph. This marks up your actual pages line by line, ranks the fixes, writes rewrites that leave placeholders instead of inventing numbers, and checks fit against a real job description. The review is written for software engineering roles and levels.

Who is this for?+

Software engineers from new grad to Staff, and engineering managers. The review judges what technical recruiters and hiring managers look for: scope, impact, evidence and level.

Will it make up numbers for me?+

No. When a bullet needs a metric only you know, the rewrite leaves a [N] or [period] placeholder for you to fill in.

Can I upload a Word file?+

PDF only. Export from Word, Google Docs or your LaTeX editor with File, then Download as PDF.

Why does it reject my PDF?+

The markup needs the text in the file to find each line on the page. Scanned resumes and image exports have no text, so export a fresh PDF from your editor. Rejected files never use a credit.

Do I need to add a job description?+

No. Without one the review is judged against the level your resume points to, and says which level it assumed. With one, it also checks you against what that job asks for.

Can I use a review credit on an interview?+

No. Review credits and interview credits are separate balances. Both are one-time packs with no recurring billing.

What if the review fails?+

If the report cannot be generated, the credit goes straight back to your account.

[ Next step ]

The resume gets you the call. Practice the interview.

Coming soonAI mock interviews