For hackathon organizers recruiting mentors
Mentor RosterEnough mentors for every hackathon track, reachable when a team is stuck.
Enter the brief's challenge tracks and sponsor integration, the hacking window and rooms, and the mentors you have with what each actually knows, and get - free in your browser, in the order the skill sets - coverage depth per track, never a headcount, with a sole-substrate or required sponsor API raising that track's bar to a mentor guaranteed on the floor whenever it is worked; every mentor tagged in the brief's own words with every unmatched tag listed; the gaps by track and hour, the overnight ones called out; the mentor-judge conflict with the contact log; the recruitment channels your roster deadline allows; then the request mechanic teams will read and the mentor briefing with the help-versus-build boundary. A mentor is not a volunteer, and not a judge. It never invents a mentor-to-participant ratio, a staffing formula or a response-time target - the one published ratio is shown with its bounds, never converted - hands shift sizing to the volunteer plan as text, labels every number of its own self-set, and never infers anyone's identity or seniority from a name - mentored before is asked.
The event and the hacking window free
Context only - never turned into a mentors-per-participant number.
Blank means today.
The interview free
The skill's ten questions, word for word
- Is the event in person, digital or hybrid; how many rooms does the hacking space occupy; and does the hacking window run through the night?
- Which challenge tracks does the published brief name, and at what sponsor-integration depth - named funder only, optional bonus challenge, required for one track, or the sponsor's technology as sole substrate?
- Is the event themed, with organizer-supplied problems, or open, with participants bringing their own?
- Who is already committed to mentor: community members and alumni, a sponsor's technical staff, or both - and is any sponsor staffing commitment already written into a signed agreement?
- Is any confirmed mentor also on the judge list?
- Do prizes carry cash value, and does any sponsor fund one?
- Have these mentors mentored before, and is this a one-off edition or a recurring event?
- What is the effort ceiling: organizer hours before the event, whether anyone will coordinate mentors live during the window, and whether a shift grid already exists from the volunteer plan.
- By what date must the roster close and the request mechanic reach participants? Channels have lead times and the mechanic has to be published before the window opens, so this date constrains both rather than expressing a preference.
- What already exists that the default ordering assumes away: last edition's mentor list, a university department or user group that would send several people, a sponsor whose staff are already on site for a booth, an organizing team who has built against this API before.
Q1's rooms and window are in card 1, Q2 is the tracks table in card 4, and Q4, Q5 and Q7's mentored-before are answered per mentor there.
The real deadline is whichever comes first of the briefing, the roster close and this order.
The request route, the contact log and the rotation free
The mechanic goes in the same place, before the window opens.
Any routing rung needs at least two - one person's messages stop when they sleep.
Needed whenever a mentor also judges.
For example: git; deployment; python. Blank leaves it out of the coverage.
The tracks and the mentors free
Copy the published brief's own words: an "accessibility" track is tagged "accessibility", not "frontend". Name the sponsor technology by product name. Hours worked look like 2027-03-13 09:00-21:00; blank is the whole window.
Tag what each person has built with; add "(read the docs)" to a tag they only know from the documentation. Mentored before is asked, never inferred - leave it blank when you have not asked.
The mentor plan, worked out free
What the page flags
Coverage depth per track - set against the tracks, not a headcount
Every mentor tagged in the brief's vocabulary - unmatched tags listed, never dropped
Coverage hour by hour across the hacking window
The gaps by track and hour - overnight ones called out
The mentor-judge conflict, stated from one side
Recruitment - re-ranked against the roster deadline, deleted rungs struck
The request mechanic - published before the window opens
The mentor briefing - the help-versus-build boundary
Rotation by expertise, interruption discipline, and the hand-off to the shift plan
The files free
The coverage grid and the tags as spreadsheets, every mentor's slots as a calendar, a mechanic draft and everything the page worked out.
The mentor plan metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
Caveats
The page's check of this reply
Saved mentor plans
How it works - and what is sourced
The order is the skill's: read the published brief; set coverage depth against the tracks, not a headcount, with a sole-substrate or required sponsor integration raising that track's bar from a mentor is available to a mentor is guaranteed on the floor whenever it is worked; pick the recruitment channels the roster deadline allows; tag every mentor in the brief's own vocabulary, the sponsor technology by name; hand the expertise constraint to the volunteer plan, which owns sizing, buffers, confirmation and replacements; publish the request mechanic where teams read the brief, before the window opens; brief the mentors on the help-versus-build boundary; keep the contact log whenever a mentor also judges; record which tracks ran short, and when.
Sourced from the skill and its references: the ten questions, the four menus with their rankings, promotions and deletions, the commitment levels, the boundary formulation, the sponsor engagement rule, the escalation route when no mentor covers a skill, the interruption rules, the one published ratio with its four bounds, and the two people every routing rung needs. Self-set, and said so wherever used: overnight as 00:00 to 06:00, 30 minutes of a slot to count in an hour, the 21-day close-deadline line, 3 days for a warm list and 21 for a sponsor negotiation, stopping visits 3 hours before the close, and the word cap. Never set at all: a mentor-to-participant ratio, a mentors-per-team or per-shift formula, an unblock latency target.