A résumé and cover letter tailored to the listing

Here's the full text of a job listing:

[paste the whole listing, including the sections about the company
and benefits]

Analyze it. Don't write anything about me yet, just about the
listing.

1. What does this role actually involve day to day — describe a
   typical workday the way you picture it from the listing.
2. Split the requirements into three groups, noting for each what
   told you it belongs there:
   - MUST have (without this I don't get hired)
   - WOULD LIKE (a plus, catchable later)
   - FILLER (phrases that don't mean anything)
3. What's repeated more than once in the listing, or mentioned
   right at the start? That's probably what matters most to them.
4. What problem is this hire most likely solving? Why did they open
   this position?
5. What's conspicuously missing from the listing, and what should I
   ask about?
6. What vocabulary does the company use — list 15 words and phrases
   it uses that I should use too.

For points 1 and 4, mark what's your guess, so I don't confuse it
with what's actually stated in the listing.

Here are some phrases from a listing I don't fully understand or
that seem off to me:

[list the sentences verbatim]

For each, tell me:
- what it most often means in practice
- an optimistic interpretation and a pessimistic one
- one specific question I could ask at the interview to check it,
  phrased so it doesn't sound distrustful

Don't turn this into a list of warnings. I want to understand, not
get scared off.

I have this entry on my résumé written as a single sentence:

“[paste the entry, e.g. President of a student club, 2024—2025]”

Interview me so we get something usable out of it. Ask me one
question at a time, in order, and wait for my answer each time.

Ask about:
- what I did repeatedly, specifically (actions, not the title)
- who I worked with and how many people
- what tools and systems I used
- what came out of it, what changed, what's quantifiable
- what was hardest and how I solved it
- what I'd do differently today

When we're done, summarize it into 5—8 bullet points written the
way they could appear on a résumé. Use only what I told you.

Here's my experience described in my own words:

[paste bullet points from all positions]

Go through them and, for each, tell me what number or measurable
figure could plausibly be attached to it — and ask me a specific
question that helps me recall it.

Look for: counts (people, orders, events, customers per day),
volumes, frequency (how many times a week/month), duration, scope
of responsibility, budget size, before/after change.

Don't invent any numbers or example numbers. Just ask.
Where I can't think of a number, tell me how to describe it without
one so it doesn't feel empty.

You have the listing analysis from the previous step, and here's my
résumé (no contact details):

[paste your résumé]

Do a three-table comparison:

1. I COVER: requirement from the listing | specifically what from
   my résumé | how strongly (direct experience / related /
   marginal)
2. I PARTIALLY COVER: requirement | what of mine comes closest |
   what I'd need to add for it to fit
3. I DON'T COVER AT ALL: requirement | how big a problem this is |
   catchable before starting, or not

At the end, tell me:
- your estimate of whether it's worth applying, and why
- 3 things from my résumé that are strongest for this role
- 3 things that are irrelevant for this role and should be
  shortened or cut

Don't sugarcoat it. If the match is weak, say so.

Rewrite my résumé for this specific role.

RULES that override everything else:
- Don't invent. You may only rephrase and reorder what's already in
  my résumé or in my notes below.
- You may not add any skill, tool, number, or experience that isn't
  there.
- Don't inflate verbs: don't turn “helped with” into “led,” don't
  turn “participated in” into “ran.”
- Where something would be worth adding but I don't have it, put it
  in a “missing” list at the end — don't put it in the résumé.

What to do:
- use the listing's vocabulary wherever it describes the same thing
  I do
- start every bullet with a verb and note what came out of it
- expand the bullets for relevant positions, shrink irrelevant ones
  to one line
- at most 5 bullets per role, 2 for older positions

Listing: [paste]
My résumé: [paste]
My notes on each position: [paste the output from phase 2]

At the end, give a table: original wording | new wording | why you
changed it. I want to see every single change.

Here's my rewritten résumé and the listing analysis.

Reorder it so the first 15 lines cover what's most relevant to this
role.

- propose an order for the sections (experience / education /
  projects / skills / languages) and justify it for this specific
  listing
- within sections, order entries by relevance, not just by date —
  and where that breaks chronology, tell me how to handle it
- propose a short 2—3 line summary right at the top: who I am, what
  I can do relevant to this role, what I'm looking for
- tell me what fits on one page and what has to go

Write the summary at the top in three variants so I can choose.
None of them may contain anything that isn't in my résumé.

Here's the final version of my résumé:

[paste]

Play the role of a recruiter who's brought this résumé into an
interview and wants to check there's substance behind it.

For each bullet, give me:
- one follow-up question they'd ask
- what they'd expect to hear in the answer to be convinced
- how they'd tell it was inflated

Separately flag any bullets that sound stronger than what's
probably actually behind them — the ones where I might stumble on
a follow-up question.

Don't judge whether it's true — only I know that. Just ask.

Pull the keywords a recruiter might search for out of this listing:

[paste the listing]

Split them into:
- job titles and role names
- tools, systems, and technologies
- technical terms and methods
- soft skills, named the way the listing names them
- abbreviations and their spelled-out forms (both, since people
  search for either)

Then compare against my résumé:

[paste your résumé]

Table: keyword | is it in my résumé? | if yes, where | if no, do I
actually have this experience, just under a different name? (say
how)

The last column is a question for me, not a statement. Don't add
words to the résumé — just show me where I describe the same thing
differently.

Check the structure of my résumé from a machine-processing
standpoint. Here's its content exactly as I copied it out of the
finished PDF:

[paste text copied out of the finished PDF, not the original file]

Check:
1. Whether the text copied out fully and in the right order —
   flag anything scrambled or missing as something to fix.
2. Whether section headers are standard and clear (Experience,
   Education, Skills, Languages) — flag unusual ones.
3. Whether dates for each position are in a consistent format.
4. Whether contact info is readable as text, not as an image.
5. What's in a table, a multi-column layout, or a graphic element
   that could fall apart.

For every issue, give a concrete fix. No generic résumé design
advice.

Write me a skeleton cover letter for this role.

Inputs:
- listing: [paste]
- my final résumé: [paste]
- why this role interests me, in my own words: [write 3—5
  sentences, rough is fine]
- what I know about the company: [paste what you've found out]

Rules:
- The letter must NOT retell the résumé. Pick three specific things
  from the listing and, for each, say how I cover it — with one
  concrete example that isn't spelled out in the résumé.
- Don't invent anything, including the reasons the company
  interests me. Use only what I wrote.
- At most half a page, 4 paragraphs.
- No stock phrases like “I read your listing with great interest,”
  “I'm a team player,” “I love learning new things.”
- Last paragraph: what I specifically offer in the first three
  months, stated soberly, with no promises I can't keep.

First give me just a 4-point outline so I can approve it.
The full text after that.

Go through this cover letter and flag any passages that sound like
generated text:

[paste the letter]

Look for:
- phrases that would fit any role at any company
- unsupported superlatives (“a major contribution,” “an exceptional
  opportunity”)
- sentences that don't actually claim anything (“I believe I'd be
  an asset”)
- three synonyms in a row instead of one precise word
- paragraphs that just retell the résumé

Only FLAG them and briefly say why for each. Don't rewrite or
suggest replacements — I'll rewrite it myself.

At the end, tell me which two sentences in the letter are the most
specific, so I know what to build around.

Here's my final résumé and here's the current text of my LinkedIn
profile:

Résumé: [paste]
Profile: [paste the headline, About section, and position
descriptions]

Do two things:

1. Find every inconsistency between the résumé and the profile:
   - different dates for the same position
   - different role titles
   - experience that's only in one of the two documents
   - different phrasing for the same thing
   List them in a table: résumé says | profile says | what to do
   about it.

2. Propose edits to the profile so it doesn't contradict the résumé
   but stays more general — the profile is also read by someone
   hiring for a different role.
   - 3 headline variants
   - a 4—6 sentence About section, first person, no stock phrases
   - 3 bullets per position on what I actually did there

Don't add anything that isn't in the résumé. Where the résumé is
silent and the profile claims something, ask me which one is true.

Prep me for the interview for this role.

Listing: [paste]
My résumé, as sent: [paste]
Gap analysis from earlier: [paste the “don't cover” list]

Generate 15 questions I could realistically be asked, split into:
- technical, directly from the listing's requirements (7)
- about my résumé — mainly places that invite a follow-up (4)
- about the gaps, i.e. what the listing wants that isn't on my
  résumé (4)

For each question, give me:
- why they're asking, what they're trying to find out
- a skeleton for a good answer in 3 points, built ONLY on what's in
  my résumé
- what would make the answer fall flat

Phrase the questions the way a person would actually ask them, not
as bullet-point requirements. Don't write full answers for me —
I want a skeleton, I'll write the text myself.

The listing wants [skill / tool / experience] that I don't have.

My actual situation: [describe honestly — e.g. I've seen it done by
a colleague, I did something similar in a different tool, I know
the principle from another area, I know nothing about it].

Help me prepare an honest answer:
- how to admit it in one sentence, with no apologizing or dodging
- which of the things I actually can do comes closest, and why
- what specifically I can do to catch up, and in what timeframe
- how long the answer should be so it doesn't turn into a ten-
  minute topic

Don't offer phrasing that claims more than what I wrote. If my
answer is “I know nothing about it,” don't paper over that.

From this listing and what I know about the company, prepare
8 questions for me to ask at the end of the interview.

Listing: [paste]
What I know about the company: [paste]
What matters to me in a job: [write 3 things]

Conditions:
- no questions whose answer is already in the listing
- for each, note what the answer would tell me and what a red-flag
  answer would look like
- 3 questions about the day-to-day and expectations in the first
  few months
- 2 about what collaboration looks like and who my closest colleague
  would be
- 2 about why the role is open and what's expected from it
- 1 about the next steps in the process and by when they'll be
  in touch

Order them by which are most important to get to if only two make
it in.

Write me a short email to send the day after my interview.

When the interview was: [date]
Who I spoke with: [name and role]
What we mostly talked about: [2—3 topics]
What I answered poorly or incompletely: [describe]
What I promised to send: [if anything]

Structure:
- a one-sentence thank-you, no gushing
- one specific thing from the conversation that stuck with me or
  that I thought of afterward — that's the core of the email
- a fuller answer to the thing I fumbled, in 2—3 sentences
- anything I'm attaching, if I promised something
- a close: I offer to send more, I ask about the decision timeline

At most 150 words, no first names unless we were on those terms,
address as [Mr. / Ms. Last name].
No pushiness, no repeating what I already said at the interview.