Your course ends. Their job search starts. Stay with them for it.
The promise of a programme is the job after it. Every learner in a batch gets the same copilot a paying job seeker gets, under your brand. Your programme team sees who is active, who is stuck and who has not started. Never their resumes.
How it works. Rolled out per batch, in an afternoon.
Learners use it because it makes their own applications better. Every number on your screen is a count of something a learner already did.
1You issue seats per batch
Tell us the batch size and the track. We set the institution up under your brand and invite your first admin.
2Learners claim a link
Paste the roster as a CSV. Each learner gets a claim link on a page carrying your name and logo. Unclaimed seats are nudged.
3They run their own search
Import a resume or build one from their projects, and the copilot does the reading. The account is theirs, and stays theirs after the programme ends.
4Your team sees the shape
Seats used. Active this week. Applications tracked. Who is stuck, inactive or cold, per batch and per track.
What every learner gets. What your programme team sees.
Two views of the same batch, separated on purpose.
Every learner
- A Career Profile where the capstone and the course projects are the evidence behind each skill.
- 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, a tracker through six stages, a brief each morning.
- Typed interview practice built from the posting and their profile, at no extra cost to the learner.
Your programme team
- Seats issued and claimed per batch; who is active this week.
- Applications tracked per learner and the furthest stage reached.
- Stuck, Inactive, Cold and Behind target, with the definition next to each count.
- A roster you can filter by state, by track, by never-started.
- CSV and print exports with a provenance header; an activity log of every export and nudge.
- Your brand on the claim page and through setup. Ours removed on request.
Who needs a nudge, in week two.
Fixed thresholds, shown on screen, so a programme manager and a career coach reading the same batch reach the same conclusion.
- Stuck
- Claimed a seat 7 or more days ago, no applications tracked yet. Usually a learner who has not imported a resume yet.
- Inactive
- No recorded activity in 14 or more days. They started, then stopped — the one your coach calls.
- Cold
- Tracking applications, but none has moved past Applied in 3 or more weeks. Worth a conversation about which roles they are choosing.
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 learner’s and stays theirs after the programme ends. Two buttons in their settings: take everything out, or have it deleted. Every request is logged.
Resume text, contact details and work-authorisation answers are encrypted at the application layer. Nothing a learner writes is retained by the model provider.
A missing requirement gets an honest answer, not a rewrite.
A learner who cannot defend a line on their resume is your reputation, not just theirs. Here is why that cannot happen.
"I have done this"
the learner says where — a course project counts. It can be written.
"I have something close"
we show the nearest real thing they built, labelled as a bridge. The score does not move.
"Not yet"
it stays out of the resume, and the log says so.
Nothing reaches their resume until the learner has read the sentence and approved it.
Interview practice for the batch.
Typed practice is included with every seat, at no extra cost to the student. Assessments your team runs are priced separately from seats.
Questions from the posting
Each learner practises the interview for the role they applied to. Their story bank is built from the projects they did with you.
A round, then a debrief that quotes them
Coverage before they practise; performance only after a round. Three ranked fixes, each quoting the learner’s own words.
Assessments you can run
Question sets you author, scored against a rubric calibrated with you, with the confidence band published. A reviewer decides every row. No auto-decline.
Your team sees how many learners practised and how many rounds they ran. Where the batch is weakest, named as one thing to teach, comes next.
What is coming for programmes.
Said honestly. Some of this is built and waiting for a switch; some is designed and not started. None of it is usable today.
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.
Cohort interview-readiness view
Where the cohort is weakest across mock rounds, named as one thing to teach. Today the cohort page counts who practised and how many rounds they ran.
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: you issue seats per batch.
1You issue seats
Every learner in the batch gets one, and your programme team gets the console. Price per seat depends on batch size and term, and it can be bundled into your programme fee.
2Or learners start on their own
A learner without a seat can sign up and pay for themselves. Same copilot, nothing for you to buy — and no console, because the console is built from seats.
One or the other per learner. A seat and a personal plan do not stack.
Questions placement teams ask
Can this run under our brand?
Yes. Your name and logo greet every learner on the claim page and stay through setup. If you would rather our name were not on it at all, we do that for you on request. A co-branded browser extension, installable only by your seat holders, is planned.
What does our team see about a learner?
Counts and states only: seat claimed, last activity, applications tracked, furthest pipeline stage, and whether they are stuck, inactive, cold or behind target. Never the resume, the tailored versions, the letters, the reasoning behind a score, or which companies declined them. This is enforced by the code that renders the console.
Is there an API or LMS integration?
Not yet. Rosters come in as a CSV per batch, and learners sign in with email or Google. Roster sync and single sign-on are on the roadmap, designed and not started.
Can we show placement outcomes to prospective learners?
Not from us, not yet. The console shows activity — what learners actually did. Outcome attribution, where a learner marks "hired" in their own account and your report reflects it, is designed and not built yet. We do not invent or estimate placement figures, and we would ask you not to attribute any to this product until that exists.
What happens to a learner’s account after the batch ends?
It stays theirs — profile, applications, history — on the free plan, readable and exportable. They can upgrade personally if they want the overnight search to continue.
One batch, one term.
Tell us the batch size and the track. We set the institution up under your brand and invite your first admin. Nothing to install, no engineering on your side.
A conversation, not a signup form. We quote against your numbers and reply within a few days.