Hiring guide

How the hiring pipelineworks, control by control.

A complete walkthrough of every tab and control, from the first applicant to your final hire. Each section explains what a button does, when to use it, and exactly who gets emailed. Nothing here is theory; it is the product you are using.

About 12 minutes to read 12 sections
Applies to Organizations· Schools· Departments

This is the same reference your team reads inside the product, on the Hiring guide tab. Nothing here is a mockup.

Start here

The pipeline, end to end

Every applicant who applies to one of your opportunities lands in the hiring pipeline as a single row. From there you move them through clear stages, schedule interviews, send offers, and reach a decision. The same applicant data powers four views, a deep filter engine, an AI ranking, and a set of automated student notifications, so you are never copying information between tools.

New applicant
Review
Interview
Offer
Hired

Four views, one filter

Pipeline, List, Insights, and Automation all read the same applicants. Filter once and every view respects it.

Privacy by default

Clicking a name opens a secure preview with a signed token, never a raw ID. Resumes open through a proxy, never a public file link.

You control the emails

Turn on Silent review and move 50 people without sending a thing. Emails go out only from the actions you choose.

SLOS AI is optional

The AI ranks candidates against the role when you ask it to. It never changes a status on its own, and you make the final call.

New here? The fastest path is below: open the Pipeline view, focus one opportunity from the filter, and follow the Review mode steps.

Coverage

What you can hire for

The hiring pipeline is not only for jobs. Every opportunity you post runs through this same workspace, with the stages and the way students are accepted adapted to what you posted. There is one exception: discounts, which a student redeems directly with a code and a link, so there is nothing to review. Everything else, from an internship to a food pantry, lands here as applicants you can act on.

Apply, then get hired or awarded

Internships, jobs, scholarships, programs, research

Students apply through an in-platform application form you build with the form builder, or you point them to your own external application link. Internships and scholarships require one of the two before you can publish. Each applicant enters the pipeline at New and moves through Reviewing, Shortlisted, Interview, Offer, and Hired, with Waitlisted, On hold, and Rejected available at any stage. A scholarship works exactly the same way: applications land here, you shortlist, and you award instead of hire.

InternshipsJobsScholarshipsProgramsResearch
NewReviewingShortlistedInterviewOfferHired

Register, then attend

Events, tours, hackathons, conferences, volunteering

Students register with one tap, or through a short signup form when you ask for more. If you set a capacity, the pipeline enforces it and holds the rest on a waitlist. The stages become Signed up, Confirmed, Waitlisted, and Declined, and after the event you mark each person Attended or No show. A campus tour or site visit is handled as an event: students sign up for a slot, you confirm, and you check them in. The attendance result is delivered to the student on a short grace delay, so a mis-click right after an event is easy to correct.

EventsCampus toursHackathonsConferencesVolunteering
Signed upConfirmedAttendedNo show

Claim a basic-needs benefit

Food pantry

A food pantry is a claim, not an application. A student taps once to reserve for the current cycle. Pantries can recur weekly, every two weeks, or monthly, or run drop-in, and each cycle is its own row, so you can see who is returning and how demand is trending, all in the same pipeline. There is no essay, no resume, and no interview, just a simple, respectful signup.

Discounts are the one type with no pipeline. A student discount is a code and a link the student redeems directly, so there is nothing to review and no applicant list. Shared resources work the same way, as a direct link rather than an application.

When to use it. Whenever you want to know where a given opportunity type lands. If a student can apply, register, or claim it, it is in this pipeline. Only discounts are handled outside it.

View

Pipeline view

The Pipeline is a board: each column is a stage and each card is one applicant. The columns adapt to the kind of opportunity, so a job shows New, Reviewing, Shortlisted, Interview, Offer, and Hired, while an event shows Signed up, Confirmed, Attended, and No show. Drag a card to a new column to change that applicant's status.

What each card tells you at a glance

Strong Match band. A strong / good / fair signal from the deterministic match engine.
Pass check. Whether the applicant meets the hard eligibility gates you set on the posting.
Activity tier. How recently and actively the student has used the platform.
Repeat applicant dot. Marks a student who has applied to more than one of your postings.
Star rating. Your own 1 to 5 rating, set from the card or the drawer.
Notes. Private internal notes your team can add per applicant.
  1. 1

    Click a photo or name to open the secure preview

    It opens in a new tab using a signed token, so the URL never exposes a student ID. Right-click works everywhere, so you can fan several applicants out into tabs.

  2. 2

    Open the drawer for the full picture

    Selecting a card slides in the applicant drawer with the resume, cover letter, form answers, match reasoning, your notes, and the rating, all in one place. Documents open through a proxy route.

  3. 3

    Drag to move, or use the bulk bar

    Drag a card between columns to change one applicant, or tick several cards and use the bulk bar to shortlist, review, reject, send offers, or email a group at once.

When to use it. Visual triage. The board is the fastest way to see the shape of a round and physically move people between stages.

View

List view

The List is a dense, sortable table of the same applicants. It loads more rows as you scroll, so a large round stays fast. Sort by application date, name, rating, GPA, graduation year, or match strength, and tick rows to run the same bulk actions as the board.

Sortable columns

Click a column header to sort. Combine with the filter engine to answer a precise question, for example the highest GPA computer science majors who are willing to relocate.

AI percentage badge

When a SLOS AI ranking is active, the list shows each candidate's match percentage and orders by AI rank, so the strongest fit floats to the top.

When to use it. Scanning many applicants quickly, sorting by a hard number, or selecting a large group for a bulk action.

The engine

Filters and deep answer search

The filter engine is the most powerful part of the pipeline. Set a filter once and it applies across the Pipeline, List, and Insights views, and to every export. Filters combine, so you can describe an exact candidate profile and the board narrows to only those people.

Application status

Every pipeline and event status, from New through Hired, No show, and Withdrawn.

Match strength

Strong, medium, or weak based on the deterministic match engine.

Student type

High school, community college, four year, or graduate.

Documents

Has a resume, or has not attached one.

Willing to relocate

Filter to students open to moving for the role.

GPA range

A minimum and maximum GPA band.

Graduation year

A from and to graduation year window.

Active within

Students active on the platform inside a recent window.

School

Autocomplete across every community college, four year, and high school, including custom typed names.

Location

City and state, applied together as an AND filter.

Field of study

Fifteen major categories, from engineering to the arts.

Offer state

Offer sent, accepted, declined, or expired.

Interview state

Invited, awaiting a pick, confirmed, completed, or cancelled.

Deep answer search, scoped to one opportunity

Focus a single opportunity and you can filter on the actual answers applicants gave on its application form, field by field. Want only the people who answered "Yes, this summer" to your availability question, or who selected a specific track, or who wrote about a particular skill? The form response strip shows a breakdown per question, and one click turns any answer into a filter. This is how you find the right person in a stack of hundreds without opening every application.

  1. 1

    Pick one opportunity from the filter

    Answer filters are specific to a single posting's form, so the engine asks you to focus one opportunity first.

  2. 2

    Open the form response breakdown

    The strip under the header shows each question with a small chart of how people answered. It is computed on the server, so the numbers are exact.

  3. 3

    Turn an answer into a filter

    Click into the filters panel and add an answer condition. The board, list, and any export immediately narrow to people who gave that answer.

When to use it. Finding a precise candidate profile, building a shortlist by hard criteria, or scoping an email or export to exactly the right people.

Intelligence

SLOS AI ranking

SLOS AI reads the full opportunity and each candidate's profile, resume, cover letter, and form answers, then ranks the pool against what the role actually needs. It returns a clear match percentage, a one line reason for each pick, top picks and a waitlist, so you can start with the strongest fit instead of the most recent application.

Deep check vs light check

Light check scores on profile and answers only and does zero resume reading. Deep check actually reads each candidate's resume and cover letter and is materially more thorough. Deep check is off by default.

Blind to identity

The AI never sees race, gender, veteran or disability status, first generation or income, or pronouns. Ranking is blind to that data by construction, and school prestige is not a ranking input.

Tuned per role

A scholarship is scored differently from a software role. The rubric adapts to the opportunity category, so a portfolio matters for a creative role and a code profile matters for engineering.

You decide

The AI assists your ranking and can make mistakes. It never moves a candidate or sends a message. Every hire is your decision.

  1. 1

    Focus one opportunity, then open SLOS AI

    The AI button appears once you focus a single posting. The studio opens full screen and shows every option before you run anything.

  2. 2

    Configure the run

    Choose deep or light check, how many candidates to rank, which statuses to include, and optional recruiter instructions. Instructions are screened for fairness before anything is sent.

  3. 3

    Apply the ranking

    When the run completes you can apply it as a live ranking. The list view sorts by AI rank and shows each percentage. Re-running with the same settings reuses already scored candidates, so you never pay twice.

See everything SLOS AI reads and how it ranks

View

Insights

Insights turns the applicants you are looking at into a picture: the funnel from applied to hired, the breakdown by status, a per question response summary for the focused opportunity, and a demographics panel for the rounds where you collect that data. It respects your active filter, so you can read the shape of any slice of your pool.

Funnel and status mix

See how many applicants reached each stage and where the drop off happens, so you know whether to widen sourcing or tighten screening.

Privacy preserving demographics

Demographic charts only render above a minimum sample size, so a small group can never be reverse engineered to identify an individual.

When to use it. Understanding your applicant pool at a glance, reporting on a round, or spotting where candidates are falling out of the funnel.

View

Automation

Automation lets you build rules that act on applicants for you. A rule watches for a condition, for example an applicant entering a status, and then takes an action, for example moving them to another stage or sending a tailored email. It is the right tool when the same manual step repeats across a high volume round.

  1. 1

    Choose a trigger

    Rules fire on the statuses you pick, so you decide exactly when the automation runs.

  2. 2

    Choose an action

    Move the candidate to a new stage, or send a professional email you have written, so applicants stay informed without manual sending.

  3. 3

    Activate and monitor

    Save and activate the rule. Every run is recorded, so you can see what fired and when.

When to use it. High volume, repeatable workflows where you want consistent, timely updates without touching every applicant by hand.

Controls

Review mode

When you focus one opportunity, a row of review controls appears. These decide whether and when applicants are emailed, which is the part teams most want to get right. The single most important habit is to keep Silent review on until you are ready, then send deliberately.

Only click Mark recruiting complete once you are actually done. It emails every remaining applicant their final status, including the ones being rejected. Finish interviews and offers first.

Silent review

A toggle. When on, dragging applicants between columns does not ping them. Move people freely while you decide; nothing is sent until you choose to send.

Confirm receipt

One click sends every applicant a professional "we received your application" acknowledgment. It is idempotent, so a second click does not double send.

Mark recruiting complete

Finalizes the round and fans out every remaining decision, accepted, rejected, or waitlisted, in one background job. It refuses while live interview invites or unanswered offers remain, and tells you how many, so you can finish those first.

Resend receipt

Owner and admin only. Re-sends the receipt or the final decision past the idempotency guard, for the rare case where a genuine re-send is needed.

Who gets emailed when

  • Confirm receipt: every applicant, once. A second click is a no op unless an admin force re-sends.
  • Interviews, Notify all or selected: only applicants you have placed in the Interviews tab.
  • Offers, Notify all or selected: only applicants you have placed in the Offers tab.
  • Mark recruiting complete: every remaining applicant who has not withdrawn. This is the big one.

If you reopen a round

You can reopen recruiting if you need to add a hire, owners and admins only. Past notifications stay sent. If you mark complete a second time, choose "send to selected" and pick only the new candidates, so you do not send a duplicate rejection to people who already received one.

Catalog

Interviews

Interviews are self booking. You paint your availability as a grid of dates and times, invite candidates to a set, and each one picks a slot that works for them. Times are always shown to the student in the right timezone, and reminders fire to both sides automatically.

Availability sets

Build a date and time grid in your institution's timezone, which is stamped on the server so a teammate in another zone produces the same slots. Reuse a set across many invites.

Bulk or single invite

Invite one candidate, or a whole shortlist to the same set. Each student self books an open slot, so you never play scheduling tag.

Deadlines and expiration

Set how long an invite stays open. An expired invite is marked clearly, and you can re-invite if you choose.

Status that syncs

Invited, awaiting a pick, confirmed, completed, expired, and cancelled all sync to the pipeline and the Interview state filter. Reschedule and cancel cascade correctly on both sides.

Timezone aware reminders

Reminders go out 48 hours, 24 hours, and 3 hours before the interview, to the candidate and to your side, each rendered in the recipient's own timezone. The candidate's copy includes the website and social links you have published, so they can prepare.

Assign the interviewers

Name the teammates who are actually running the meeting and they are reminded on the same schedule, in the portal and by email. The account owner is always reminded, so there is no need to add them. Only active teammates can be assigned, and anyone who leaves stops receiving reminders automatically.

Feedback and rating

After the interview, capture feedback and a rating so your decision is recorded against the applicant.

When to use it. Any time you need to meet candidates. Self booking removes the back and forth and keeps every time correct across zones.

Catalog

Offers

Offers carry a deadline, notes, and any documents you attach. Send one offer or extend the same terms to a whole group, then track who accepted, declined, or let it expire, all from the Offers tab.

Send or extend with terms

Each offer has an expiration date, notes, and attached documents, so the candidate has everything they need to respond.

Bulk offers

Apply one deadline and one set of notes to many selected candidates at once, when you are extending the same offer broadly.

Track the outcome

See accepted, declined, and expired counts, and filter the pipeline by offer state to follow up on the people who have not yet responded.

Pull an offer back

Moving an applicant out of Offer sent clears the offer and warns you first, so a status change never silently rescinds an offer.

When to use it. The final step before a hire. Deadlines keep the process moving and the tracking shows you exactly where every offer stands.

Catalog

Keep in touch

Not every strong candidate is the right fit today. Keep in touch is your talent pool: save standout applicants with tags and notes, then segment, search, email, and export the list when the next role opens.

Save standout candidates

Add a promising applicant to the pool with tags and a note, so you remember why they stood out.

Segment and search

Filter the pool by tag and search by name, so you can find the right person fast when a new opening appears.

Bulk email the pool

Reach the whole list, or a tagged segment, with one professional message when a new opportunity is a fit.

Export for records

Download the pool for your own records or to share with a hiring manager.

When to use it. Building a pipeline of future talent so your next round starts with people you already know are strong.

Frequently asked

What is in the StudentLife OS hiring pipeline?+

Four views over the same applicants: a Pipeline board of drag and drop stage columns, a dense sortable List, an Insights panel with the funnel and response breakdowns, and Automation rules. Around them sit a deep filter engine, an optional AI ranking, self booking interviews, offers with deadlines, and a keep in touch talent pool. One filter applies across every view and every export.

Can I move applicants without emailing them?+

Yes. Silent review is a toggle on every focused opportunity. With it on, dragging applicants between stages sends nothing, so you can triage the entire pool privately. Emails go out only from the actions you choose: Confirm receipt, interview invitations, offers, automation rules you set up, and Mark recruiting complete.

Which kinds of opportunities run through the pipeline?+

Nearly all of them. Internships, jobs, scholarships, programs, and research use apply then get hired or awarded. Events, campus tours, hackathons, conferences, and volunteering use register then attend. A food pantry is a one tap claim per cycle. Discounts are the single exception: a student redeems a code and a link directly, so there is no applicant list to review.

Does the AI ranking see demographics?+

No. The AI never sees race, gender, veteran or disability status, first generation or income, or pronouns, and school prestige is not a ranking input. Ranking is blind to that data by construction. The AI also never moves a candidate and never sends a message. It ranks when you ask it to and you make every decision.

Can I search what applicants actually wrote on my form?+

Yes. Focus a single opportunity and you can filter on the answers applicants gave on its application form, field by field. The form response strip shows a breakdown per question, and one click turns any answer into a filter that narrows the board, the list, and any export.

Is this the same pipeline for organizations, schools, and departments?+

Yes. Every view, control, and stage in this guide works the same way on all three sides, which is why this one guide serves all of them. Inside an account, actions are gated by team role and enforced on the server, so a teammate only sees and can run what their role allows.

Run this pipeline yourself.

Everything in this guide is in the product from day one. Create an account, post an opportunity, and review your first applicants end to end.