How to write interview questions from a resume

To write interview questions from a resume, pick the lines where the candidate made a decision or claimed a result, and ask why they made that call. Then prepare two or three follow-ups: what else they considered, what went wrong, and which part of the work was theirs. Keep the resume line next to each question so anyone on the panel can see why it’s being asked.

Why resume-based questions work better than generic ones

They test what the candidate actually did. Ask someone to describe a challenge they overcame and you get a rehearsed story. Ask why they capped payment retries at three and you get either a real explanation or a long pause, and both tell you something. People who did the work offer details you didn’t ask for. People who watched from the next desk run out by the second follow-up.

What to look for when you read the resume

Mark four kinds of lines on your first pass and you have the skeleton of a question list.

• Specific numbers or decisions. A retry limit or a new cache has a reason behind it, and that reason is what you want to hear.
• Scope. Owning the payments system could mean they designed it alone, or that they fixed parts of it as one of five engineers.
• Turning points. Changing companies, switching roles, or rebuilding a service on a new stack usually involved a judgment call.
• Vague wording. Improved, led, and stabilized all leave out how much, what exactly, and how far. Those gaps are your questions.

Skip lists of tools and certifications. There’s little to ask about a plain fact.

How to turn one line into a main question and follow-ups

Make the decision in the line your main question, then add follow-ups about alternatives, failure, and personal contribution. The main question asks why, since the resume already says what they did. An example from a fictional candidate:

Resume line: Haneul Kim, backend developer, 4 years, payments team
  Split the nightly settlement batch by merchant and ran the jobs in
  parallel, cutting run time from 2 hours to 40 minutes.

Main question
  Why did you decide to split the batch by merchant?

Follow-ups
  1. What other approaches did you consider, and why not those?
  2. What went differently than you expected after going parallel?
     How did you find out?
  3. Which parts of the design and the code did you do yourself?

You don’t have to ask every follow-up. If the first answer already compared options, skip the first one. If the answer keeps saying “we,” go straight to the third. Do keep one question about failure on every list, though. Resumes only show what went well, so that question is your one chance to hear how the candidate handles a problem.

Why keep the resume line next to each question

It lets any interviewer, including one who didn’t write the list, know what the question is for. Panels often split questions among several people, and a question read without its purpose tends to stop after the first answer. Requiring a source line also keeps personal questions unrelated to the job off the list.

What to write down during the interview

A few words beside each question, and no more. Transcribing pulls your eyes to the screen just when you should be picking the next follow-up. Something like “split by merchant after seeing uneven load, couldn’t explain rollback” is enough to bring the moment back later.

If you want to record, tell the candidate before you start why and for how long, and ask for their consent. If they say no, take notes only.

How to evaluate the candidate afterward

Reread your notes while the interview is fresh, sort them into strengths and concerns, and only then decide. Deciding first and finding support later favors whoever talked most smoothly.

Tie each point to the answer it came from. A strength might be that they explained the merchant split with load numbers; a concern, that they couldn’t say how to roll back a failed run. Then when another interviewer disagrees, you can both look at the same answer.

How to handle the resume and interview records

Treat the resume as the candidate’s personal data: share it only with the people interviewing, and delete it when the hiring process ends. Once it lands in a group chat or on a few laptops, nobody can say where the copies are. If you copied resume lines into your question doc, delete those too. For recordings and notes, follow your company’s retention policy, or agree on one with HR if there isn’t one.

Doing this in DDirong

In DDirong, Interviewer mode pulls items out of an uploaded resume, drafts questions with follow-ups, and highlights the resume sentence behind whichever question you pick. You record the interview and leave short notes beside each question. Afterward the recording is transcribed and, with your notes, turned into strengths, concerns, and an answer summary. The automatic grade is for reference only.

When you complete the interview, the resume and the items taken from it are deleted. The questions, notes, and recording stay. Because of server costs, the mode is available for 7 days after an admin approves it. There is no fee, no paid upgrade, and no automatic billing. Sign in and request it from the mode menu.