AI job search: resumes and interviews with ChatGPT or Claude

Review the attached resume against the attached job description from the perspective of a recruiter for this role.

Give me:
1. An editing match assessment from 0 to 100, with your reasoning. This is not the employer's ATS score.
2. Five important requirements or keywords missing from the document.
3. For each gap, distinguish experience that is present but poorly described from experience with no evidence in my resume.
4. Three points that could raise questions during a quick read.
5. Which sections are strong or weak, and why.
6. The changes I should make first.

Use only the supplied information. Do not claim to work for this company or know how it ranks applicants. Ask when information is missing. Do not invent experience, skills or achievements.

Rewrite my experience section using the previous review and the facts I supplied.

Rules:
1. Include job-description keywords only when they describe my actual experience.
2. Build bullets around what I accomplished, how it was measured and what I did. Use XYZ where the information supports it, without forcing the formula.
3. Start with a clear action verb. Replace "responsible for" where you can describe the action itself.
4. Use numbers only when I supplied them. Mark missing details [FILL IN] and ask what needs measuring. Do not suggest a plausible-looking number.
5. Keep bullets as short as possible without losing useful information.
6. Put the achievements most relevant to this role first.
7. Do not change dates, titles, responsibility or qualifications.

Show the revised wording and the questions that still need answers.

Review the revised resume against the job in two passes.

First pass: technical readability.
- Which requirements have evidence in the text, and which are still missing?
- Are headings, tables, columns or contact details likely to make information extraction harder?
- If you can only see text rather than the formatted file, say that you cannot check the layout.
- Do not guarantee an ATS pass or 100% compatibility.

Second pass: a hiring manager's read.
- What is clear on a quick read, and what takes effort?
- Which claims need an example or explanation?
- Which bullets could be shortened or moved?
- What would I need to explain in an interview?

Return a final version and a pre-submission checklist. Keep my facts intact and do not fill missing details yourself.

Find [JOB TITLE] roles in [LOCATION OR REMOTE] posted in the last [7/14/30] days on LinkedIn or Indeed, depending on the access available to you.

1. Read the full description, check that the listing is active and provide its link and the date checked.
2. Compare required qualifications with my experience. Flag gaps and explain the fit in words. Do not present a score as my chance of getting hired.
3. Choose up to 10 relevant jobs. If there are fewer, do not pad the list with weak matches.
4. For each job, draft a tailored summary, relevant experience bullets and a cover note of no more than three sentences.
5. Before each submission, show me the wording, file and form answers, then wait for my approval.
6. Do not guess answers about work authorization, availability, salary or experience I have not supplied.

Keep a table with company, role, link, gaps, changes and status. Write "submitted" only when the site confirms submission. Otherwise use "draft" or "needs attention".

Write a cover letter of no more than 250 words using my resume and the job description in this conversation.

- Open with a requirement or problem explicitly stated in the job description.
- Connect two or three real examples from my experience to what the role needs.
- If a relevant gap exists, state it briefly and explain related experience. Do not hide a missing required qualification.
- Close with a specific reason I am interested in the company, using information I supply or a source you show.
- Use direct language without generic praise or phrases such as "passionate and driven".

Ask before writing the final version if my personal reason or a suitable example is missing.

I have an interview for [ROLE] at [COMPANY] on [DATE]. Use my resume and the job description in this conversation.

1. Prepare a company brief: its activity, business model, competitors and relevant developments. Find current sources, add links and dates, and separate facts from inferences. If search is unavailable, ask me for sources.
2. Suggest 10 plausible technical, behavioral and situational questions. Explain why each fits the role.
3. For each question, outline a 60-90 second answer from experience I supplied. Ask for a story when one is missing; do not invent it.
4. Suggest five questions I could ask about the role and the work.
5. After I review the preparation, run a mock interview with five questions, one at a time. Give feedback on accuracy, clarity and length after each answer.

For behavioral questions, use STAR: Situation, Task, Action, Result. Do not label an answer "perfect".

I received an offer for [ROLE AND LEVEL] at [COMPANY AND LOCATION]: [BASE, BONUS, EQUITY AND BENEFITS]. My priorities and alternatives are [DETAILS].

1. Find relevant compensation data with sources, dates, currency, location and role level. Separate base salary from total compensation and explain weak comparisons.
2. Suggest a reasoned request if there is enough information. Otherwise explain what is missing instead of inventing a number.
3. Draft a direct email expressing interest and requesting a clear change.
4. Prepare wording for a call, including a response when base pay is fixed but other terms can be discussed.
5. Help me compare the offer with my alternatives and the minimum I define. Do not decide whether I should accept or decline.

Do not send anything. Show the draft for review.

Draft a LinkedIn profile update for [TARGET ROLE] using my resume and the job descriptions in this conversation.

- Three short headlines describing my actual work and specialty.
- An About section of up to three short paragraphs with a real example and the roles or conversations I want.
- Experience bullets in a slightly more personal voice, using facts I have approved.
- Five relevant skills, with reasons for their priority. Do not promise search rankings.
- Two or three projects or work samples for Featured, only if they exist and can be shared.

Do not invent achievements or go beyond my information. Flag wording that needs my approval. Check field limits in the interface before use.

Write three follow-up emails for [ROLE] at [COMPANY]. Contact details, conversation notes and the agreed timeline are [DETAILS].

1. After applying: under 60 words, with one job requirement and a brief example of my fit. Suggest timing based on the listing's instructions.
2. After interviewing: under 100 words, with a personal thank-you and a topic we actually discussed. Prepare it for possible delivery within a day.
3. After the agreed update date has passed: under 80 words, asking for an update and making it easy to explain a delay. If no date was agreed, suggest roughly a week as a starting point, not a fixed rule.

Do not invent names, conversations or links. If a source or work sample would help, ask me which one. Return drafts only.

Compare my resume with the job description. Give an editing assessment from 0 to 100 with reasons, and five important requirements without evidence in the document. Separate missing experience from poorly described experience. Do not present this as an actual ATS score.

Rewrite the relevant experience bullets around accomplishment, measure and action. Use only facts and numbers I supplied. Ask for missing measurements or describe a qualitative result without inventing one. Include keywords only when they accurately describe my experience.

Check my resume file for possible text-extraction problems: columns, tables, headers, images and reading order. Say if you cannot see the layout. Suggest fixes and a manual check after uploading. Do not guarantee compatibility with every ATS.

Suggest three challenging technical questions relevant to this role. Ask one at a time and wait for my answer. Give feedback and build an improved outline using my actual experience. Do not invent knowledge I do not have or claim these are the interviewer's exact questions.

Write a cover letter under 250 words. Connect the job requirements with two or three real examples from my experience. Use the personal reason I supply for choosing this company. Ask when information is missing. Avoid lines that could describe any applicant.

Suggest five short LinkedIn headlines for [TARGET ROLE]. Use terms from the attached job descriptions only when they describe my experience. Each headline should explain my work and specialty without promises or invented achievements.

Write a LinkedIn About section under 200 words from my experience. Connect my work to a real example and end with the opportunities I want. Ask for a sample of my writing if you do not have one.

Suggest five behavioral questions based on the job. Ask me for a suitable story for each, then help organize it into Situation, Task, Action and Result. Separate my contribution from the team's work. Do not supply missing results yourself.

Compare the attached offer with relevant data for the role, level and location. Show sources and dates, and separate base from total compensation. Draft a reasoned request and email if the evidence is sufficient. Otherwise list what needs checking.

Write a thank-you email under 150 words using the interview details I provide. Mention a real discussion topic and a relevant example from my experience. Close with the agreed next step. Do not invent a conversation, name or commitment.

Find up to 20 companies with active [ROLE] openings in [LOCATION OR REMOTE]. Give a listing, date checked and reason for fit for each. Separate verified openings from companies worth researching. Say if current search is unavailable or fewer results exist.

Prepare a brief on [COMPANY] before an interview for [ROLE]: its activity, relevant news, evidence about working there and three questions I could ask. Show sources and dates. Separate official information, opinions and inferences. Do not invent a company challenge.