Job reqs and workflows
A job req’s workflow is your hiring process, written down: steps in the order candidates move through them, activities inside each step, and automation rules that act on candidates along the way. One job req has one workflow, and every candidate who applies to that req follows it. Every job req has its own workflow, so a customer care role and a technical support role can be screened completely differently. This is why the job req is the center of everything: change the workflow and you’ve changed what every candidate in that req does next. Workflows have versions. You build changes in a draft, and candidates only see them once you publish. Candidates already in progress stay on the version they started with, keeping their scores, interviews and offers. See Workflows overview and Publish workflow changes.Job reqs and job postings
A job posting is the public ad for a job req: the title, location, pay and description candidates read before they apply. One job req can carry many postings. Use that to advertise the same job in different ways: a different title per city, a different language, or a posting aimed at one board. Whichever posting someone applies through, they land in the same job req and the same workflow, and the Job Post they came from is recorded on their Candidate Application’s Details tab. Two things to know when you reorganize job reqs:- Deactivating, closing or archiving a job req turns all of its postings off and takes them down. Reactivating the req doesn’t turn them back on; you reopen each posting yourself.
- Duplicating a job req doesn’t copy its postings. Create new ones on the copy.
Job postings and job boards
In Journeyfront your career site is called a job board: a branded page, hosted by Journeyfront, that lists open postings. Each posting is linked to exactly one board, in Link to Job Board. This is the one place in the chain where you don’t get a free many-to-many. To list the same job on two boards, for example a global careers site and a country site, create a second posting and link it to the other board. Both postings still feed the same job req. A posting appears on its board only when Make job posting page active and Post job to job board are both on, and the board itself is enabled. See Job boards.Job reqs and referral portals
Referral portals break the pattern: they list job reqs directly, not postings. A job req can appear on several portals at once. You choose this per job req, under Setup, then Configurations, in Show on Referral Portals:| Option | What it does |
|---|---|
| All Portals | The job req is listed on every referral portal. This is the default. |
| No Portals | The job req isn’t listed on any portal. |
| Specific Portals | The job req is listed only on the portals you pick. |
Candidate profiles and applications
When someone applies to a job req, Journeyfront creates a Candidate Application: their progress through that job req’s workflow, with their scores, interviews and offer. Apply to three job reqs and you have three applications. All of a person’s applications roll up into one Candidate Profile. That’s what stops the same person being worked twice by two recruiters without anyone noticing: open their profile and every application is there, whichever job req it belongs to. Where a person has ended up with two records, you can compare and merge them. See Candidate profiles and applications and Compare and merge candidates. Scores, interviews and offers belong to the application, not the person, because each job req measures its own attributes. The person is what ties them together.Job reqs and hiring classes
Because a job req can stay open all year, the people you hire are grouped into hiring classes: usually one per start date, each with its own number of openings. A class belongs to one job req, and a hire counts toward its class’s openings. Once a class has as many hires as openings, it’s marked filled. That’s what lets you answer “how is the March class doing” without creating a new job req every month.Job reqs and job profiles
A job profile is a role as your company measures it: the people who do that job, the assessments they took, how they perform and how long they stay. It’s the level Journeyfront builds predictive models at, because a model needs the outcomes of many employees doing the same work. A job req is one hiring effort. Many job reqs feed a single profile. You might run “Customer Service Tier 1 MX” and “Customer Service Tier 1 PH” as separate job reqs, because they hire in different countries with different languages and teams. Both link to one Customer Service job profile, so everything you learn about customer service agents pools in one place instead of splitting into a dozen thin samples. Each job req links to exactly one job profile, chosen in Linked to Job Profile when you create it. See Create a job req.What the link does when you hire
The link isn’t only for reporting. When you hire someone, Journeyfront creates their employee record in a job profile, and the job req’s profile is the default:1
The Hire window opens
Job Profile is already filled in with the job req’s linked profile.
2
The recruiter can change it
Pick a different profile in that field when this particular hire belongs somewhere else, for example someone hired into a team lead role off a Tier 1 req.
3
The hire lands where you chose
Their employee record is created in that profile, and it shows on the Jobs tab of their Candidate Profile and on the Employees page.
Journeyfront builds predictive models from your outcome data rather than you configuring them. To get a model for a role, ask your Customer Success Manager, then add it to the job reqs linked to that profile. See Predictive models.
The shape of it
| Relationship | How many |
|---|---|
| Job req to workflow | One job req to one workflow, with many steps and activities |
| Job req to job postings | One job req to many postings |
| Job posting to job board | Each posting to exactly one board |
| Job req to referral portals | One job req to many portals |
| Candidate applications to candidate profile | Many applications to one person |
| Job req to hiring classes | One job req to many classes |
| Job reqs to job profile | Many job reqs to one profile |
Related
The whole map
Every piece in one diagram, on the TA leaders guide.
Workflows overview
Steps, activities, automation and versions.
Glossary
Every term, in plain language.