How to Prepare for Your Mentor Session
Rule
Come with three specific questions. Not 'is this good?' — that is not a question. 'We cannot get the API to return data when the input contains special characters — here is the error we are seeing' is a question.Have your demo ready.
Run your prototype before the call. Know what works and what does not. Be ready to share your screen and show it live.
Bring three specific questions.
Name every question in advance. The more specific the question, the more useful the answer.
Know your biggest blocker.
The single biggest obstacle between your current prototype and a demo-ready version. Name it before the call, not during it.
What not to do.
Do not spend the first 15 minutes explaining the project. Your mentor has read your brief and README. Start at the problem, not the backstory.
What Your Mentor Is Looking For — Four Lenses
Scope realism.
Is what you are trying to build achievable in two weeks? Mentors often help teams cut features that are not essential to the core demo — and this almost always makes the final product stronger.
Technical unblocking.
What is the hardest technical problem you are facing? Mentors can suggest approaches, libraries, or workarounds.
Ethics gaps.
Has the ethics checklist revealed anything that needs a design change? Mentors flag concerns that may affect the final submission before they become unfixable.
Pitch readiness.
Can you explain what the agent does in 30 seconds? Can you show it doing something real? If not — this is the moment to think about final presentation.
✏️ Student Reflection
After the mentor session: Update your architecture sketch to reflect any scope changes discussed. Document one specific decision you changed as a result of mentor feedback — and why. Set your Week 7–8 milestones in your project log within 24 hours of the call.📝 Your Lesson Submission
Share your reflection, ask a question, or leave a comment. Your mentor will respond.
🔐
You need to be logged in to submit your reflection.
← Previous6.2 — Documentation and Ethics Review (Mid-Build)
Next →7.2 — Iteration and Testing: Making It Reliable🔒 Submit reflection to unlock