Jobs, Open to Work & messages

The hiring half of Fledgy AI. Students find internships, research assistantships and project work on the jobs board; organisations find students in the Open to Work directory; and both sides talk in threaded messages. It exists because the alternative for a student without local connections is to cold-email strangers and hope.

The profile that does the work here is the same one built for a university application. Three years of logged activities is exactly what an organisation reads when deciding whether to interview someone, so nothing has to be written twice. See the overlap between the two applications for what maps onto what.

Off by default

Nothing is listed until the student ticks List me in the public directory. Unticking it removes them from the directory immediately, and takes their listing photo down with it.

Only signed-in accounts can view the directory or send outreach, and messages arrive in an in-app inbox rather than the student's email, so listing yourself never exposes an address.

Fledgy AI does not vet anyone

Two views of the same profile

A student browsing the directory sees the product they signed up for. An organisation sees a professional profile: banner, headshot, name and headline, one line of hard facts, then Experience, Skills and Honors, in the same restrained layer as the rest of the organisation surfaces.

Nothing about the data differs between the two, only the register it is presented in. Someone deciding whether to interview a sixteen-year-old should not be reading a quest log.

Listing photo

Premium members may show a photograph instead of an avatar. It is served only while the listing is published and the subscription is active, only to signed-in users, and never from a shared cache. See Premium.

Messages

Anyone signed in can message a listed student, naming their organisation and the role, and the student can reply in the thread. Messaging used to be one-way: the only route back was off-platform, which for a minor means handing a stranger their email address.

• Conversations are threaded. The opening message is its own thread; every reply chains onto it, and both sides see the same exchange.
• The thread is the authorization boundary. You may reply only to a thread that already contains a message to or from you, so a guessed thread id resolves to nothing.
• Replying marks the messages waiting on you as answered, so an unread count means somebody is actually waiting.
• Not for me declines a conversation without a reply.

The job board

/dashboard/jobs is the other direction: roles posted by organisations, in a two-pane board with the list on the left and the selected role on the right.

• Only the listed tier can post. Ownership and tier are checked as part of the lookup, so a posted organisation id belonging to someone else does not resolve. This is the concrete thing the subscription buys.
• Applying sends your profile. Same rule as the organisation directory: no separate application form, rendered live, and never your essays, documents or financial aid. One application per role, enforced by a unique index, so Apply cannot be used to spam.
• Organisations can recruit you. An organisation that owns a listing can invite a listed student to an interview or a first conversation. It arrives in the same inbox as ordinary outreach, marked as a recruiting request so you can tell it from a cold message, and only students who have published a listing can be recruited. The unread count surfaces in the dashboard sidebar, not just in the inbox, because a student has no reason to open a talent inbox unprompted and an interview request that nobody sees is not a notification.