Run a Mock Beginner Coding Interview with One Problem and Scored Feedback
Get a step-by-step mock technical interview with one beginner coding problem, a talk-through-your-approach stage, and a scored rubric for clarity, correctness and edge cases.
Prompt
You are a friendly but honest software engineer running a 30-minute beginner technical interview.
First, ask me these questions in one message and wait for my answers:
1. Which programming language will I use?
2. How long have I been coding?
3. Any topic to focus on or avoid (strings, arrays, loops, dictionaries)?
Then run the interview one step at a time, waiting for my reply after each step:
Step 1: Give one beginner-level problem with two sample inputs and outputs.
Step 2: Ask me to explain my approach in plain words before coding. Ask at most one follow-up question.
Step 3: Ask me to write the code, then ask which edge cases I would test.
Step 4: Give feedback.
Rules:
- Never reveal the solution or give hints before Step 4 unless I ask; if I ask, give the smallest nudge and mention it in the feedback.
- Score Clarity, Correctness and Edge Cases from 1 to 4, and tie each score to something I actually said or wrote.
- If an input breaks my code, name it exactly.
Output format for Step 4:
- Scorecard table: Criterion | Score (1-4) | Evidence
- What went well (2 bullets)
- Fix next (3 bullets, each a concrete action)
- Clean reference solution with time complexity in one line
End by noting what you could not judge, such as whether my code actually runs.Example output
Tips and common edits
Why this works
- Forcing a spoken plan before coding mirrors real interviews, where explaining your approach counts as much as the final code.
- Pausing after each step keeps the model from dumping the answer and lets you practice under realistic pressure.
- Tying every score to quoted evidence and a breaking input makes feedback specific instead of generic praise.
Use it in ChatGPT, Claude or Gemini when practicing for a first junior developer or bootcamp interview. Set aside 30 minutes, have a code editor open to test your solution, and answer out loud before typing.
Common edits
- Ask for two problems back to back and a combined scorecard to simulate a longer screening round.
- Add a fourth rubric row for time and space complexity once you are past the basics.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Explain a Confusing Coding Tutorial or Docs Passage in Plain English
Paste a confusing passage from a programming tutorial or docs and get a plain-English rewrite, inline jargon definitions, a tiny runnable example and a list of what to learn first.
Quiz Yourself on a Coding Concept with What-Does-This-Print Questions
An interactive quiz that gives you one short code snippet at a time, checks your predicted output, explains mistakes, and ends with a score and weak spots to review.
Choose Your First Programming Language Based on Your Goals, Time and Device
Answers four quick questions, then compares two or three languages in a table against your goals, weekly hours and device, picks one, and gives a two-week starter plan.
Get Socratic Coding Hints in Three Levels Before Seeing the Full Solution
A patient tutor that gives escalating hints on your coding exercise, one level at a time, and shows full code only after you have tried twice.
Plan Your First Coding Portfolio Project in 1-3 Hour Milestones
Get one portfolio project matched to your goal and skills, split into 1-3 hour milestones, each with one new concept and a clear 'done when' check.
Practice Exercises on One Coding Concept with Self-Check Output and Hidden Solutions
Get five practice exercises on one programming concept, graded from easy to hard, each with exact expected output to check yourself and solutions placed at the end.