Product tour
One application.
Every step in between.
Follow Maya Rosen as she applies to Northwind Studio's Senior Frontend Engineer job. At every step you'll see two windows on the same moment: the hiring team's, in dark, and the candidate's, in light.
01 The team publishes
A job with its process upfront.
Rachel sets up the Senior Frontend Engineer job: its stages, a reply target for each, and the people on its hiring team. Once Northwind's website is verified, she publishes and copies the job link. The public page shows the whole process, so candidates know what's ahead before they apply.
The workflow is designed once, per job. Stages come in kinds: Applied, Review, Screening, Interview, Assignment, Offer and Decision.
The public job page lists every stage of the process. Nothing is hidden until after you've applied.
- A process per jobStages, each with an optional reply target in working days.
- A link to share anywhereCopy the job link, or let people find it in Find jobs.
- Public once verifiedJobs go public after the company proves its website domain.
02 The candidate applies
With the profile that fits.
Maya keeps a General profile and a card for each kind of role, each with its own CV. She picks Frontend engineer. Northwind gets a copy of that card as she sent it, and Maya lands in the first column with a next step waiting for the team.
Building interfaces people actually enjoy. Six years shipping design systems and product UI.
A copy of the card and its CV, exactly as they were when she applied. Later edits don't change what the team received.
Building interfaces people actually enjoy. Six years shipping design systems and product UI.
Her profile's name, private notes, to-dos and CV labels never reach the company.
- A card per kind of roleEach with its own CV, and a CV builder with an ATS score.
- Verified, never "unverified"Phone and email verification shows teams a badge. Nobody gets a negative label.
- Private stays privateHer profile names, notes, to-dos and CV labels never reach the company. How
03 The shared journey
One pipeline. One journey.
The job's workflow is the candidate's journey. When Rachel moves Maya to Technical interview, Maya's journey moves with her and the card says whose turn it is. Both screens refresh within about a second, with no refreshing and no emails to chase.
A column per stage. Every card says what's next and who's waiting: “Your move” or “Waiting on candidate”.
Her application page: the next action first, then the journey, with the activity, interviews, to-dos, private notes and documents below.
- Rename a stage onceEvery candidate's journey shows the new name.
- A real contact personWhoever answers first becomes the candidate's contact, and can hand over.
- Same object, two viewsOne application per candidate and job. Neither side keeps a copy to maintain.
04 Scheduling
Times offered. One picked.
Rachel offers a few times, or lets Maya choose her own. Maya sees them in her time zone and taps one. It lands on both calendars, nobody is double booked, and a drag on the calendar reschedules.
a Offer, then pick
Interview types, working hours and overrides, and interviewers who are users of the workspace.
Shown in her time zone. Choosing becomes her next step, and the team is told right away.
b Booked on both calendars
Day, Week, Month and List. Drag an interview to move it.
The same interview on Maya's calendar, in her own time zone.
- No double bookingInterviewers are workspace users, so their time is shared.
- Guests with a linkSomeone outside Cortopus joins one interview with a link and a passcode, and sees only that.
- Honest about what's nextGoogle and Outlook calendar sync and automatic video links are planned, not available yet.
05 Home assignments
A brief out. A hand-in back.
Rachel writes the brief in Markdown, attaches files and sets a due date. Maya sees it on her application and in her to-dos, adds her own files, and hands in. The application moves back to the team's court.
a The brief goes out
# Accessible data table
Build a sortable table from the attached data. Keyboard first. Tell us what you'd do with another day.
A Markdown brief, files and a due date, sent from the application.
Accessible data table
Build a sortable table from the attached data. Keyboard first. Tell us what you'd do with another day.
The brief, its files and a place to hand in. The due date appears in her to-dos.
b The hand-in comes back
Her files arrive on the application, right where the brief was. The next step is the team's, with its own reply target.
Handed in, with a date to expect an answer by. Nothing left to chase.
- Files, both waysThe brief's files and her hand-in live on the same application.
- In her to-dosAssignments due sit next to her own tasks.
- A reply target for the reviewThe team has a date to answer by, and so does Maya.
06 Messages
One conversation per application.
Messages live with the application they're about, and arrive live on both sides. Next to them, the team keeps private notes, with @mentions, that the candidate never sees.
@Tom Weiss can you take the React round? I'll cover systems and collaboration. @CoralAI summarize her portfolio notes above.
The team's note sits under the conversation. Teammates get private DMs and groups too, away from any candidate.
Her conversation with Northwind's hiring team, on the application it belongs to. No inbox to search.
- Shared, then privateApplication conversations are shared with the candidate. Notes and DMs are team-only.
- @mentions in notesPull a teammate in, right where the context is.
- @CoralAI, from that thread onlyIt answers using only the conversation or note it's in, and never counts as a human reply.
07 Scorecards and decision
Independent feedback. A clear answer.
After the interviews, each interviewer fills in their own scorecard, and nobody sees the others' until they've added theirs. Then the team decides: an offer for Maya to answer, or a clear close with real reasons.
a Feedback stays on the team's side
Scorecards are independent: others' verdicts stay sealed until you add yours.
She sees where she stands and by when. Scorecards, team notes, stars and blocks never reach her.
b An offer to answer
Hi Maya, we'd love for you to join Northwind Studio. Take your time, and ask us anything before you answer.
Make an offer from the application. The team is told the moment Maya answers.
Hi Maya, we'd love for you to join Northwind Studio. Take your time, and ask us anything before you answer.
An offer to answer, with a message from the team and her questions one tap away.
c Or a clear no, with real reasons
- Not enough relevant experience for the role
- Another candidate is a closer fit
- Doesn't meet a stated requirement of the role
Hi Lucas, thank you for your time and interest in Northwind Studio. We've decided to move forward with other candidates for the Senior Frontend Engineer role…
Reasons are required, chosen from the company's own list, and the message comes from a template. It can be scheduled.
Hi Lucas, thank you for your time and interest in Northwind Studio. We've decided to move forward with other candidates for the Senior Frontend Engineer role. We enjoyed meeting you, and we wish you the best.
A written answer in the team's own words. The reasons are shared only if the team chooses to include them.
- Sealed until you've added yoursOne interviewer's verdict can't shape another's.
- Reasons from your own listWith templates using {first_name}, {job}, {company} and {reasons}.
- Blocking is a decision, not a ruleManual, with a reason, and reversible. Never automatic.
08 The promise
Every candidate hears back.
Each stage of a job can carry a reply target, in working days. The candidate sees the date. The team is reminded before it passes, and flagged when it's overdue. At every step of Maya's story, someone was holding that date.
Warnings and overdue flags on the list. A deadline can be extended when a team needs more time.
A date she can count on, on the stage she's waiting in. Never silence.
A date on each stage
The longest a candidate waits for the team's next move, set per stage, counted in the jurisdiction's working days.
A nudge before it passes
Teams are reminded ahead of the date, and overdue replies are flagged.
Extend, in the open
When a team needs more time, the deadline is extended, not forgotten.
Measured, not promised
Dashboards show replies on time against your own targets, and the median reply time.
What you just saw
Eight arms.
One application.
Every piece of hiring lives on the application that both sides share. Pick any arm to jump back to its chapter.
- ApplicationsEvery application in one place, verified when the company hires on Cortopus.
- StagesThe job's own workflow becomes the candidate's journey, stage by stage.
- InterviewsThe team offers times; the candidate picks one. Booked on both sides.
- AssignmentsBriefs, files and hand-ins, with a due date both sides can see.
- MessagesOne conversation per application, arriving live on both sides.
- ScorecardsIndependent feedback, sealed until each interviewer adds their own.
- DecisionsAn offer to answer, or a clear close with the team's real reasons.
- Reply targetsEach stage can carry a reply date. Candidates hear back.
Go deeper
Two sides. One application.
For candidates
Every application, interview, assignment and offer in one place, with your next step always first. Free for candidates.
Explore Cortopus for candidatesFor hiring teams
Jobs with their process upfront, pipelines that say whose move it is, independent scorecards and fair, reasoned decisions.
Explore Cortopus for hiring teamsEarly access is open
Bring both sides
of hiring together.
Create a candidate account in a minute, or set up your hiring workspace and publish your first job with its process upfront.
Running hiring at scale? Talk to us about early access