Features Β· Docs

Everything inside OptiResume

A complete, plain-English reference to every feature, what it does, why it matters, how to use it, and what to expect. Most features are free forever; only the AI-powered ones consume credits (and cache hits are always free).

Tailor

Reshape your resume for every JD, same facts, the recruiter's words.

JD-Tailored Resume Variants

One resume, rewritten for the exact job you're applying to.

AI Β· credit

Recruiters, and the ATS that pre-screens for them, scan for the words in their job description. Paste any JD and OptiResume produces a brand-new variant of your resume that speaks that JD's language: it leads your summary and skills with what the role prioritises, and rewrites bullets to use the JD's terminology wherever the underlying skill is genuinely yours. Each variant is saved as its own row, so you can keep one finely-tuned resume per company or drive instead of endlessly overwriting a single file.

Preview

Your bullet

Worked on backend APIs using Python and Flask for a college portal.

Tailored for the JD

Architected production REST services in Python (Flask, FastAPI), shipped 12 endpoints integrating three downstream systems.

Why it matters

A generic resume competes on luck; a JD-tailored one competes on relevance. The very same experience, described in the recruiter's own vocabulary, is what moves you from 'auto-filtered in six seconds' to 'shortlisted', without ever touching the truth of what you actually did.

How to use it

  1. 1Open any resume on your dashboard and click 'Tailor for a JD'.
  2. 2Paste the full job description. Optionally set a target role and a variant label (e.g. 'TCS DET 2026') so your saved list stays scannable.
  3. 3We generate a new resume row plus a plain-language summary of every change we made, your audit trail.
  4. 4Skim the summary, keep what's true, and download or copy the variant.

What to expect

1 AI credit per variant; an identical JD + resume is served from cache for free. Anti-fabrication is hard-wired: the model may re-word and re-order, but it can never invent a skill, employer, metric, or project you didn't list. Every 'bridge' it makes, surfacing a real skill of yours in the JD's words, is flagged so you can verify it.

Pro tips

  • Set a variant label per drive so your resume list reads like a campaign board.
  • Add a target role for sharper framing when the JD title is vague.
  • Read the 'what changed' summary before you apply, it doubles as interview prep.

JD Requirements Breakdown

Know which missing keywords are dealbreakers and which are bonuses.

AI Β· credit

Not every requirement in a JD carries the same weight. This breakdown reads a job description and separates the true must-have skills from the nice-to-haves, reads the seniority signal (intern / fresher / junior / mid / senior / lead), tags the domain, and lists 3-5 of the day-to-day responsibilities in plain English. It then labels each keyword you're missing as either a real blocker or a bonus, so you spend your limited prep time on what actually gates the application.

Why it matters

Chasing every missing keyword equally is how people waste weeks learning a 'nice-to-have' while ignoring the one must-have that's silently rejecting them. Prioritisation is the entire game, this tells you where the leverage is.

How to use it

  1. 1Open any analysis that has a JD attached.
  2. 2In the missing-keywords section, click 'Analyze JD requirements'.
  3. 3Read the must-have vs nice-to-have split, the seniority tag, and the responsibilities list.
  4. 4Fix the must-have gaps first, those are the ones costing you interviews.

What to expect

1 AI credit, cached per JD hash, re-running the same JD later is free. The breakdown is stored with the analysis so you can revisit it any time.

Pro tips

  • If you're a fresher and the JD reads 'mid-level', that's your signal the bar is high, tailor aggressively.
  • Must-haves you genuinely lack are honest reasons to keep learning, not reasons to fabricate.

Skill-Claim Credibility

Make sure every skill you list is one you can defend.

Free

Anyone can type 'React' on a resume. The Skill Claim card checks whether the skills in your Skills section actually show up in your projects or experience, and flags the ones that don't, because that's exactly the gap a recruiter probes in an interview. You can close a flagged skill two ways: add a bullet that demonstrates you used it, or attach real evidence (a GitHub repo, a certificate, a hosted project, or a live demo). A proof is owned by your account, so one link covers every resume variant.

Why it matters

Recruiters discount unproven claims and trust demonstrated ones. An unsupported skill list quietly drags down how credible the rest of your resume looks. We surface those gaps before an interviewer does, so you either back the skill up or drop it, and walk in able to defend every line.

How to use it

  1. 1Open any analysis, the Skill Claim card lists any skills we couldn't find backed up in your bullets.
  2. 2Add a bullet that shows the skill in action, that's the strongest fix, or click 'Add proof', paste a URL, and pick a type: github / project / certificate / demo.
  3. 3Proof-backed skills show a verified check and a link to the evidence, and count toward the 'N verified' badge on your report.

What to expect

Free, and permanent across your account. One proof per skill covers all resumes. Note: a proof is a credibility signal for you and interviewers, it does not change your ATS or match score, those stay tied to what's actually written on the page.

Pro tips

  • Prioritise the skills the JD marks as must-have, those are the ones you'll be grilled on first.
  • A pinned GitHub repo with a clear README is the most credible proof type for freshers.

Have an idea for a feature?

OptiResume is built in the open by one person who reads every message, bug, idea, complaint, or kudos. If something here could be clearer or more useful, tell us.