← Cruxfinder blog

Amazon

5 Claude Prompts Every Amazon Seller Should Save for Hiring Virtual Assistants

Hiring and onboarding a virtual assistant well takes real structure most sellers build from scratch each time. Here are five reusable Claude prompts built specifically for that process.

Eric Hawley · August 17, 2026 · 8 min read

Last updated August 2026

5 Claude Prompts Every Amazon Seller Should Save for Hiring Virtual Assistants

Photo by Planet Volumes on Unsplash (https://unsplash.com/@planetvolumes)

Table of contents

Hiring a virtual assistant well takes more structure than most sellers give it, a clear job description, a consistent interview process, a real onboarding plan, and most of that structure gets skipped or improvised under time pressure. These five prompts are built to fix that specifically.

1. Drafting a Specific Job Description

"Write a job description for a virtual assistant to handle [specific tasks: PPC monitoring, customer service, listing updates] for an Amazon [category] business, using [specific tools: Seller Central, a specific PPC tool, a specific helpdesk]. Include the specific skills that would actually predict success in this role, not generic virtual assistant qualifications." A generic job posting attracts generic applicants, Harvard Business Review's reporting on employees informally using AI tools inside their companies covers a related pattern worth knowing, new hires increasingly expect to use AI tools themselves, worth factoring into how a role is actually structured. specificity in the posting itself is a filter.

claude ai prompts writing screen
Photo by Planet Volumes on Unsplash (https://unsplash.com/@planetvolumes)

2. Building a Structured Interview Question Set

"Draft ten interview questions for this role, focused on situational judgment for the specific tasks in the job description, not generic behavioral questions. Include at least three questions that would reveal whether a candidate has actually done this kind of work before versus just claiming familiarity." Situational, role-specific questions surface real capability more reliably than generic interview templates.

3. Creating a Skills Assessment Task

"Design a short, realistic task a candidate could complete in under an hour that would demonstrate whether they can actually do [a specific core task from the job description]. Include clear evaluation criteria for what a strong response looks like versus a weak one." A real work sample, evaluated against explicit criteria, predicts on-the-job performance far better than an interview alone.

4. Building a Structured Onboarding Checklist

job interview resume desk
Photo by Dayne Topkin on Unsplash (https://unsplash.com/@dtopkin1)

"Create a first-two-weeks onboarding checklist for a new virtual assistant handling [specific responsibilities], including account access to set up, training materials to walk through, and a specific first task appropriate for week one that builds confidence without high stakes." A structured onboarding reduces the ramp-up time that otherwise eats into the first month of a new hire's actual productivity.

5. Drafting a Standard 30-Day Check-In

"Draft a structured 30-day check-in template covering what's going well, what's been unclear, and specific performance against the original job description's core tasks, framed to encourage honest feedback rather than just reassurance." A consistent check-in template, used with every new hire, makes it far easier to compare how onboarding is actually going across multiple hires over time.

Making These Prompts Reusable

Save these five as a standing reference rather than rewriting them from scratch for each new hire. Customizing the bracketed placeholders for a specific role takes minutes once the underlying structure exists, which is the entire point of building this once rather than improvising it every time hiring comes up.

What This Does Not Replace

Harvard Law School's Program on Negotiation covers how AI is genuinely changing preparation for high-stakes conversations without replacing the human judgment that actually makes a hiring decision, a closely related principle here: these prompts structure the hiring process, they do not replace your own evaluation of whether a specific candidate is genuinely the right fit.

A Worked Example of the Full Sequence

Say you're hiring for PPC monitoring specifically. The job description prompt produces a posting naming your actual PPC tool and the specific metrics the VA will track. The interview questions prompt produces situational questions like "a campaign's ACoS jumped 40 percent overnight, walk me through how you'd investigate it," which reveals real process knowledge a generic "tell me about a time you solved a problem" question would not. The skills assessment gives the candidate an actual (anonymized) account snapshot and asks them to flag what they'd investigate first, which is a far better predictor of real performance than either the posting or the interview alone.

Building This Into a Repeatable Hiring Process

Once these five prompts produce a workflow that's working well, consider saving the sequence as a reusable Skill if you're using Claude Cowork, so future hires follow the identical structured process without rebuilding it each time. Our guide on the Simplest Possible Attempt method for building reliable Claude Skills covers exactly this kind of iterative refinement, from a rough first version to something worth saving and reusing.

Adapting These Prompts for Different Roles

While written around a PPC monitoring example, the same five-prompt structure, job description, interview questions, skills assessment, onboarding checklist, 30-day check-in, applies directly to hiring for customer service, listing management, or any other recurring role. The only changes needed are the bracketed specifics: the actual tools, tasks, and category context for that particular role. Building a small library of these adapted prompt sets for each recurring role type you hire for turns this from a one-time technique into a genuinely reusable hiring system.

Frequently Asked Questions

Do these prompts only work with Claude, or would they work with other AI tools too?

The wording is largely tool-agnostic, but they're written to take advantage of Claude's ability to hold a longer, more detailed job context across a conversation, which matters when refining a job description or onboarding checklist through several rounds.

Should I use the AI-drafted interview questions exactly as written?

Use them as a strong starting structure, then adjust for your specific role and category, since a generic question set misses the specifics that actually predict good performance in your particular business.

Can Claude actually screen candidates for me?

No, it can help you draft evaluation criteria and structure the review process, but the actual judgment on a specific candidate's fit still requires your own review of their responses and work samples.

How specific should the job description prompt be?

Very specific. Include the actual tools they'll use, the specific tasks they'll own, and your category, since a generic virtual assistant job description attracts generic, less-qualified applicants.

Takeaways

  • A specific job description naming actual tools and tasks filters for more qualified applicants than a generic virtual assistant posting.
  • Situational, role-specific interview questions surface real capability more reliably than generic behavioral questions.
  • A short, realistic skills assessment task with explicit evaluation criteria predicts on-the-job performance better than an interview alone.
  • A structured onboarding checklist reduces the ramp-up time that otherwise eats into a new hire's first productive month.
  • A consistent 30-day check-in template used across every hire makes it possible to compare how onboarding is actually going over time.

For ongoing coverage of Amazon seller operations and team building, see our newsletter.

ShareXLinkedIn

Keep up with Amazon seller news and marketplace updates in the weekly Cruxfinder issue.

Frequently asked questions

Do these prompts only work with Claude, or would they work with other AI tools too?
The wording is largely tool-agnostic, but they're written to take advantage of Claude's ability to hold a longer, more detailed job context across a conversation, which matters when refining a job description or onboarding checklist through several rounds.
Should I use the AI-drafted interview questions exactly as written?
Use them as a strong starting structure, then adjust for your specific role and category, since a generic question set misses the specifics that actually predict good performance in your particular business.
Can Claude actually screen candidates for me?
No, it can help you draft evaluation criteria and structure the review process, but the actual judgment on a specific candidate's fit still requires your own review of their responses and work samples.
How specific should the job description prompt be?
Very specific. Include the actual tools they'll use, the specific tasks they'll own, and your category, since a generic virtual assistant job description attracts generic, less-qualified applicants.

Want this in your inbox every Monday?