Direct answer
Direct answer: early-career engineers should bring questions that help a mentor inspect a real decision: what to learn next, how to judge technical quality, what evidence to build, which trade-offs matter and what follow-up would prove progress. A useful mentoring question is specific enough that the answer can change an action this month.
A mentoring session is not a performance. It is working time with someone who can see patterns the mentee has not yet seen. The best questions therefore arrive with context: what the engineer is trying to do, what they have already attempted, where they feel uncertain and what decision they need to make next.
That structure matters in diaspora and cross-border STEM networks because mentor time is often voluntary, remote and limited. A session can still be warm and generous, but it should not depend on improvisation alone.
Before the session: frame the decision
The first question should not be "what advice do you have for me?" A better opener is, "I am choosing between these two next steps; what evidence would you want to see before deciding?" That question lets the mentor respond as an engineer rather than as a motivational speaker.
The Government Communications mentor and mentee guide recommends agreeing objectives, ground rules and meeting structure early. For a STEM mentee, that can be translated into a short pre-session note: current project, decision needed, constraint, artifact attached and preferred outcome from the call.
Good preparation also prevents hidden mismatch. A mentor may be strongest on systems design, procurement, research careers, workshop facilitation or professional communication. The mentee should ask what kind of judgement the mentor can offer, then use that strength deliberately.
CAMNEST-UK can support this through workshops and seminars that teach mentees how to prepare questions before they enter a one-to-one relationship. The goal is not to make mentoring formal for its own sake. The goal is to protect the rare chance to receive thoughtful feedback.
Questions about technical judgement
Early-career engineers often ask whether an idea is good. A stronger version is: "Which failure mode would you test first?" That invites the mentor to discuss reliability, assumptions, measurement and constraints. It also shows that the mentee is ready to think beyond presentation polish.
Other useful technical questions include: "What part of this design would worry you in the field?", "Which standard, dataset or stakeholder should I understand before moving forward?", "What would make this prototype unsafe, unmaintainable or too expensive?", and "What evidence would move this from interesting to credible?"
The National Academies STEMM mentorship resources emphasise expectations, culture and development. In engineering, culture includes how people challenge ideas. A mentor is not there to approve every draft. They are there to help the mentee learn which questions a professional environment will ask.
For pilot engineering schemes, technical mentoring should produce artifacts: revised diagrams, risk notes, test plans, stakeholder maps or decision logs. Without artifacts, the session may feel encouraging but leave little evidence that the mentee is developing judgement.
Questions about career direction
Career questions also improve when they become concrete. "How do I grow?" is too broad. "Which two skills would make me more useful on a multidisciplinary project this year?" is sharper. "What should my portfolio prove if I want to move toward energy systems, health technology or infrastructure?" is sharper still.
A mentor can also help a mentee separate identity from sequence. Not every interest needs to become a career immediately. Some skills are foundation skills, some are exploration and some are distractions for now. Asking a mentor to name that distinction can save months of scattered effort.
Early-career engineers should ask about professional habits as well as opportunities. "What did you learn to document earlier than most people?" "How do you communicate uncertainty to non-engineers?" "Which meetings should an engineer prepare for differently?" These questions turn experience into teachable practice.
Contact requests should come late, not first. A better approach is to ask, "What would I need to prepare before you would feel comfortable introducing me to someone in this area?" That respects the mentor relationship and encourages the mentee to build evidence before asking for access.
Evidence and follow-up questions
The most overlooked question is the follow-up question: "What should I bring back next time?" If the answer is vague, the mentee should make it specific. A draft, a data table, a one-page concept note or three revised questions are all better than a promise to "think about it."
UKRI mentoring best-practice material points toward clear purpose and structured support. For CAMNEST-UK, that structure can remain light: the mentee records the action, the mentor records the evidence they expect to see, and the programme lead can notice when pairs need a reset.
A practical question set for every session is simple. First: what decision am I making? Second: what assumption is weakest? Third: what evidence would make this credible? Fourth: who else is affected? Fifth: what should I produce before the next conversation?
That set works because it respects engineering practice. It makes the mentee responsible for preparation, gives the mentor something real to evaluate and turns a conversation into progress that can be inspected later.
The mentee should also bring one question about constraints. Early-career engineers often focus on the technical ideal and understate the practical boundary: budget, maintenance, local skills, procurement, safety, timeline or access to equipment. Asking "which constraint would you design around first?" invites the mentor to teach professional prioritisation.
Another strong question is about communication: "How would you explain this project to a non-engineer who controls resources?" That question matters because engineering progress often depends on people who do not share the same vocabulary. A mentor can help translate technical merit into risk, cost, learning or public value.
Mentees should bring one reflection question as well. "What pattern do you see in how I approach problems?" can reveal habits that are invisible from inside the work. The answer may concern over-explaining, avoiding uncertainty, jumping to tools, under-documenting assumptions or waiting too long to ask for help.
For programme leads, the same questions create a diagnostic record. If many mentees struggle to define evidence, the network may need a workshop on evaluation. If many ask for contacts before showing artifacts, the programme may need stronger preparation guidance. Individual questions can therefore improve the whole mentoring system.
The question list should stay alive. After three sessions, retire questions that have been answered and add sharper ones. A mentee who asks the same broad question every month is probably not converting advice into action. A mentee whose questions become more precise is showing growth even before a final outcome is visible.
The best mentoring questions do not make the mentor feel wise. They make the mentee more capable. They leave behind a clearer decision, a sharper artifact and a next step that can survive the end of the call.
FAQ
How many questions should a mentee bring?
Three strong questions are usually better than ten vague ones, especially when each question includes context and a possible next action.
Should early-career engineers ask for contacts?
Only after they have shown the technical or career question they are trying to solve; mentoring should not become a cold-introduction shortcut.
What should be written down after the session?
Record the decision, the action, the evidence to produce and the date of the next useful check-in.
Sources consulted: National Academies STEMM mentorship tools, UKRI formal mentoring best practice, Government Communications mentor and mentee guide, ASME mentor guidance. Featured image: existing site asset, /assets/img/photo-section.jpg.