Student employment for universities
Student jobs, run from the inbox your departments already use.
A coordinator emails Rook a job. It appears on your pages, students sign in to see why it fits them, and they apply in two minutes. Rook handles everything in between.
How Rook works
The opportunity connection is the product.
Five steps. Rook is responsible for the three in the middle.
Rook distributes it everywhere students already are
The same opportunity appears on your job board, on the department's own site, in the student portal, in feeds, and behind a QR code on a printed flyer. One posting, many placements, all current, and every one of them counted.
Who does the work
Rook, continuously.
The student experience
Students never have to find Rook.
Rook's job listings run inside the pages your students already open: the portal, a department site, a flyer on a door. One tap takes them to a two-minute application with campus sign-in, where they see which jobs fit them and why.
<script src="https://rook.work/embed/v1.js" async></script>
<rook-jobs tenant="example" placement="embed-library" department="library"></rook-jobs>Two lines of HTML. Your web team is done in an afternoon.
Preview of Rook inside a university's student portal: a search box, a department filter and a work-study filter over 214 open campus jobs, each with its department and pay, and a work-study tag where it applies. Choose a job to open its page.
For departments
The dashboard is available. The dashboard is not required.
A coordinator posts twice a year. Asking them to learn and revisit a system is how opportunities go stale. Rook comes to them instead, by email today and in Microsoft Teams next.
Email that writes the posting
Describe the job in a sentence to your school's Rook address. Rook replies with a draft, asks for anything it still needs, and sends a Publish button.
Reply to manage it
"Extend the photography job two weeks." "Show me the applicants." "Close it." Reply to any Rook email about a job, and Rook answers or sends a button to confirm.
A Monday digest that acts
New applicants and how they fit, jobs about to close, and an Extend button that works without signing in.
Feeds, embeds and flyers
RSS and JSON feeds for the whole school, one department or work-study jobs, an embed for any page, and a QR flyer for any door.
Reporting
Know which opportunities are reaching students.
From day one, Rook tracks every opportunity from posting to hire, by department and by where students found it. By the end of your first semester you have your own numbers, not borrowed benchmarks.
Every school gets the dashboard, each report as a spreadsheet, and exports of applications and hires for its own records.
- Where students saw your opportunities, and which placement produced each application and hire
- How long job postings sit open, and how long they take to fill, by department
- How many students applied who had never held a campus job
- Which opportunities closed without a hire, and where each one stalled
Built for how universities buy
Student records never reach the AI.
Rook's assistant reads what staff write in the email thread, the job posting, your department names, today's date and a short note of the conversation so far, and no student records. Rook's own code writes every reply, and an automated test checks before every release that student data doesn't reach the model.
FERPA by design
Applications never reach the AI, and only your school's staff see them. Hiring decisions are buttons, never free text read by a model.
WCAG 2.2 AA
Automated accessibility checks scan every page and the embed, at desktop and phone sizes, and a failure stops the deploy. Emails are simple, high-contrast HTML with a plain-text copy.
Your sign-in
Campus SSO over SAML or OpenID Connect, set up by your IT team with a test login first.
Your procurement
Pay by card, or by invoice and purchase order. Set everything up before you go live.
Questions university teams ask first
No. Rook handles the part before the hire: posting, finding, applying and choosing. Students sign in with your existing SSO (or an emailed link until it's set up), and hires export as a spreadsheet for whatever onboarding you already run.
Plain rules, not an AI: the student's availability against the job's days, the hours they want against the job's hours, the skills they list against the ones the job requires, and work-study. Every fit shows its reasons, to the student and to the department on each application.
One script tag and one <rook-jobs> element per placement, copied from Rook's snippet builder. Your page's styles can't reach inside it and Rook's never leak out, and each placement can show a different department or just work-study jobs.
Enough to write an email. Posting is a sentence to Rook, and the weekly digest brings routine actions to them. The dashboard is there for the offices that want it.
No. Rook's assistant only reads what staff write in the email thread, the job posting, your department names, today's date and a short note of the conversation so far. Students' email addresses and student IDs in a staff email are replaced before anything leaves Rook, and so are their full names, apart from one-word names and names that are also a department or job title. Rook's own code writes every reply, and an automated test checks before every release that student data doesn't reach the model.
Your move
Every opportunity deserves the right student. Every student deserves to know what's possible.
Send us one of your job pages. On a 30-minute call we will have Rook embedded on a copy of it, with your own opportunities in it.
Get started
Start a conversation
Tell us a little about your campus and what you're hoping Rook can do. Someone from the Rook team will reply, usually within a school day.
What happens next
- A reply from someone on the Rook team, not an automated sequence.
- If it helps, a 30-minute walkthrough with Rook running on a copy of one of your job pages.
- When you're ready, we set up your school's site and email your campus admin a link to finish it. It opens to students during a free trial or once you subscribe.