Meet the Mentors Who Support MS Hackathon Teams
What a mentor actually does at MS Hackathon
Mentors at MS Hackathon are experienced builders, designers, and researchers who volunteer their time to help teams move from a vague idea to a working prototype. They are not judges, and they are not there to write code for you. Their role is to ask sharp questions, spot risks early, and share practical shortcuts they have learned in real projects.

Every mentor has a different background, so handoffs between mentors are normal. One mentor might help you scope the problem, while another helps you debug an API or polish a pitch. Treat each handoff as a fresh pair of eyes rather than a restart.
How to prepare before you ask for help
Teams that get the most from mentoring arrive with context. Before you approach a mentor, write down what you are building, what you have tried, and where you are stuck. A short written summary saves time and helps the mentor give targeted advice.
- State the problem in one sentence.
- List what you already tested.
- Name the decision you need to make next.
- Bring your current code or prototype link.
When you ask a focused question, mentors can go deeper. Instead of saying "it does not work", say "the login flow fails when the token expires, and we need to choose between refresh tokens and re-login". That kind of question invites a useful answer.
Making the most of mentor handoffs
Handoffs happen when a mentor rotates to another team or when you move from one phase to another. Prepare a short handoff note so the next mentor does not repeat the same questions. Include the goal, the current status, open decisions, and any advice you already received.
"A good handoff is three sentences long and saves twenty minutes of explanation."
Use a simple table to track mentor feedback during the event. It keeps your team aligned and makes the next handoff almost effortless.
| Phase | Mentor focus | Your action |
|---|---|---|
| Ideation | Problem framing and user value | Write a one-sentence pitch |
| Build | Architecture and debugging | Share a minimal reproduction |
| Pitch | Story, demo, and timing | Rehearse a three-minute demo |
Turning advice into progress
After each conversation, decide what you will change within the next hour. Small, concrete changes beat long discussions. If a mentor suggests three options, pick one, test it, and note the result for the next handoff.
- Summarize the advice in your own words.
- Assign one owner to each action.
- Set a short deadline before the next mentor arrives.
Mentors remember teams that listen, iterate, and come back with results. That reputation often turns into valuable feedback during final judging and beyond the event.
Respect the mentor role
Mentors are generous with their time, but they cannot join your team or build your product. Keep questions specific, respect their schedule, and thank them for their input. If you follow the handoff habits above, you will leave MS Hackathon with sharper skills and a stronger network.
