The season is four months long.
You find out how it went in November.
Every student gets the same job-search copilot a paying job seeker gets. Your placement cell sees who is active, who is stuck and who has not started — in week two, not month four. Never their resumes.
How it works. Nobody reports anything to you.
Students use it because it makes their own applications better. Every number on your screen is a count of something a student already did.
- You issue seats
Tell us how many students are in the season. We set the institution up and invite your first admin. Nothing to install, no IT ticket.
- Students claim a link
Paste the roster as a CSV. Each student gets a claim link on a page carrying your name and crest. Unclaimed seats get a nudge.
- They run their own search
Import a resume, set where they will work, and the copilot does the reading. The same product a paying job seeker gets.
- You see the shape
Seats used. Active this week. Applications tracked. Who is stuck, inactive or cold, with the definition next to each.
What every student gets. What your cell sees.
Two views of the same season, separated on purpose.
- A Career Profile built from their resume, with skills that only count when there is evidence behind them.
- New roles found overnight and ranked with reasons, from twelve built-in job sources plus anything they paste.
- A straight answer on every posting: Fit score from three readers, a verdict, the red flags.
- A resume rewritten per application from their own evidence, with a log of every change and every refusal.
- A cover letter in their voice, a PDF export, and a tracker through six stages.
- Interview practice built from the posting and their profile. Not switched on yet; at no extra cost to the student when it is.
- Seats issued, seats claimed, who is active this week.
- Applications tracked per student and the furthest stage each has reached.
- Three attention states with fixed definitions: Stuck, Inactive, Cold — plus Behind target against the interview goal you set.
- A roster you can filter by those states, by branch, by CGPA floor, by never-started.
- CSV and print exports with a provenance header, and an activity log of every export and nudge.
- Your crest on the claim page and through setup. Our name removed entirely on request.
Three states. Each one is a definition, not a judgement.
The thresholds are shown on screen next to every count, so two officers reading the same roster reach the same conclusion.
- Stuck
Claimed a seat 7 or more days ago, no applications tracked yet. One conversation usually fixes it.
- Inactive
No recorded activity in 14 or more days. Different from stuck: they started, then stopped.
- Cold
Tracking applications, but none has moved past Applied in 3 or more weeks. The one to sit down with.
What we will never show you.
- Not their resume — no version, tailored or original.
- Not the cover letters the copilot drafts for them.
- Not why a job scored the way it did for them.
- Not which companies turned them down.
- Not their phone number.
Enforced in the product’s code — the console reads from an allow-list of fields — not promised in a policy. You see the shape. Never the content.
The account is the student’s, and stays theirs after the season ends. Two buttons in their settings: take everything out, or have it deleted. Deletion is scheduled with a cancel link, and every request is logged.
Resume text, contact details and work-authorisation answers are encrypted at the application layer. Nothing a student writes is retained by the model provider. A named person answers privacy questions.
A missing requirement gets an honest answer, not a rewrite.
The sentence a student cannot defend in the interview is the thing to worry about with any AI writing tool. Here is how that cannot happen.
the student says where. It counts, and it can be written.
we show them the nearest real thing they have done, labelled as a bridge. The score does not move.
it stays out of the resume, and the log says so.
Nothing reaches their resume until the student has read the sentence and approved it. A gap usually means a project they forgot to add, not work they cannot do.
Interview practice for the cohort.
Built, and not switched on for anyone yet. Everything below is what it will do — described without a screenshot, because there is nothing yet to screenshot, and priced separately from seats.
- Questions from the posting
The interview for the role they actually applied to, not a generic bank. Their story bank is built from their own projects.
- A round of about fifteen minutes, then a debrief
Coverage before they practise; performance only after a round. We would rather show nothing than a number with nothing behind it.
- Assessments your cell can run
Question sets you author, scored against a rubric calibrated with you. A reviewer decides every row. There is no auto-decline, and bulk decline does not exist.
Priced separately from seats. Your cell will see the same shape it always sees: where the cohort is weakest, named as one thing to teach.
What is coming for institutions.
Said honestly. Some of this is built and waiting for a switch; some is designed and not started. None of it is usable today.
- Cohort interview-readiness view
Where the cohort is weakest across mock rounds, named as one thing to teach. Built alongside Interview Prep; appears when that launches.
- Outcome attribution
A student marks "hired" in their own account; your cohort report shows it — offers held, where and when, with the student in control of what is shared. Designed, not started.
- Co-branded browser extension
The job-board companion, carrying your crest, installable only by students holding one of your seats.
- Roster sync and single sign-on
Today the roster comes in as a CSV and students sign in with email or Google. SIS/LMS sync and SSO are designed for institutions that need them.
How this works: the college issues seats.
Every student in the batch gets one, and your cell gets the console. Price per seat depends on batch size; we quote against your numbers.
A student without a seat can sign up and pay for themselves. Same copilot, nothing for the cell to buy — and no console, because the console is built from seats.
One or the other per student. A seat and a personal plan do not stack.
Questions placement teams ask
Who pays — the college or the student?
What exactly can a placement officer see about a student?
Does this need our IT department?
Can we scope officers to one cohort?
Will it show our placement rate?
Can it carry our brand?
One cohort, one season.
Tell us how many students your cell is placing this season. We set the institution up and invite your first admin. Nothing to install, no procurement portal, no IT ticket.
A conversation, not a signup form. We quote against your numbers and reply within a few days.