Questions
Questions that get real answers
Question types that unlock honest answers in informational interviews: day-to-day work, skills, entry paths, tradeoffs, and a worked example conversation arc.

Weak questions get brochure answers. Strong questions invite stories, tradeoffs, and specifics you cannot scrape from a careers page.
This Mentorwick guide groups question types, shows which ones to avoid early, and walks through a worked example arc for a thirty-minute chat.
Paper is enough.
Start with the day, then the path
Ask what a normal Tuesday looks like before asking how to 'break in.' Day-to-day detail grounds everything else.
Skill questions should separate must-haves from nice-to-haves. 'Which skill would you hire for tomorrow?' beats 'What skills matter?'
Entry-path questions work better as stories: 'How did people on your team get their first role?' invites patterns, not slogans.
Practice your first question out loud. Stumbles at the start waste scarce minutes and make you rush the better questions later.
When they offer a story, follow the story before you jump to your next prepared line. Curiosity reads better than a checklist.
After the meeting, turn notes into three actions for the next month. Learning without a next action tends to evaporate.
Invite tradeoffs and warnings
Ask what surprises newcomers, what burns people out, and what they wish they had known. Honest answers often live here.
Save compensation for later meetings unless they offer it. Early pay questions can shift the tone toward a job screen.
Close with 'Who else should I learn from?' only if the conversation went well — and make it optional.
Rushed closings feel disrespectful.
Worked example: A thirty-minute arc
Mina spoke with a nonprofit fundraiser. Minutes 1–5: thank-you and her one-line goal. Minutes 5–15: Tuesday schedule and which skills show up weekly. Minutes 15–25: how teammates entered the field and what newcomers misunderstand. Minutes 25–30: one warning and a thank-you.
She avoided 'Can you get me a job?' and left with three concrete practice projects. The fundraiser later introduced her to a peer — unprompted — because the conversation stayed respectful.
Mina's notes used the other person's phrases. Those phrases later helped her rewrite a cover letter without copying anyone's private advice into a public post.
Turning answers into a thirty-day plan
After each meeting, pick one skill to practice, one person to learn from next, and one artifact to build.
Schedule the practice on your calendar the same day you write the notes. Intention without a slot fades.
Share a short progress note with the person only if they invited follow-up. Otherwise keep the work private until you have something useful to show.
Review your question list monthly. Retire questions you can now answer yourself.
If three conversations give the same warning, treat it as a pattern worth planning around.
Listening techniques that keep answers flowing
Silence is a tool. After an answer ends, wait two seconds before your next question. People often add the most candid detail in that pause, especially about challenges or trade-offs.
Reflect a phrase back: 'You said the first ninety days were mostly shadowing. What did you shadow?' Using their own words shows attention and invites depth without a new prepared question.
Take short notes on paper rather than typing during a video call. Keyboard noise and a glance away from the camera can make the other person shorten answers to fit your note-taking.
Watch for energy shifts. When the person speeds up or smiles while describing a project, ask a follow-up there. Enthusiasm often marks the part of the job they think newcomers misunderstand.
Questions to retire
Some common questions rarely produce useful information. 'What is a typical day like?' tends to invite a vague overview; ask instead about yesterday or last Tuesday, which anchors the answer in real events.
'Do you like your job?' usually gets a polite yes. Try 'What would make you leave this field?' or 'What surprised you most in your first year?' to surface more honest views.
Avoid asking for information you could find in five minutes online, such as the company founding year or headquarters city. It signals limited preparation and uses time that could go to experience only they can share.
Checklist for your question list
- Do I have a day-in-the-life question first?
- Do I separate must-have skills from optional ones?
- Did I include one tradeoff or warning question?
- Am I avoiding early compensation and referral demands?
- Can I ask follow-ups based on their answers?
- Do I have a clean closing question that respects time?
Quick reference: question types
| Type | Example | Why it works | Avoid early |
|---|---|---|---|
| Day-to-day | What does Tuesday look like? | Gets concrete detail | Vague 'tell me about your job' |
| Skills | Which skill would you hire for tomorrow? | Forces priority | Laundry lists |
| Entry path | How did teammates get first roles? | Surfaces patterns | 'How do I break in?' only |
| Tradeoff | What burns people out here? | Invites honesty | Complaint baiting |
| Close | What should I learn next month? | Actionable | Immediate referral ask |
Key terms
- Brochure answer
- A polished generic reply with little usable detail.
- Tradeoff question
- A prompt that invites costs as well as benefits.
- Follow-up
- A question built from something they just said.
- Conversation arc
- The planned order of question types across the meeting.
- Phrase capture
- Writing down their wording for later use in your own materials.
Questions to ask
- What day-in-the-life detail do I still lack?
- Which skill priority do I need clarified?
- What tradeoff am I afraid to ask about?
- How will I follow their stories instead of my script?
- What closing question respects the clock?