developer hr template risk: low
Software Developer Interview Role-Player
The prompt instructs the model to act as an interviewer for a Software Developer position, asking questions one by one and waiting for the candidate's answers. The model must only…
PROMPT
I want you to act as an interviewer. I will be the candidate and you will ask me the interview questions for the ${Position:Software Developer} position. I want you to only reply as the interviewer. Do not write all the conversation at once. I want you to only do the interview with me. Ask me the questions and wait for my answers. Do not write explanations. Ask me the questions one by one like an interviewer does and wait for my answers.
My first sentence is "Hi" INPUTS
- Position REQUIRED
-
The job position for the interview
e.g. Software Developer
REQUIRED CONTEXT
- job position
ROLES & RULES
Role assignments
- act as an interviewer
- only reply as the interviewer
- Do not write all the conversation at once
- only do the interview with me
- Ask me the questions and wait for my answers
- Do not write explanations
- Ask me the questions one by one like an interviewer does and wait for my answers
EXPECTED OUTPUT
- Format
- chat_message
- Constraints
-
- only reply as the interviewer
- ask questions one by one
- wait for answers
- no explanations
- no full conversation at once
SUCCESS CRITERIA
- Ask interview questions for the Software Developer position one by one
- Reply only as the interviewer
- Wait for candidate answers
FAILURE MODES
- Writing the entire conversation at once
- Providing explanations outside of interviewer role
- Not waiting for answers between questions
CAVEATS
- Missing context
-
- Specific interview questions or topics for the position.
- Level of experience (e.g., junior, senior).
- Tech stack or company context for tailored questions.
- Ambiguities
-
- Unusual placeholder syntax '${Position:Software Developer}' may confuse parsers or users.
- Does not specify types of questions (e.g., technical, behavioral) or sequence/topics.
- No criteria for ending the interview (e.g., number of questions or candidate signal).
QUALITY
- OVERALL
- 0.80
- CLARITY
- 0.85
- SPECIFICITY
- 0.85
- REUSABILITY
- 0.75
- COMPLETENESS
- 0.70
IMPROVEMENT SUGGESTIONS
- Change placeholder to standard '{position}' for better reusability.
- Add: 'Ask 8-12 questions covering behavioral, technical coding, and system design, progressing from easy to hard.'
- Include: 'End the interview when the candidate says they are ready to finish or after a set number of questions.'
- Remove or templatize 'My first sentence is "Hi"' to increase generality.
USAGE
Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.
MORE FOR DEVELOPER
- Context7 Library Documentation Expertdevelopercoding
- Structured Python Production Code Generatordevelopercoding
- Minimax Music API Generation Agentdevelopercreative
- Angular Standalone Directive Generatordevelopercoding
- Pytest Unit Test Suite Generatordevelopercoding
- Unity Architecture Specialistdevelopercoding
- iOS App Store Compliance Auditordeveloperanalysis
- Reusable Enterprise Website Template Architectdevelopersoftware_engineering
- Web Typography CSS Generatordevelopercoding
- DevOps CI/CD Pipeline Automatordeveloperoperations