Claude Prompts for Systems Analyst Job Search

You are an expert recruiter for systems analyst roles. Here is my resume:

[PASTE RESUME]

And the job description:

[PASTE JOB DESCRIPTION]

Rewrite my bullet points to match this role. Lead each with business impact (a process shortened, a system integrated, defects reduced, a requirement delivered) and quantify it. Mirror the exact tools and terms from the job description (for example requirements gathering, BRD/FRD, UML, BPMN, SDLC, SQL, JIRA, Visio, gap analysis, UAT) without inventing anything. Flag any stretch.

Act as an ATS parser for systems analyst roles. From this job description:

[PASTE JOB DESCRIPTION]

List the methods, tools, and exact keyword phrases (for example requirements elicitation, process mapping, data flow diagrams, use cases, stakeholder management, ERP, SQL, Agile, UAT) an ATS would score against, ranked by prominence. Then tell me which are missing from my resume:

[PASTE RESUME]

and where I could add each one truthfully.

Help me quantify this systems analyst project for my resume: [DESCRIBE PROJECT, for example replacing a manual reconciliation process with an automated workflow]. Ask me up to 4 questions to surface the impact (who the stakeholders were, what requirements I gathered, what system or process changed, how much time, error rate, or cost it affected). Then write 2 resume bullets in the format 'accomplished X by doing Y, resulting in Z'.

Write a concise cover letter for this systems analyst role:

[PASTE JOB DESCRIPTION]

Using my background:

[PASTE RESUME OR SUMMARY]

Under 250 words, no cliches. Open with a concrete reason I fit this team or domain, cite one project where I gathered requirements or improved a process and the outcome it drove, and close with a clear call to action. Match the company's tone.

Write a 4 to 5 sentence LinkedIn message to the hiring manager for this systems analyst role: [PASTE ROLE AND COMPANY]. Introduce me briefly, give one specific reason I am interested in their team or product, and mention one relevant thing I have delivered ([DETAIL, for example a BRD that unblocked a stalled integration]). Warm, human, under 90 words.

Act as a hiring manager interviewing me for a systems analyst role. Give me one realistic scenario (for example: a business unit wants a new reporting system but cannot articulate what they need). Play the vague stakeholder and make me elicit requirements by asking questions. After I work through it, tell me which questions I missed, whether I separated needs from wants, and how a strong analyst would have scoped it. Start now and wait for my first question.

I need to practice translating between technical and business audiences. Give me a scenario where I have to explain a systems trade-off (for example: build a custom integration versus buy an off-the-shelf module) to a [ROLE, for example non-technical operations director]. Play that stakeholder and ask the blunt questions they would ask ('what does this cost us?', 'what breaks if we wait?'). After a few rounds, tell me where I was too technical or buried the recommendation.

I have a systems analyst interview at [COMPANY] for a [ROLE] role. Based on the job description below and what is publicly known about how this company works, list the 10 most likely interview questions (requirements, process, technical, and behavioral), and for each give me a one-line strategy for answering it well. Job description: [PASTE JOB DESCRIPTION]

Compare my resume against job descriptions for [TARGET ROLE, for example Senior Business Systems Analyst]. My resume: [PASTE RESUME]. Target job descriptions: [PASTE 2 to 3]. Identify the specific method, tool, and domain gaps between me and these roles (for example BPMN modeling, a specific ERP, Agile ceremonies, data analysis), ranked by how much they matter, and for each suggest the fastest credible way to close or reframe it.