Developer Interview Questions

The Challenge: Interviewing When You're Non-Technical

You can't write code. How do you evaluate someone who can?

The good news: You don't need to understand code to hire well. You need to understand problem-solving, communication, and process.

Technical Questions (But Not Really)

These questions test technical thinking without requiring you to understand code:

Problem-Solving Questions

• "Walk me through how you'd build [your app feature]"
  • Good answer: Breaks down into steps, mentions data, users, edge cases
  • Bad answer: Vague ("I'd just use React"), no structure
• "What's the hardest technical problem you've solved?"
  • Good answer: Explains the problem clearly, walks through their approach
  • Bad answer: Uses jargon to sound smart, can't explain simply
• "How would you handle [specific edge case in your app]?"
  • Example: "What if two users try to book the same time slot simultaneously?"
  • Good answer: Thinks through solutions, asks clarifying questions

Architecture & Planning Questions

• "If you were starting this project, what would you build first?"
  • Tests if they understand MVP and prioritization
• "What tech stack would you recommend and why?"
  • Good answer: Justifies choices based on your needs
  • Bad answer: "Whatever I know" or "The newest framework"
• "How would you structure the database for [your app]?"
  • You won't understand details - but they should explain clearly

Soft Skills Questions (Even More Important)

Communication & Process

• "How do you handle being stuck on a problem?"
  • 🚩 Red flag: "I never get stuck" or "I'll figure it out"
  • ✅ Good: Asks for help after trying, uses Google/Stack Overflow
• "Walk me through your typical day/week of work"
  • Tests: Do they plan? Test? Communicate progress?
• "Tell me about a time you missed a deadline"
  • Everyone has - how did they handle it?
  • Did they communicate early or surprise you at the deadline?

Working Style Questions

• "How do you prefer to receive feedback?"
• "What's your availability/timezone overlap?"
  • Critical for remote work - be specific
• "How do you handle changing requirements?"
  • Because requirements WILL change
• "Describe your ideal project setup"
  • Daily standups? Weekly check-ins? Async updates?

Questions for Different Experience Levels

Junior Developers (1-2 years)

Focus on: Learning ability, willingness to ask questions, basics

• "What resources do you use when learning something new?"
• "Tell me about a project where you learned a new technology"
• "How comfortable are you working independently vs with guidance?"
• Expectation: They'll need supervision - that's okay if budget-appropriate

Mid-Level Developers (3-5 years)

Focus on: Independence, decision-making, best practices

• "How do you decide between two technical approaches?"
• "What's your experience with testing/QA?"
• "Tell me about a project you owned end-to-end"
• Expectation: Should work independently with minimal guidance

Senior Developers (6+ years)

Focus on: Architecture, mentoring, long-term thinking

• "How would you set up this project for future scalability?"
• "What's your experience mentoring junior developers?"
• "How do you make technical decisions that affect the whole project?"
• Expectation: Should guide architecture, spot problems early

How to Evaluate Answers (When You're Non-Technical)

Good Signs

• ✅ Explains concepts in simple terms (if they can't explain simply, they don't understand)
• ✅ Asks clarifying questions before answering
• ✅ Admits when they don't know something
• ✅ Mentions trade-offs ("We could do X which is faster, or Y which is more robust")
• ✅ References real projects/experiences
• ✅ Talks about testing and edge cases

Red Flags

• 🚩 Uses jargon excessively without explaining
• 🚩 Dismisses your questions ("That's not how it works")
• 🚩 Overconfident ("This will be easy" / "No problem")
• 🚩 No questions about your project
• 🚩 Vague answers with no specifics
• 🚩 Blames others for past project failures
• 🚩 Can't explain their process

The Portfolio Deep Dive

Ask about their previous work:

• "Show me a project you're proud of - walk me through it"
• "What would you do differently if you rebuilt this?"
• "What was the biggest challenge in this project?"
• "How long did this take? Was it on time/budget?"

What to look for:

• Can they explain their work clearly?
• Do they take ownership or credit the team appropriately?
• Do they learn from past projects?

Sample Scoring Rubric

Rate each area 1-5:

For non-technical founders: Communication (30%) is weighted highest because you MUST be able to understand each other.

Follow-Up Question Techniques

The "Explain Like I'm Five" Test

• When they use jargon: "Can you explain that in simpler terms?"
• Good developers can translate technical → simple
• If they can't explain it simply, they might not understand it deeply

The "How Would You..." Drill-Down

• Start: "How would you build [feature]?"
• Follow-up: "What if [edge case]?"
• Follow-up: "How would you test that?"
• Tests: Do they think through the whole problem or just the happy path?

The "Tell Me More" Probe

• When answers are vague: "Can you give me a specific example?"
• When they mention a project: "Tell me more about that"
• Gets them to reveal depth of knowledge

The Trial Task Alternative

Can't evaluate from questions alone? Consider a paid trial task:

• Duration: 4-8 hours of work
• Pay them: Their hourly rate (non-negotiable)
• Real work: A small, real feature from your project
• Evaluate: Code quality, communication, delivery time

A $200-400 trial task is cheap insurance before committing to a $20K+ project

Interview Structure Template

30-45 minute interview flow:

1. Intro (5 min): Your project, your needs, their background
2. Technical Questions (10 min): Problem-solving, architecture
3. Soft Skills (10 min): Communication, process, working style
4. Portfolio Review (10 min): Walk through their previous work
5. Their Questions (5 min): What do THEY want to know?
   • 🚩 Red flag if they have no questions
6. Next Steps (5 min): Timeline, trial task, references