Junior developer interview questions, with scoring guide
Junior developer interview questions with a scoring guide: what each question reveals, strong answer signals, red flags and a short code task to pair.
The short answer
These junior developer interview questions help you hire entry-level developers who read and reason about code, investigate problems methodically and learn new concepts quickly. Ask every candidate the same six questions with the same follow-ups, score each answer from 1 to 4, and pair the interview with a short task reading a function and proposing a testable fix.
Replace the placeholders and review the template against the actual role and local requirements before use.
Junior Developer: structured interview
Purpose
Explore read and reason about code, investigate problems, learn new concepts with the same core questions for each candidate.
1. Walk us through what you would do when a bug cannot be reproduced consistently.
Follow up: What did you do personally? What information did you use? What would you change?
2. Walk us through a task where read and reason about code mattered.
Look for: a specific example, a clear approach and an explanation of the result.
3. How would you handle a mistake involving investigate problems?
Look for: ownership, checking the impact and a useful correction.
4. What would you need to clarify before starting this work sample?
Read a short function, explain one edge case and propose a small, testable correction.
Look for: relevant questions rather than confident assumptions.
5. What feedback helped you improve learn new concepts?
Look for: a concrete change in behavior and reflection on the outcome.
6. Which tools would you use, and what would you verify yourself?
Look for: appropriate tool use and accountability for the final work.
Scoring guide
1: No relevant example or unsupported claim.
2: Partly relevant evidence, with important gaps.
3: Clear relevant example and a sound approach.
4: Strong evidence, sensible trade-offs and thoughtful reflection.
Record evidence before discussing scores. Do not reward similarity to the interviewer. Offer accommodations and avoid questions about protected personal information.
Candidate questions
Leave time for the candidate to ask about responsibilities, feedback, working arrangements and the next step.
Use these entry level developer interview questions with the strongest applicants from a short skills assessment. Ask them in order and score as you go. Rather than long puzzles, the coding interview questions for juniors here focus on explaining and changing code, which shows understanding and is harder to fake with outside help.
What good answers include
Score each answer against the 1 to 4 guide in the template. Strong answers to each question typically include:
A bug that cannot be reproduced: gathering information, logs, narrowing conditions and asking for help at the right time.
Reading code: explaining what a piece of code does, line by line, and where it could fail.
A mistake while investigating: owning a wrong assumption, finding the real cause and adding a test.
Clarifying the function task: questions about inputs, edge cases and expected behaviour.
Feedback on learning: a concrete change in how they learn new concepts, such as building a small example.
Tools: debuggers, documentation and AI assistants, while verifying the code themselves.
Red flags
Treat these as prompts for a follow-up question, not automatic rejections:
Guesses at fixes without investigating.
Cannot explain code they say they wrote.
No mention of testing a change.
Relies on AI output without checking it.
Nerves can make anyone's first answer vague, so ask a follow-up before scoring. If you notice a red flag, ask the candidate for a specific example or to explain their reasoning, and score what they say next rather than your first impression.
A work sample to pair with the interview
Pair the interview with the task in the template: read a short function, explain one edge case and propose a small, testable correction, in 20 minutes, talking through their thinking. The junior developer assessment shows the tests that come first, including a SQL coding task graded on hidden test cases, and our guide on Interview Coder explains formats that hold up when AI tools are common.
Scoring the answers consistently
Score every candidate with the same scale and record evidence as you go. Copy the free interview scorecard template, list these junior developer interview questions as its criteria, and write one line of evidence for each score before you compare notes with other interviewers. If two of you interview, score independently first, then discuss any answer where your scores differ by more than a point. Our guide to structured interviews explains calibration in more detail, with a worked example of a four-level rating scale.
Gather skills evidence before the interview
Interviews work best when you already know who can do the core tasks. Send a short skills test to every applicant who meets the basic requirements, then interview the strongest few. Bring one of each candidate's test answers into the interview and ask them to talk it through: it confirms the result and gives you a natural follow-up question. The hiring process for small businesses shows where each step fits, from the job definition to the offer.
Key junior developer interview questions, what they reveal and strong answer signals
What it reveals
Strong answer signals
Unreproducible bug
Methodical investigation
Gathers data, narrows conditions
Reading code
Understanding
Explains behaviour and failure points
Learning new concepts
Growth
Specific method and example
Frequently asked questions
What are good junior developer interview questions and answers?+
Ask candidates to explain code, debug a problem, describe how they learn and how they verify their work. Strong answers are specific and show a methodical approach, not memorised definitions.
Should I use coding puzzles for junior developers?+
Short code reading and small changes to real code are usually fairer and more informative than long algorithm puzzles, and they reflect the work juniors actually do.
Can candidates use AI tools in a developer interview?+
Decide in advance and tell candidates. Many teams keep the interview AI-free but allow AI in a disclosed work sample, scoring how candidates check and adapt the output.
What should I test before a junior developer interview?+
A short coding test in the language the role uses, plus a reasoning test, give comparable evidence for every applicant. The interview then explores how each candidate applies those skills in practice.
How long should a junior developer interview take?+
About 45 minutes: 30 for the six questions and follow-ups, and 15 to 20 for a live code-reading or small change task. Tell candidates the total time in the invitation so they can plan their day.
Interview the candidates who showed the skills
Send a short skills test first, then use these questions with the shortlist. Start free.